Help installing oVirt on single machine, without cockpit
Have you thought about deploying HostedEngine and when you need to update
The reply button is taking me to a "mailto" tab again, but hopefully making the subject the same, will put this under the right thread? If not, I'm not sure how to reply on the new system. The original thread is here: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/3L6EVRT4YBEJOIW..., and it continues here for a bit: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/C4Z65RXLFPOCS6O... . @Strahil Nikolov the engine -> put the host in maintenance -> backup & restore The way I understand the update process, you can't update with a hosted engine unless you have two hosts. One needs to run the engine VM, so the other can go into maintenance. Is this wrong? For my use case, I'm looking for something that'll work/update on a single host. I'm trying to get the engine running next to the hypervisor, so it can run when the VM's come down. I can get the engine running on a CentOS Stream install, but it says it has 0/0 hosts running, so I don't think it can deploy VM's. I can't find a way to install the node's hypervisor package-set either. Unless that package exists, the only other idea I have for this route is doing a "hosted engine" install, but destroy the engine VM and point it to the local engine. This seems extreme to me lol. I tried setting up the engine on a node itself, but the error I can't get past yet is in the second url, top of this message. It can't start the ovirt-imageio service, because of a missing file. Happy Holidays all! Cameron
Strahil's suggestion is to use the backup and restore function of the ovirt engine by essentially putting host into maintenance i.e. shutting down all VMs and the hosted engine, upgrading the host using the repositories to the latest ovirt version and then deploying the new version hosted engine 'as new' but restoring from previous version backup. This may fall apart if there's a backup incompatibility between 2 versions but minor versions would be OK. ------ Original Message ------ From: "Cameron Showalter" <cameronsplaze222@gmail.com> To: users@ovirt.org Sent: 27/12/2021 5:38:17 PM Subject: [ovirt-users] Help installing oVirt on single machine, without cockpit
The reply button is taking me to a "mailto" tab again, but hopefully making the subject the same, will put this under the right thread? If not, I'm not sure how to reply on the new system. The original thread is here: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/3L6EVRT4YBEJOIW..., and it continues here for a bit: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/C4Z65RXLFPOCS6O....
@Strahil Nikolov
Have you thought about deploying HostedEngine and when you need to update the engine -> put the host in maintenance -> backup & restore
The way I understand the update process, you can't update with a hosted engine unless you have two hosts. One needs to run the engine VM, so the other can go into maintenance. Is this wrong? For my use case, I'm looking for something that'll work/update on a single host.
I'm trying to get the engine running next to the hypervisor, so it can run when the VM's come down. I can get the engine running on a CentOS Stream install, but it says it has 0/0 hosts running, so I don't think it can deploy VM's. I can't find a way to install the node's hypervisor package-set either. Unless that package exists, the only other idea I have for this route is doing a "hosted engine" install, but destroy the engine VM and point it to the local engine. This seems extreme to me lol.
I tried setting up the engine on a node itself, but the error I can't get past yet is in the second url, top of this message. It can't start the ovirt-imageio service, because of a missing file.
Happy Holidays all! Cameron
Well, you can shut down the engine (don't forget the global maintenance), yum update, reboot -> the host is updated Then wait for ovirt-ha-agent & ovirt-ha-broker to bring the engine up.Global maintenance, wipe the storage (assuming NFS/GlusterFS is used) or at least rename the subdirectory to something different.Restore from backup and it should be back as new. Best Regards,Strahil Nikolov On Tue, Dec 28, 2021 at 0:27, Joseph Goldman<joseph@goldman.id.au> wrote: _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SZWVLPZDESDW24...
The migration from 4.3 to 4.4 is done by the same method... It always worked but for major version upgrade there is a strict requirement which version the backup was done. Even if it doesn't work - a fresh engine can still recover the VMs by importing the storage domain (no VM snapshots are allowed), yet other settings might be lost (VM networks, users,etc) Also, I forgot to mention that with GlusterFS, you can create a snapshot as a point in time recovery (shut down the engine first as it has a DB) on the Engine's volume. Happy Holidays! Best Regards,Strahil Nikolov On Fri, Dec 31, 2021 at 2:33, Strahil Nikolov<hunter86_bg@yahoo.com> wrote: Well, you can shut down the engine (don't forget the global maintenance), yum update, reboot -> the host is updated Then wait for ovirt-ha-agent & ovirt-ha-broker to bring the engine up.Global maintenance, wipe the storage (assuming NFS/GlusterFS is used) or at least rename the subdirectory to something different.Restore from backup and it should be back as new. Best Regards,Strahil Nikolov On Tue, Dec 28, 2021 at 0:27, Joseph Goldman<joseph@goldman.id.au> wrote: _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SZWVLPZDESDW24...
On Fri, Dec 31, 2021 at 2:40 AM Strahil Nikolov via Users <users@ovirt.org> wrote:
The migration from 4.3 to 4.4 is done by the same method... It always worked but for major version upgrade there is a strict requirement which version the backup was done.
A small clarification: engine-backup's backup/restore never intended to support, let's call this, "functional downgrade" - restoring to a version older than the one used for backup. For a long time, it supported only restoring to the same X.Y, ignoring Z. In 3.6->4.0 and 4.3->4.4 we also patched it to allow, as you mention, upgrading, as a means to migrate to a new OS version. It's quite likely we'll do the same in 4.4->4.5, because we plan to support also CentOS Stream 9. At some point in 4.4, we noticed that upgrading from a too-old 4.3 is broken, so we also patched it to require a minimal 4.3 (4.3.10). But until quite recently, downgrade inside the same X.Y was not prevented. See also: https://bugzilla.redhat.com/show_bug.cgi?id=1932392 Best regards,
Even if it doesn't work - a fresh engine can still recover the VMs by importing the storage domain (no VM snapshots are allowed), yet other settings might be lost (VM networks, users,etc)
Also, I forgot to mention that with GlusterFS, you can create a snapshot as a point in time recovery (shut down the engine first as it has a DB) on the Engine's volume.
Happy Holidays!
Best Regards, Strahil Nikolov
On Fri, Dec 31, 2021 at 2:33, Strahil Nikolov <hunter86_bg@yahoo.com> wrote: Well, you can shut down the engine (don't forget the global maintenance), yum update, reboot -> the host is updated
Then wait for ovirt-ha-agent & ovirt-ha-broker to bring the engine up. Global maintenance, wipe the storage (assuming NFS/GlusterFS is used) or at least rename the subdirectory to something different. Restore from backup and it should be back as new.
Best Regards, Strahil Nikolov
On Tue, Dec 28, 2021 at 0:27, Joseph Goldman <joseph@goldman.id.au> wrote: _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SZWVLPZDESDW24...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FVFKEMSGQEMVOU...
-- Didi
participants (4)
-
Cameron Showalter -
Joseph Goldman -
Strahil Nikolov -
Yedidyah Bar David