Re: [ovirt-devel] 3.5.1 RC schedule [was Re: [ovirt-users] oVirt Weekly Sync Meeting: Dec. 10, 2014]
On Fri, Dec 12, 2014 at 03:22:50PM +0100, Sandro Bonazzola wrote: > Il 11/12/2014 10:45, Dan Kenigsberg ha scritto: > > On Thu, Dec 11, 2014 at 08:36:46AM +0100, Sandro Bonazzola wrote: > >> Il 10/12/2014 16:54, Brian Proffitt ha scritto: > >>> (On time this week!) > >>> > >>> = > >>> #ovirt: oVirt Weekly Sync > >>> = > >> > >> [cut] > >> > >>> * 3.5.z updates Two blockers have postponed RC again. New RC date will > >>> be discussed and decided in mailing list. (bkp, 15:30:01) > >> > >> [cut] > >> > >> Let's start the discussion and decision task. > >> We have an ETA on the last pending blocker for 3.5.1 on next week. > >> I suggest to postpone RC and GA after winter holidays. > >> > >> What about: > >> RC - 2015-01-07 > >> GA - 2015-01-14 > > > > Can we have a vdsm respin before that? We get repeated reports of bugs > > that are already solved in the stable branch. > > > > Can you elaborate on what's the request? > 1) have a VDSM async release which should go in > http://resources.ovirt.org/pub/ovirt-3.5/ as stable release > 2) have a "beta" in http://resources.ovirt.org/pub/ovirt-3.5-pre taking > latest snapshot > > If the request is 1, please provide the RPMs to be added to the stable > repository. It's 1. The stable branch vdsm is clearly better from the one shipped in 3.5.0. I've tagged v4.16.9 for this occasion. Yaniv, can you build an official ovirt build from this tag? ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Question about emulating ARM using oVirt
On 12/11/2014 06:16 AM, Richard Chapman wrote: Hi and just wanted to say love oVirt. I’m using oVirt 3.5 on Fedora20 to help with are devel/testing needs. Are software runs on top of Linux both in Intel and ARM platforms. While oVirt can handle very well the intel side of things I still need to run everything on ARM on real hardware. What I’m wondering is there a plan to support at least ARM emulation using QEMU now libVirt has been fixed. Thank Chapman…. I can't say there is a real plan to do so at this point, but it shouldn't block you from writing a custom hook changing the xml we pass to libvirt to envoke qemu-kvm with arm instead of qemu-kvm. you can (ab)use maybe some existing behaviors/properties, as well as add more of your own via custom properties (and for fancy - custom ui plugins to show those custom properties in the proper dialogs) I'd say that's a good start to adding such support as an add-on, before considering it in the main code base. that's actually how we sometime develop a new feature - first "try it for sanity" via a custom hook to understand its scope and the issues. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] Feature review: Cluster parameters override
Hi, Cluster parameters override[1] has been targeted to 3.6.0. Can you please provide - A contingency plan in case the feature won't be ready - A brief text which will be used in release notes - A section with links to test cases or a description of the testing required for validating the feature? [1] http://www.ovirt.org/Features/Cluster_parameters_override Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] 3.5.1 RC schedule [was Re: [ovirt-users] oVirt Weekly Sync Meeting: Dec. 10, 2014]
Il 11/12/2014 10:45, Dan Kenigsberg ha scritto: > On Thu, Dec 11, 2014 at 08:36:46AM +0100, Sandro Bonazzola wrote: >> Il 10/12/2014 16:54, Brian Proffitt ha scritto: >>> (On time this week!) >>> >>> = >>> #ovirt: oVirt Weekly Sync >>> = >> >> [cut] >> >>> * 3.5.z updates Two blockers have postponed RC again. New RC date will >>> be discussed and decided in mailing list. (bkp, 15:30:01) >> >> [cut] >> >> Let's start the discussion and decision task. >> We have an ETA on the last pending blocker for 3.5.1 on next week. >> I suggest to postpone RC and GA after winter holidays. >> >> What about: >> RC - 2015-01-07 >> GA - 2015-01-14 > > Can we have a vdsm respin before that? We get repeated reports of bugs > that are already solved in the stable branch. > Can you elaborate on what's the request? 1) have a VDSM async release which should go in http://resources.ovirt.org/pub/ovirt-3.5/ as stable release 2) have a "beta" in http://resources.ovirt.org/pub/ovirt-3.5-pre taking latest snapshot If the request is 1, please provide the RPMs to be added to the stable repository. If the request is 2, I can't see the added value from just enabling nightly 3.5 snapshot, run 'yum update "vdsm*"' and disable it. I assume that not having replies to above dates other than this vdsm early release request means all the other agree with the proposed date. Updating the calendar accordingly. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
