[ovirt-devel] VDSM mom dependancy on RHEL7

[Adam Litke]

On 23/07/14 13:18 +0100, Dan Kenigsberg wrote:
>On Wed, Jul 23, 2014 at 07:05:07AM -0400, Martin Polednik wrote:
>> ----- Original Message -----
>> > From: "Dan Kenigsberg" <danken at redhat.com>
>> > To: "Martin Polednik" <mpolednik at redhat.com>, dcaro at redhat.com
>> > Cc: devel at ovirt.org
>> > Sent: Wednesday, July 23, 2014 12:19:42 PM
>> > Subject: Re: [ovirt-devel] VDSM mom dependancy on RHEL7
>> >
>> > On Tue, Jul 22, 2014 at 06:36:10PM -0400, Martin Polednik wrote:
>> > > Hi,
>> > >
>> > > I've gone through installing VDSM on RHEL7 host
>> > > (Red Hat Enterprise Linux Server release 7.0 (Maipo)) and encountered
>> > > issue with mom:
>> > >
>> > > Error: Package: mom-0.4.1-2.el6.noarch (ovirt-3.5-epel)
>> > >            Requires: python(abi) = 2.6
>> > >            Installed: python-2.7.5-16.el7.x86_64 (@rhel7)
>> > >                python(abi) = 2.7
>> > >                python(abi) = 2.7
>> > >
>> > > Repositories used were master, master-snapshots and 3.5 + dependancies.
>> > > Although it is possible to get it working by getting mom source and
>> > > rebuilding it on RHEL7, I'd like to know if there is different RHEL7
>> > > repo or this is mistake in repos.
>> >
>> > http://resources.ovirt.org/pub/ovirt-3.5-pre/rpm/el7/ is quite empty,
>> > I'm afraid.
>>
>> The problem actually occurs when getting mom from
>> http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/
>
>mom there
>http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/noarch/mom-0.4.1-0.0.master.20140718.gitfcedb2d.el7.noarch.rpm
>is of older version than the one in your ovirt-3.5-epel
>(mom-0.4.1-2.el6.noarch). Try disabling ovirt-3.5-epel repo.
>
>Since el6->el7 upgrade should be possible, el7 packages must have a
>higher n-v-r than their el6 diblings.

Who is the person that is actually building the mom rpms for the
release?  It's actually not me :)  I am actually a bit confused about
how to handle this.  Since mom is actually an upstream project that is
used by people outside of oVirt releases, I have been maintaining
upstream packages in Fedora/epel.  We haven't really encountered a
situation where oVirt needs to ship something different than what is
upstream (but this may come to pass in the future).  A couple of
questions...

1) Should we even be building mom in the ovirt repos at all?

2) If we need to ensure a smooth upgrade between el6 and el7, does
this mean that I need to bump the el7 version every time I upgrade the
el6 packages?  This seems strange to me.  I think the better solution
is to not require a specific version of python (2.6, 2.7, etc) but
just < 3 until we support python3.

3) We should probably make vdsm depend on a specific version of MOM.
That way we can upgrade the fedora package but have an ovirt host stay
on a current stabilized version.

>_______________________________________________
>Devel mailing list
>Devel at ovirt.org
>http://lists.ovirt.org/mailman/listinfo/devel

-- 
Adam Litke