[Users] Lifecycle / upgradepath

[Dave Neary]

Hi Sven,

On 02/06/2014 09:42 AM, Sven Kieske wrote:
> Currently, there is no single document describing supported
> (which means: working ) upgrade scenarios.

There are multiple documents which, together, do that, however.

This documents the move from 3.2 on F18 to 3.3 on F19:
http://www.ovirt.org/OVirt_3.2_to_3.3_upgrade

The same principle applies for a move from CentOS 6.4/oVirt 3.2 to
CentOS 6.5/oVirt 3.3 (except replace fedup with the CentOS equivalent,
which I don't know).

This one concentrates on updating the database in-place:
http://www.ovirt.org/OVirt-database-upgrade-procedure

> As far as I know, currently it is supported to upgrade
> from x.y.z to x.y.z+1 and from x.y.z to x.y+1.z
> but not from x.y-1.z to x.y+1.z directly.

Both should be possible. "supported" is a tricky word to use here
(because "support" means something special for RHEV).

> maybe this should be put together in a wiki page at least.
> 
> also it would be cool to know how long a single "release"
> would be supported.

Again, support is a tricky word. We do not maintain older oVirt 3.x
releases when the new one comes out, although we typically make a bug
fix release for the previous version when the latest version comes out.

> In this context I would define a release as a version
> bump from x.y.z to x.y+1.z or to x+1.y.z
> a bump in z would be a bugfix release.
> 
> The question is, how long will we get bugfix releases
> for a given version?

They stop, as I understand it, when we move to the next minor version.
(that is, y to y+1). We have not had a major release since my time in
oVirt, so I don't know if we will continue bug fix releases on the
stable branch when there is a major version upgrade.

Cheers,
Dave.

-- 
Dave Neary - Community Action and Impact
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13