Hi Eric, see my comments inline.
On Sat, May 21, 2016 at 4:38 PM, Eric Helms <ehelms(a)redhat.com> wrote:
I recall seeing some discussion of Lago vs Vagrant and how there
some leverage between the two. We are currently using Lago in our release
testing pipeline, however, for years now we've been using Vagrant for
deploying developer and production hand-on testing environments. There are
benefits to how we test and build environments to centering on a singular
technology. Thus, I had a few questions I was hoping to get some thoughts
1) What was the outcome of the Lago vs Vagrant discussions?
The outcome was understanding that Vagrant can defiantly help in a few
flows which Lago is currently doing, for e.g Image handling and managing
but probably not replace Lago completely, at least not at first.
We didn't got a chance to peruse this path yet, though we have an intern
that is going to do a POC on it soon and hopefully help move forward with
In the meantime Lago has proven to be valuable tool for oVirt and being
used now in CI for both stable and latest versions, so I do see it being
supported and developed in the near future.
2) How to reconcile the built up base of Vagrant use within our
with Lago (or how to sell switching to Lago)?
It would be great if your group can help POC or move forward with testing
Vagrant with Lago, so we'll have a better idea on where Lago (2.0?) is
unfortunately we have only 1.5 engineers on Lago ATM and they are mostly
focused on supporting oVirt as the first 'customer' which uses Lago in
3) Do you see them as co-existing with different application
Yes, as mentioned above, I'd love to see Lago uses Vagrant when possible,
and If we'll see in the future that It doesn't make sense to continue
maintaining Lago as a layer on top of Vagrant,
We might consider migrating it to be a Vagrant plugin or similar, but I
think its too soon to tell.
To give an example of a disconnect where centering technology would
benefit, we do an installation test currently spinning up a Lago based
environment. Users testing our builds are using our existing Vagrant setup
to spin up environments. However, we aren't testing the setup and
configuration users are using and we end up double building the techniques
for setting up environments.
Thanks for any thoughts,
lago-devel mailing list
EMEA ENG Virtualization R&D
Red Hat Israel
irc: eedri (on #tlv #rhev-dev #rhev-integ)