[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.pl... ] eyal edri [Administrator] commented on OST-39: ---------------------------------------------- This is the tool we're using for tracking issues for OST, so its the right place, if needed we can have a trello card pointing to this ticket. 0. Lago. I don't think that the fact Vagrant was used for POC KubeVirt alone is a major advantage to re-do all the work we've done to make OST run with Lago, Moving to Vagrant will mean investing a lot of efforts and resources ( which we don't have, looking at the Lago+OST headcount ATM ) into making something we already have working for little value IMO and will delay significantly the work to support KubeVirt. We can consider it once we'll have a full time maintainer for Lago/OST. 1. Once we support Ansible as deploy scripts in OST, which shouldn't be hard after the recent merges to Lago, we can just use the existing Kubenetes playbooks, not sure how using Vagrant makes it simpler. Ansible for engine - not sure how/what we'll need, but [~fdeutsch] provided us with POD definitions, I'm guessing once you have Kubenetes its just a matter of running / deploying the engine container? ( so according to the request we should have available engine & vdsm in containers, otherwise I didn't understand the request ) -- This message was sent by Atlassian JIRA (v1000.718.3#100026)