[JIRA] (OVIRT-1048) Run OST against vdsm+Engine on kubernetes

[Yaniv Kaul (oVirt JIRA)]

    [ https://ovirt-jira.atlassian.net/browse/OVIRT-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26402#comment-26402 ] 

Yaniv Kaul commented on OVIRT-1048:
-----------------------------------

[~eedri] - I strongly agree. I think lago has just gained good support for providing the Ansible hosts list (via https://github.com/lago-project/lago/pull/428 ).
The provides the basic infrastructure needed from the host (L0) to do things via Ansible.
I'd argue though that we need to use Ansible from L1, not from L0. So I rather we copy the relevant Ansible, scripts, what not, and execute it from L1.

I'm not sure I'd use Atomic right away, though I agree it's a goal.

> Run OST against vdsm+Engine on kubernetes
> -----------------------------------------
>
>                 Key: OVIRT-1048
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1048
>             Project: oVirt - virtualization made easy
>          Issue Type: New Feature
>          Components: Jenkins, Lago
>            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)