[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26428#comment-26428 ] Yaniv Kaul commented on OST-39: ------------------------------- [~eedri] - too many items there, I think. We should probably document it in KubeVirt's trello and not here. 0. Do we use Lago as is, or vagrant? Unclear to me, and I do see a nice advantage for the community using vagrant. 1. Ansible installing K8S - makes sense to me. This is quite integrated into vagrant and is easy to do (though requires Ansible on Host L0) in Lago. Do we have Ansible to install Engine? Quite possibly from QCI - we should utilize that - but it's not within a Container - Engine is not yet containerized (production-ready, at least) 3. Good point about Add Host. Donno yet... 4. ACK 5. ACK.
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)