7:26 p.m.
Is it possible to have multiple engines with different versions of ovirt
running in the same cluster? I am working on a plan to upgrade our
ovirt cluster to the 4.2 release however we would like to have a
rollback plan in case there are issues with the new engine.
2 a.m.
On Wed, May 16, 2018 at 7:37 PM Michael Watters <wattersm(a)watters.ws> wrote:
Is it possible to have multiple engines with different versions of
ovirt
running in the same cluster? I am working on a plan to upgrade our
ovirt cluster to the 4.2 release however we would like to have a
rollback plan in case there are issues with the new engine.
You can run multiple engines, each on a different host (or vm). Then
you can remove entities from one engine and add them to the other.
If something goes wrong, you can move the entities back to the orignal
engine.
I think the new DR support can make this process easy and robust,
but not sure it works with older engine versions.
Adding Maor to add more info on this direction.
I think that hosted engine upgrade flow may also be useful, dumping
engine database on the old engine, and restoring it to a new engine,
and it may work better for upgrading between different versions.
Simone is the expert in this area.
Nir
9 a.m.
On Thu, May 17, 2018 at 2:00 AM, Nir Soffer <nsoffer(a)redhat.com> wrote:
On Wed, May 16, 2018 at 7:37 PM Michael Watters
<wattersm(a)watters.ws>
wrote:
> Is it possible to have multiple engines with different versions of ovirt
> running in the same cluster? I am working on a plan to upgrade our
> ovirt cluster to the 4.2 release however we would like to have a
> rollback plan in case there are issues with the new engine.
>
You can run multiple engines, each on a different host (or vm). Then
you can remove entities from one engine and add them to the other.
If something goes wrong, you can move the entities back to the orignal
engine.
I think the new DR support can make this process easy and robust,
but not sure it works with older engine versions.
DR supports engine 4.2 and above, but the usecase is a bit different than
what's described.
You can try to use replicated storage domains in the new setup, and then
try to register those VMs and upgrade them to cluster 4.2
If any problem will occur you can shutdown the hosts in the new setup and
start the old setup back again.
Adding Maor to add more info on this direction.
I think that hosted engine upgrade flow may also be useful, dumping
engine database on the old engine, and restoring it to a new engine,
and it may work better for upgrading between different versions.
Simone is the expert in this area.
Nir
4:06 p.m.
On Wed, May 16, 2018 at 7:26 PM, Michael Watters <wattersm(a)watters.ws>
wrote:
Is it possible to have multiple engines with different versions of
ovirt
running in the same cluster? I am working on a plan to upgrade our
ovirt cluster to the 4.2 release however we would like to have a
rollback plan in case there are issues with the new engine.
If this is on a production-level setup, you anyway should have a
contingency plan if anything goes bad to the engine.
I recommend automated engine setup along with regular engine backup.
You can then take a backup prior to upgrade.
Y.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
4:04 p.m.
On 05/17/2018 09:06 AM, Yaniv Kaul wrote:
On Wed, May 16, 2018 at 7:26 PM, Michael Watters <wattersm(a)watters.ws
<mailto:wattersm@watters.ws>> wrote:
Is it possible to have multiple engines with different versions of
ovirt
running in the same cluster? I am working on a plan to upgrade our
ovirt cluster to the 4.2 release however we would like to have a
rollback plan in case there are issues with the new engine.
If this is on a production-level setup, you anyway should have a
contingency plan if anything goes bad to the engine.
I recommend automated engine setup along with regular engine backup.
We run backups every night. My concern is that once ovirt 4.2 is
installed there isn't an easy way to roll back to ovirt 4.1.
5:33 p.m.
On Fri, May 18, 2018 at 4:04 PM, Michael Watters <wattersm(a)watters.ws>
wrote:
On 05/17/2018 09:06 AM, Yaniv Kaul wrote:
On Wed, May 16, 2018 at 7:26 PM, Michael Watters <wattersm(a)watters.ws>
wrote:
> Is it possible to have multiple engines with different versions of ovirt
> running in the same cluster? I am working on a plan to upgrade our
> ovirt cluster to the 4.2 release however we would like to have a
> rollback plan in case there are issues with the new engine.
>
If this is on a production-level setup, you anyway should have a
contingency plan if anything goes bad to the engine.
I recommend automated engine setup along with regular engine backup.
We run backups every night. My concern is that once ovirt 4.2 is
installed there isn't an easy way to roll back to ovirt 4.1.
Correct. Some split their whole setups for two complete system to be able
to step upgrade.
Y.
2378
days inactive
2383
days old
5 comments
4 participants
participants (4)
-
Maor Lipchuk -
Michael Watters -
Nir Soffer -
Yaniv Kaul