[
https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.pl...
]
eyal edri [Administrator] commented on OST-39:
----------------------------------------------
[~fdeutsch] Just to emphasis the scope and requirements, let me re-iterate on what we
agreed on the email:
A new OST suite will be created which will run the same tests run today in basic suite,
the difference will be:
1. Replace deploy scripts for engine + storage with Ansible playbook which will install
Kubernetes
2. The Ansible playbook will also need to deploy engine + vdsm as containers in PODS once
Kubernetes will be running
3. Not sure how 'add host' should work - will VDSM come ready in a container and
already connect to the engine or we'll still need to run 'add host' command to
add it? or an alternative 'add host' command.
4. Kubernetes will be running on VMs created by Lago
5. We will consider to use Atomic as OS for the VMs, but CentOS should work as well as
starting point.
Please confirm I'm not talking nonsense and we can continue to move towards this goal
:)
Run OST against vdsm+Engine on kubernetes
-----------------------------------------
Key: OST-39
URL:
https://ovirt-jira.atlassian.net/browse/OST-39
Project: oVirt system tests
Issue Type: New Feature
Reporter: Fabian Deutsch
Assignee: infra
Priority: Highest
Labels: kubevirt
Hey,
Yaniv Bronheim is building containers for vdsm and engine.
Lago should become capable of running OST against this setup.
The basic flow is:
1. Normal CentOS
2. Install kubernetes
3. Deploy engine and vdsm pods
The pod definitions are here:
https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree
https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree
A similar script can be found here:
https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh
But this script is deploying kubevirt, instead of the engine + vdsm container.
--
This message was sent by Atlassian JIRA
(v1000.718.3#100026)