[ovirt-users] Migrating oVirt cluster from 4.0 to 4.1

[Tomas Jelinek]

On Mon, Jun 12, 2017 at 6:30 PM, Pavel Gashev <Pax at acronis.com> wrote:

> Tomas,
>
>
>
> Since the restart is not actually required in my case, what if I set
> compatibility version in the DB directly to make the engine happy?
>

that's a nasty hack...


>
>
> I have no plans to restart my VMs in this year. And I don’t want to block
> online updating of VM parameters by the “next run configuration”.
>

By online updating you mean hotplug? Or just normal update of fields which
don't need restart (like description)? Because both are possible even with
a next run snapshot.


>
>
>
>
> *From: *Tomas Jelinek <tjelinek at redhat.com>
> *Date: *Monday, 12 June 2017 at 16:42
> *To: *Pavel Gashev <Pax at acronis.com>
> *Cc: *James <james at jloh.co>, users <users at ovirt.org>
>
> *Subject: *Re: [ovirt-users] Migrating oVirt cluster from 4.0 to 4.1
>
>
>
>
>
>
>
> On Mon, Jun 12, 2017 at 2:12 PM, Pavel Gashev <Pax at acronis.com> wrote:
>
> Can I update VMs compatibility version without restarting VMs?
>
>
>
> yes, but it will be applied only after restart.
>
>
>
>
>
> According to the source code, restarting is required during upgrading to
> 4.1 only if a VM uses random generator device. If it doesn’t, a restart is
> not really required.
>
>
>
> right, but the VM will still be marked with this "next run configuration"
> and will be set to have the old compatibility version.
>
>
>
>
>
>
>
> *From: *<users-bounces at ovirt.org> on behalf of Tomas Jelinek <
> tjelinek at redhat.com>
> *Date: *Monday, 12 June 2017 at 14:15
> *To: *James <james at jloh.co>
> *Cc: *users <users at ovirt.org>
> *Subject: *Re: [ovirt-users] Migrating oVirt cluster from 4.0 to 4.1
>
>
>
>
>
>
>
> On Mon, Jun 12, 2017 at 12:17 PM, James <james at jloh.co> wrote:
>
> We recently moved our oVirt cluster from 4.0 to 4.1 and have migrated
> all the hosts. The datacenter currently has a compatability setting of
> 4.1 but the cluster is still on 4.0. As cross-cluster migrations has
> been removed (no option anymore?) we aren't 100% sure how to get the
> cluster onto 4.1 whilst keeping the VMs online. Do we just change the
> compatibility version live and it "just works" or do we have to have
> downtime?
>
>
>
> yes, you just change the compatibility version. The VMs which are down
> will be automatically updated and work with the new cluster, the running
> ones will be marked with a "triangle" icon and will be automatically
> updated on restart of them.
>
>
>
>
> Any info would be great!
>
> Regards,
> James
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170614/013dc843/attachment.html>