On Tue, Nov 26, 2013 at 05:18:49AM -0500, Yaniv Bronheim wrote:
----- Original Message -----
From: "Sandro Bonazzola" sbonazzo@redhat.com To: "Dan Kenigsberg" danken@redhat.com, vdsm-devel@fedorahosted.org Cc: hateya@redhat.com Sent: Tuesday, November 26, 2013 8:50:38 AM Subject: Re: [vdsm] Pending Self-Hosted-Engine Patches in ovirt-3.3.2
Il 25/11/2013 22:16, Dan Kenigsberg ha scritto:
An important feature of ovirt-3.3 has not made it to the ovirt-3.3.0 deadline: http://www.ovirt.org/Features/Self_Hosted_Engine.
It would allow to run Engine as a VM on top one of the hosts controlled by itself, saving resources and allowing high availablity out-of-the-box.
The feature was not ready on time for the ovirt-3.3.0 release but now its Engine-side patches are merged, and its Vdsm-side patches are pending aproval for entry into Vdsm's stable branch.
http://gerrit.ovirt.org/20189 http://gerrit.ovirt.org/20190 http://gerrit.ovirt.org/20191 http://gerrit.ovirt.org/20192 http://gerrit.ovirt.org/20193 http://gerrit.ovirt.org/20194 http://gerrit.ovirt.org/20209 http://gerrit.ovirt.org/20300 http://gerrit.ovirt.org/21357
I suggest to take the pending patches into the ovirt-3.3 branch, and ship ovirt-3.3.2 with this feature enabled.
+1
We shall not release ovirt-3.3.2 before we are assured by quality engineering that we have no regression to main Vdsm code. If we do not receive this green light, and there's urgency to release ovirt-3.3.2, we'd fork and ship 3.3.2 only with the urgent fixes.
Any objections?
not from my side. waiting for the green light
I'm suggesting not to wait with merging. A CR+2 V+1 should be enough for those patches. The release of ovirt-3.3.2 should wait, though.
are there more pending urgent fixes that I'm not aware of?
You may be aware of http://gerrit.ovirt.org/#/c/21700/ but I'm sure there would be more.
Dan.