[
https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.pl...
]
Yaniv Kaul commented on OST-39:
-------------------------------
0. I think it's time to understand if we want to use Lago for Kubevirt or not. I
prefer vagrant - it's more common, works out of the box on both Ubuntu and possibly
other operating systems (does it have nested virt on Mac or Windows?). I would like to
believe that moving to vagrant is actually a good opportunity to start afresh. Lago is not
killed by it, and will remain relevant for OST.
1. Ansible is supported today in vagrant. I believe a fair start of support exists in Lago
as well - but as Barak pointed out, probably need a bit of Cloud-Init work too perhaps -
not sure.
Engine is not containerized for real yet. Once it does, we'll probably deploy it via
standard Pod deployment options (saw today ansible-containers, for example - sounds neat).
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)