[ovirt-users] qemu-kvm-rhev on EL machines for oVirt 3.4.z ?

[Allon Mureinik]

----- Original Message -----

> From: "Gianluca Cecchi" <gianluca.cecchi at gmail.com>
> To: "Sven Kieske" <s.kieske at mittwald.de>
> Cc: "Allon Mureinik" <amureini at redhat.com>, "users" <users at ovirt.org>
> Sent: Wednesday, September 10, 2014 10:57:27 AM
> Subject: Re: [ovirt-users] qemu-kvm-rhev on EL machines for oVirt 3.4.z ?

> On Wed, Sep 10, 2014 at 9:44 AM, Sven Kieske < s.kieske at mittwald.de > wrote:

> > > In the discussion on the patch [3], Dan raised the concern that 3.4.z is
> > > a
> > > mature z-stream, and adding this dependency on resources.ovirt.org 's
> > > repos will effectively blocks all vdsm updates for users which don't have
> > > these repos enabled in their production environments.
> 

> > I'm sorry but I don't understand this.
> 

> Hello,
> I directly put here what I see Dan wrote in the link provided and that it
> seemed to me more a warning than a blocker.. (eventually he may add further
> content...)

> "

> Patch Set 2:

> I'm not sure that this is a good idea for a mature z-stream. If someone has
> installed ovirt-3.4 without enabling the resource.ovirt.org 's repos, this
> patch effectively blocks all vdsm updates for him.

> If we really want this in ovirt-3.4.4, please explain why and warn about the
> downsides on users at ovirt.org .
> "

> I don't completely understand too...
> How could one have installed 3.4 without enabling resource.ovirt.org 's
> repos?
> Afaik the most of us who used EL 6 for their infra, then in soe way installed
> the rhev qemu-kvm package or desired/asked to do so in some way...

> So I think that is this is clearly stated on release notes there should be no
> particular problem.

> Gianluca

If we decide to move forward with this patch, we'll definitely provide qemu-kvm-rhev in the repo - the concern was indeed for users who don't have this enabled. 
Unlike 3.5, the 3.4.z repo doesn't seem to provide any "3rd parties" that can't be built from oVirt's sources - so, theoretically, it can be installed without the repo enabled - and the discussion here is whether this is an interesting usecase or not. 

My personal tendency is to go forward (with a release note, as suggested), but as noted, there is some disagreement (e.g., Dan's comment), so we're looking for additional opinions. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140910/6d1257e5/attachment-0001.html>