----- Original Message -----
> From: "Fabian Deutsch" <fabi...@redhat.com>
> To: "Barak Azulay" <bazu...@redhat.com>
> Cc: arch@ovirt.org, "node-devel" <node-de...@ovirt.org>, "Douglas Landgraf"
> <dland...@redhat.com>
> Sent: Monday, March 31, 2014 9:39:55 AM
> Subject: Re: [node-devel] Versioning of oVirt Node
>
> Am Sonntag, den 30.03.2014, 04:46 -0400 schrieb Barak Azulay:
> > I assume that this new schema is handling also the frist upgrade from
> > the old name schema.
>
> Hey Barak,
>
> could you explain what the first upgrade to the old schema name was for
> you?
There are 2 scenarios that needs to be considered:
1 older engine with new rhevh (with new name schema)
* customer with rhev 3.4 tries to upgrade a 3.4 cluster level rhevh to the
latest rhevh (with new name schema ... 3.4 cluster level)
2 newer engine supporting older clustrers:
* assume you have 3.4 engine out with several ISOs located in the same dir,
Than there is an upgrade to 3.5 where the name schema changes (and in the
same dir you have old name schema and new name schema),
Than you want to upgrade a 3.4 cluster level rhevh to the latest rhevh
(with new name schema ... 3.4 cluster level)
In both cases the UI should suggest the best fit for upgrade,
While for #2 we can add some logic to the engine to handle both cases (ugly and
problematic),
For #1 above there is very little we can do.
>
> - fabian
>
_______________________________________________
Arch mailing list
Arch@ovirt.org
http://lists.ovirt.org/mailman/listinfo/arch
