[
https://ovirt-jira.atlassian.net/browse/OVIRT-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26340#comment-26340
]
eyal edri [Administrator] commented on OVIRT-1048:
--------------------------------------------------
Since this will require a whole new suite with different deploy scripts ( but
still using the same tests ),
I wonder if we should add support to use Ansible scripts instead of bash
scripts and utilize existing Ansible playbooks to install Kubernetes [1].
We will still add a new suite, but at least we'll use existing code and not
write new bash scripts for it.
Also, Shouldn't we use CentOS Atomic images rather than base CentOS?
[[email protected]][~ykaul][[email protected]][[email protected]] - WDYT?
[1] https://galaxy.ansible.com/grycap/kubernetes/
> 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.1#100026)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
