[node-devel] Versioning of oVirt Node

[Alon Bar-Lev]

----- Original Message -----
> From: "Fabian Deutsch" <fabiand at redhat.com>
> To: "Alon Bar-Lev" <alonbl at redhat.com>
> Cc: arch at ovirt.org, "node-devel" <node-devel at ovirt.org>, "Douglas Landgraf" <dlandgra at redhat.com>
> Sent: Thursday, April 3, 2014 12:45:25 PM
> Subject: Re: [node-devel] Versioning of oVirt Node
> 
> Am Donnerstag, den 03.04.2014, 05:41 -0400 schrieb Alon Bar-Lev:

<snip>

> > 
> > > > > 
> > > > > > Released:
> > > > > > ovirt-node-iso-3.4.z-1.dist.rpm
> > > > > 
> > > > > would you replase z in that string above?
> > > > 
> > > > Each stable release/fix release you issue z is incremented async of
> > > > any other package.
> > > > 
> > > > > 
> > > > > > Please note that the downstream component is eliminated in
> > > > upstream,
> > > > > 
> > > > > Could you please exaplain this a bit more.
> > > > 
> > > > You wrote:
> > > > 
> > > > > > >
> > > > ovirt-node-iso-<ovirt-target-version>-<build-date>.<number>.<dist>.iso
> > > > 
> > > > This means that you have no upstream version for your own use...
> > > > ovirt-target-version is of ovirt, but what is the version of the node?
> > > 
> > > Oh right. Well the "node" version can be retrieved by looking at the
> > > version of the contained ovirt-node pkg. We don't need to expose it in
> > > the name.
> > > 
> > > That's actually what I want to avoid - to expose the node version -
> > > because this isn't helpful to th euser - even worse - it is confusing.
> > 
> > On the contrary... the node version is the part that is important, this is
> > the upstream version of the component, and should not be hidden.
> 
> We keep the version for the "real" component which is the ovirt-node
> package.
> Further more we could say that the ovirt-node-iso component is a
> component on it's own with it's own version.

Component version that builds the output is important.
As a change in that component will result in different output.
So there must be a trace for that version.

> Because the ISO is squashing many packages I don't see a hard reason why
> it should have the version of the ovirt-node package.
> And my suggestion is to let the ovirt-node-iso component follow the
> overall/project version.

The version of the process that builds is important, for example, let's say you build an image using component-v1, then build another image using component-v2, now, you find a severe bug in component-v1 and want to fix only this bug and release component-v1.1, how can you do this, how can you know that you have component-v1, component-v2, component-v1.1 is v1.1 > v2 ?

> For us "No(o)dlers"" it would be interesting to see the ovirt-node
> version.
> For "vdsmlers" the vdsm version would be interesting.
> But to the consumer the oVirt version for which it cna be used is
> probably the most interesting - after all it should be a black box ;)

Even a black box should have a version to enable proper release engineering... There must be a way to trace back a component from output to source, and be able to rebuild it to produce the exact output. This is required so that this "black box" may fixed, bugs may be assigned to right version, bug will be resolved at right version etc...

Alon