[
https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
eedri reassigned OST-39:
------------------------
Assignee: [email protected] (was: infra)
This will probably require installing OpenShift via Ansible, and since we
already support Ansible in Lago, we need to choose the right playbook from
Galaxy.
proposed role:
https://github.com/openshift/openshift-ansible/tree/master/playbooks/byo
we should run config.yml
> Support for testing ovirt-containers in OST
> -------------------------------------------
>
> Key: OST-39
> URL: https://ovirt-jira.atlassian.net/browse/OST-39
> Project: oVirt system tests
> Issue Type: New Feature
> Reporter: Fabian Deutsch
> Assignee: [email protected]
> 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.1074.0#100051)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
