<div dir="ltr">+1</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 21, 2016 at 7:23 PM, Ryan Barry <span dir="ltr"><<a href="mailto:rbarry@redhat.com" target="_blank">rbarry@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">+1 here. It would be a great addition in order to use oVirt for testing without users writing their own API scripts.</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 21, 2016 at 11:05 AM, Vojtech Szocs <span dir="ltr"><<a href="mailto:vszocs@redhat.com" target="_blank">vszocs@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1<br>
<br>
I agree with Barak's point. Plus it would make people (who use Vagrant) aware of oVirt.<br>
<span class="m_7703263983686171069HOEnZb"><font color="#888888"><br>
Vojtech<br>
</font></span><div class="m_7703263983686171069HOEnZb"><div class="m_7703263983686171069h5"><br>
<br>
----- Original Message -----<br>
> From: "Barak Korren" <<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>><br>
> To: "Sandro Bonazzola" <<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a>><br>
> Cc: <a href="mailto:board@ovirt.org" target="_blank">board@ovirt.org</a>, "devel" <<a href="mailto:devel@ovirt.org" target="_blank">devel@ovirt.org</a>><br>
> Sent: Monday, November 21, 2016 6:12:45 PM<br>
> Subject: Re: [ovirt-devel] [Call for Vote] Proposal for new Incubator Project<br>
><br>
> +1<br>
> I think oVirt had been missing from the list of Vagrant providers for too<br>
> long.<br>
><br>
> On 21 November 2016 at 19:09, Sandro Bonazzola < <a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a> > wrote:<br>
><br>
><br>
><br>
><br>
><br>
><br>
> Il 21/Nov/2016 17:55, "Brian Proffitt" < <a href="mailto:bproffit@redhat.com" target="_blank">bproffit@redhat.com</a> > ha scritto:<br>
> ><br>
> > All:<br>
> ><br>
> > This project was initially proposed for review on Oct. 9. It has been<br>
> > reviewed for major issues and having heard no objections, it's now time to<br>
> > formally vote on accepting this as an official oVirt incubator subproject.<br>
> ><br>
> > The last time we voted on one of these was during an IRC weekly meeting, so<br>
> > I believe it is appropriate to post a Call for Vote on the Devel and Board<br>
> > lists.<br>
> ><br>
> > Voting will be open until 1200 UTC Nov. 28, 2016. A net total of +5 votes<br>
> > should be received to formalize this project as an incubator subproject.<br>
> > Please use the following vote process:<br>
> ><br>
> > +1<br>
> > Yes, agree, or the action should be performed. On some issues, this vote<br>
> > must only be given after the voter has tested the action on their own<br>
> > system(s).<br>
> ><br>
> > ±0<br>
> > Abstain, no opinion, or I am happy to let the other group members decide<br>
> > this issue. An abstention may have detrimental affects if too many people<br>
> > abstain.<br>
> ><br>
> > -1<br>
> > No, I veto this action. All vetos must include an explanation of why the<br>
> > veto is appropriate. A veto with no explanation is void.<br>
> ><br>
> > Thank you!<br>
> > Brian Proffitt<br>
> ><br>
> ><br>
> > ---<br>
> ><br>
> > Project Proposal - Vagrant Provider<br>
> ><br>
> > A vagrant provider for oVirt v4<br>
> ><br>
><br>
><br>
> My vote is +0. I have no strong opinion on this and I'm not using vagrant so<br>
> I would be happy to leave other to decide.<br>
> Using the + because I am happy to see the contribution ☺<br>
><br>
><br>
><br>
><br>
><br>
> > Abstract<br>
> ><br>
> > This will be a provider plugin for the Vagrant suite that allows<br>
> > command-line ease of virtual machine provisioning and lifecycle<br>
> > management.<br>
> ><br>
> > Proposal<br>
> ><br>
> > This Vagrant provider plugin will interface with the oVirt REST API<br>
> > (version 4 and higher) using the oVirt provided ruby SDK<br>
> > 'ovirt-engine-sdk-ruby'. This allows users to abstract the user<br>
> > interface and experience into a set of command line abilities to<br>
> > create, provision, destroy and manage the complete lifecycle of<br>
> > virtual machines. It also allows the use of external configuration<br>
> > management and configuration files themselves to be committed into<br>
> > code.<br>
> ><br>
> > Background<br>
> ><br>
> > I have previously forked and maintained the 'vagrant-ovirt' gem as<br>
> > 'vagrant-ovirt3' due to Gems requiring unique names. The original<br>
> > author has officially abandoned the project. For the last few years<br>
> > all code to maintain this project has been maintained by myself and a<br>
> > few ad-hoc github contributors. This provider interfaced directly with<br>
> > oVirt v3 using fog and rbovirt. The new project would be a fresh start<br>
> > using the oVirt provided ruby SDK to work directly with version 4.<br>
> ><br>
> > Rationale<br>
> ><br>
> > The trend in configuration management, operations, and devops has been<br>
> > to maintain as much of the development process as possible in terms of<br>
> > the virtual machines and hosts that they run on. With software like<br>
> > Terraform the tasks of creating the underlying infrastructure such as<br>
> > network rules, etc have had great success moving into 'Infrastructure<br>
> > as code'. The same company behind Terraform got their reputation from<br>
> > Vagrant which aims to utilize the same process for virtual machines<br>
> > themselves. The core software allows for standard commands such as<br>
> > 'up', 'provision', 'destroy' to be used across a provider framework. A<br>
> > provider for oVirt makes the process for managing VMs easier and able<br>
> > to be controlled through code and source control.<br>
> ><br>
> > Initial Goals<br>
> ><br>
> > The initial goal is to get the base steps of 'up', 'down' (halt), and<br>
> > 'destroy' to succeed using the oVirt provided ruby SDK for v4.<br>
> > Stretch/followup goals would be to ensure testability and alternate<br>
> > commands such as 'provision' and allow configuration management suites<br>
> > like puppet to work via 'userdata' (cloud-init).<br>
> ><br>
> > Current Status<br>
> ><br>
> > The version 3 of this software has been heavily utilized. The original<br>
> > fork known as 'vagrant-ovirt' has been abandoned with no plans to<br>
> > communicate or move forward. My upstream fork has had great success<br>
> > with nearly 4x the downloads from <a href="http://rubygems.org" rel="noreferrer" target="_blank">rubygems.org</a> . Until my github fork<br>
> > has more 'stars' I cannot take over it completely so the gem was<br>
> > renamed 'vagrant-ovirt3'. This is also true for <a href="http://rubygems.org" rel="noreferrer" target="_blank">rubygems.org</a> since<br>
> > gems are not namespaced, therefore could not be published without a<br>
> > unique name. The v4 provider is still pending my initial POC commit<br>
> > but there are no current barriers except initial oVirt hosting. The<br>
> > hosting of oVirt v3 for testing is a laptop on a UPS at my home, and<br>
> > v4 is also a different pc attached to a UPS.<br>
> ><br>
> > External Dependencies<br>
> ><br>
> > RHEVM/oVirt REST API - This provider must interact with the API itself<br>
> > to manage virtual machines.<br>
> ><br>
> > Initial Committers<br>
> ><br>
> > Marcus Young ( 3vilpenguin at gmail dot com )<br>
> ><br>
> > --<br>
> > Brian Proffitt<br>
> > Principal Community Analyst<br>
> > Open Source and Standards<br>
> > @TheTechScribe<br>
> > 574.383.9BKP<br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > Devel mailing list<br>
> > <a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
> > <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a><br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> Devel mailing list<br>
> <a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a><br>
><br>
><br>
><br>
> --<br>
> Barak Korren<br>
> <a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a><br>
> RHEV-CI Team<br>
><br>
> ______________________________<wbr>_________________<br>
> Devel mailing list<br>
> <a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a><br>
______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a></div></div></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/devel</a><br></blockquote></div><br></div>