[Users] no new mom for ovirt?

Thu Jan 23 07:31:09 UTC 2014

Hi Sven,

Adam already described the status pretty weel, but I have one remark.

Please note that the oVirt release of mom has .git<hash> in its release string. It is true that the release number itself is lower, but the RPM actually contains the same or even newer features than the RHEV package (.el6ev).

If you check the packaging guidelines and the version string semantics, you will find out that the NVR as we call it is: <name>-<version>-<release>. Name is obvious, but the relationship between version and release is this:

- version is the base version of _upstream_tarball_ that was used to create the package (both packages you mentioned have 0.3.2)
- release is distribution specific string (all Fedora, oVirt, RHEV have their own _independent_ sequence) that is increased any time there is a change to the _spec_ file for that distribution, it also usually identifies the distribution using the .dist suffix

So when we freeze the version of upstream for a specific distribution, we then add patches to the spec file without modifying the base upstream tarball with sources. That is why the RHEV package has -8 as the release number.

So in an ideal world the release and packaging situation looks like this:

upstream release: mom-0.3.2.tar.gz (distribution agnostic tarball with sources, if there is .gitXYZ it should be part of the version here)
Fedora rpm: mom-0.3.2-X.f20 (version based on upstream, release according to the needs of Fedora)
EPEL rpm: mom-0.3.2-X.el6 (version based on upstream, release according to the needs of Fedora)
RHEV rpm: mom-0.3.2-Y.el6ev (version based on upstream, release according to the needs of RHEV)
oVirt rpms: ideally it should use the packages that were built using the proper distribution build process..

Unfortunately oVirt sometimes needs newer version of some dependencies than what are available in the distributions we build our packages for, so we have to use our own repositories and that causes confusion in versioning. What we should do is to always bump only the version and keep the release as "-1". But mom did not do it like that and I think that is what Adam was trying to solve for the past couple of days now.

I hope this cleared the confusion a bit.

Short summary :) -- Please do not mix version and release as release is distribution specific number and can't be compared to packages for other distributions.

--
Martin Sivák
msivak at redhat.com
Red Hat Czech
RHEV-M SLA / Brno, CZ

----- Original Message -----
> On 22/01/14 17:15 +0000, Sven Kieske wrote:
> >Hi,
> >
> >thanks for the exhaustive answer again.
> >
> >But is the mom release all?
> >
> >are the related changes to the
> >guest agent and to vdsm also released?
> >
> >in which version?
> >Also I think this:
> >http://rhn.redhat.com/errata/RHEA-2014-0064.html
> >
> >is incorrect, as it states that this is fixed
> >in the mom release, but it isn't.
> >
> >it relies on swap information from guest-agent
> >which also needs an upgrade (if the guest has swap
> >configured).
> >
> >I think there is some lack of documentation
> >around this.
> >
> >Which version of vdsm and guest agent do you
> >need to use this new mom?
> 
> Adding Martin who should be able to answer these questions better than
> I...
> 
> 
> >
> >Am 22.01.2014 17:52, schrieb Adam Litke:
> >> On 22/01/14 03:12 -0500, Doron Fediuck wrote:
> >>>
> >>>
> >>> ----- Original Message -----
> >>>> From: "Sven Kieske" <S.Kieske at mittwald.de>
> >>>> To: "Users at ovirt.org List" <Users at ovirt.org>
> >>>> Sent: Tuesday, January 21, 2014 6:45:10 PM
> >>>> Subject: [Users] no new mom for ovirt?
> >>>>
> >>>> Hi,
> >>>>
> >>>> I just checked this BZ:
> >>>> https://bugzilla.redhat.com/show_bug.cgi?id=1025845
> >>>>
> >>>> This is closed for RedHat but afaik not for upstream.
> >>>>
> >>>> It mentions the fixed mom version:
> >>>> mom-0.3.2-8.el6ev
> >>>>
> >>>> but on resources.ovirt.org I find just older versions
> >>>> like
> >>>> http://resources.ovirt.org/releases/3.4.0-alpha/rpm/EL/6/noarch/mom-0.3.2-3.16.git97e1741.el6.noarch.rpm
> >>>>
> >>>>
> >>>> so downstream (payed) red hat has newer versions than upstream
> >>>>
> >>>> how can that be? Or am I looking in the wrong repo?
> >>>> Should this not be hosted on ovirt.org repo?
> >>
> >> Hi Sven!  Thanks for bringing this up.  You have stumbled upon our
> >> completely broken mom build process in oVirt.  Part of the problem
> >> stems from the fact that MOM is a standalone package (available in
> >> upstream Fedora) which is being rebuilt by oVirt.  The Fedora releases
> >> have typically been much slower than the oVirt releases (and different
> >> people are doing each).  Here's what we are doing to fix the issues:
> >> - Fix the MOM build system (merged)
> >> - Create branches in the MOM repo for ovirt releases (in progress)
> >> - I will be taking responsibility for oVirt releases of MOM in
> >>   addition to the Fedora package itself.
> >>
> >> These changes should lead to a normalized release process for MOM and
> >> ensure that built packages for all supported oVirt releases will be
> >> made available on resources.ovirt.org.
> >>
> >> Up until very recently, all MOM development has been done in a single
> >> branch.  As a workaround for your issue you can build your own rpm
> >> from git (use the v0.3.2-stable tag) or grab this [1] nightly build.
> >>
> >> [1]
> >> http://resources.ovirt.org/releases/nightly/rpm/EL/6Server/noarch/mom-0.3.2-20140120.gitfd877c5.el6.noarch.rpm
> >>
> >>
> >> Sorry for all of the confusion!
> >>
> >>
> >>
> >>
> >
> >--
> >Mit freundlichen Grüßen / Regards
> >
> >Sven Kieske
> >
> >Systemadministrator
> >Mittwald CM Service GmbH & Co. KG
> >Königsberger Straße 6
> >32339 Espelkamp
> >T: +49-5772-293-100
> >F: +49-5772-293-333
> >https://www.mittwald.de
> >Geschäftsführer: Robert Meyer
> >St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
> >Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
> 