[
https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
eyal edri [Administrator] moved OVIRT-1048 to OST-39:
-----------------------------------------------------
Component/s: (was: Lago)
(was: Jenkins)
Workflow: Software Simplified Workflow for Project OST (was: Task
Management Workflow)
Key: OST-39 (was: OVIRT-1048)
Project: oVirt system tests (was: oVirt - virtualization made easy)
> 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)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
