On Sun, Sep 18, 2022 at 4:10 AM David White via Users <users@ovirt.org> wrote: > > I thought I'd report back to the list and mention that I was successful in > migrating off of the hyperconverged environment onto a stand-alone engine > environment, and Gluster has been removed from the oVirt configuration.
Thanks for the report. > > I ran into a few minor hiccups, all of which were resolved fairly easily, and > I took notes. I intend to submit a PR to the github documentation, since none > currently exist for migrating the engine off of a hyperconverged environment. > > My only remaining questions at this point is: > > Are there things on the hosts themselves that I should cleanup? You might want to reinstall them from scratch, one-by-one, if you care that much about them being clean. I personally do not think it's worth it if your only reason is getting rid of hosted-engine remains, but you might want to do this regardless for other reasons (e.g. if they are old machines and accumulated other kinds of cruft). > I noticed that the "hosted-engine" command still exists. I went to run a yum > remove on that, and it tried to remove basically everything... You can try 'dnf remove --noautoremove ovirt-hosted-engine-setup ovirt-hosted-engine-ha'. This will remove also 'ovirt-host', which is not such a good idea - it's a package that has no content, other than a list of dependencies, on the various packages needed for a functional oVirt host. Nothing will be broken immediately, but in principle you risk losing new deps added to a future version of it, etc. > so I figured that wasn't actually a good idea. > > Do I need to do anything in the oVirt config (maybe something in the Postgres > database) to basically tell it that it is no longer self-hosted, but is > instead stand-alone? I do not know all the details, sorry. You might want to deploy a hosted-engine, dump the engine db, then search the dump for 'hosted' or something like that. Even checking a dump of a standalone engine can show you relevant stuff to check. One item I do know about is how to prevent 'engine-setup' from preventing you from continuing because it thinks it's a hosted-engine and not in global maintenance: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/SKGWY5ZIBAG5GTWHIPDUO5O64PUZN7Y2/ There is also the field 'hosted_engine_configured' in 'vds_dynamic', not sure it's safe to change it outside of the engine (but no idea why it might not be). Good luck and best regards, > > > Sent with Proton Mail secure email. > > ------- Original Message ------- > On Friday, August 19th, 2022 at 11:01 AM, David White via Users > <users@ovirt.org> wrote: > > Hi Paul, > Thanks for the response. > > I think you're suggesting that I take a hybrid approach, and do a restore of > the current Engine onto the new VM. I hadn't thought about this option. > > Essentially what I was considering was either: > > Export to OVA or something > OR > Build a completely new oVirt engine with a completely new domain, etc... and > try to live migrate the VMs from the old engine to the new engine. > > > Do I understand you correctly that you're suggesting I install the OS onto a > new VM, and try to do a restore of the oVirt settings onto the new VM (after > I put the cluster into Global maintenance mode and shutdown the old oVirt)? > > Sent with Proton Mail secure email. > > ------- Original Message ------- > On Friday, August 19th, 2022 at 10:46 AM, Staniforth, Paul > <p.stanifo...@leedsbeckett.ac.uk> wrote: > > Hello David, > I don't think there's a documentated method to go from > a Hosted Engine to standalone just the other way standalone to HE. > > I would suggest doing a full backup of the engine prepare the new VM and > restore to that rather than trying to export it. > This way you can shut down the original engine and run the new engine VM to > test it works as you will be able to restart the original engine if it > doesn't work. > > Regards, > Paul S. > > > > ________________________________ > From: David White via Users <users@ovirt.org> > Sent: 19 August 2022 15:27 > To: David White <dmwhite...@protonmail.com> > Cc: oVirt Users <users@ovirt.org> > Subject: [ovirt-users] Re: Should I migrate existing oVirt Engine, or deploy > new? > > > Caution External Mail: Do not click any links or open any attachments unless > you trust the sender and know that the content is safe. > > In other words, I want to migrate the Engine from a hyperconverged > environment into a stand-alone setup. > > Sent with Proton Mail secure email. > > ------- Original Message ------- > On Friday, August 19th, 2022 at 10:17 AM, David White via Users > <users@ovirt.org> wrote: > > Hello, > I have just purchased a Synology SA3400 which I plan to use for my oVirt > storage domain(s) going forward. I'm currently using Gluster storage in a > hyperconverged environment. > > My goal now is to: > > Use the Synology Virtual Machine manager to host the oVirt Engine on the > Synology > Setup NFS storage on the Synology as the storage domain for all VMs in our > environment > Migrate all VM storage onto the new NFS domain > Get rid of Gluster > > > My first step is to migrate the oVirt Engine off of Gluster storage / off the > Hyperconverged hosts into the Synology Virtual Machine manager. > > Is it possible to migrate the existing oVirt Engine (put the cluster into > Global Maintenance Mode, shutdown oVirt, export to VDI or something, and then > import into Synology's virtualization)? Or would it be better for me to > install a completely new Engine, and then somehow migrate all of the VMs from > the old engine into the new engine? > > Thanks, > David > > Sent with Proton Mail secure email. > > > To view the terms under which this email is distributed, please go to:- > https://leedsbeckett.ac.uk/disclaimer/email > > > > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@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/APQ3XBUM34TG76XGRBV6GIW62RP6MZOD/ -- Didi _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@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/MA33ILLG3IGDDXZRHCXYVKLZHIH4L7UZ/
