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.

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? 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... 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?



Sent with Proton Mail secure email.

------- Original Message -------
On Friday, August 19th, 2022 at 11:01 AM, David White via Users 
<[email protected]> 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 
> <[email protected]> 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 <[email protected]>
> > Sent: 19 August 2022 15:27
> > To: David White <[email protected]>
> > Cc: oVirt Users <[email protected]>
> > 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 
> > <[email protected]> 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

Attachment: publickey - [email protected] - 0x320CD582.asc
Description: application/pgp-keys

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]/message/APQ3XBUM34TG76XGRBV6GIW62RP6MZOD/

Reply via email to