<div dir="ltr">does the broker automatically sync the change you made in /etc/ovirt-hosted-engine/hosted-engine.conf to the other ha hosts or did you omit a step?<div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 6 November 2014 11:10, Groten, Ryan <span dir="ltr"><<a href="mailto:Ryan.Groten@stantec.com" target="_blank">Ryan.Groten@stantec.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I went through this a couple months ago. Migrated my hosted-engine from one NFS host to another. Here are the steps that I documented from the experience. There is probably a better way, but this worked for me on two separate hosted-engine environments.<br>
<br>
1. Make a backup of RHEV-M<br>
2. Migrate VMs off all hosts that run hosted-engine (except hosted-engine itself)<br>
3. Put hosted-engine hosts in maintenance mode (except host that's running hosted-engine)<br>
4. Put hosted-engine in global maintenance mode<br>
5. Shutdown hosted-engine<br>
6. Stop ovirt-ha-agent and ovirt-ha-broker services on all hosted-engine hosts<br>
7. On each hosted-engine host:<br>
a. service ovirt-ha-agent stop<br>
b. service ovirt-ha-broker stop<br>
c. sanlock client shutdown -f 1<br>
d. service sanlock stop<br>
e. umount /rhev/data-center/mnt/<hosted-engine-share><br>
f. service sanlock start<br>
8. mount new NFS share on /hosted_tgt<br>
9. mount old NFS share on /hosted_src<br>
10. Copy data (make sure sparse files are kept sparse):<br>
a. rsync --sparse -crvlp /hosted_src/* /hosted_tgt/<br>
11. Edit /etc/ovirt-hosted-engine/hosted-engine.conf and change path:<br>
storage=10.1.208.122:/HostedEngine_Test<br>
12. Make sure permissions are vdsm:kvm in /hosted_tgt/<br>
13. umount /hosted_tgt<br>
14. umount /hosted_src<br>
15. Pick one hosted-engine host and reboot, then run:<br>
a. hosted-engine --connect-storage (make sure the new NFS is mounted properly)<br>
b. hosted-engine --start-pool (wait a few seconds then try again if you get an error)<br>
c. service ovirt-ha-broker start<br>
d. service ovirt-ha-agent start<br>
e. hosted-engine --vm-start<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
-----Original Message-----<br>
From: <a href="mailto:users-bounces@ovirt.org">users-bounces@ovirt.org</a> [mailto:<a href="mailto:users-bounces@ovirt.org">users-bounces@ovirt.org</a>] On Behalf Of Frank Wall<br>
Sent: November-06-14 8:12 AM<br>
To: Jiri Moskovcak<br>
Cc: users<br>
Subject: Re: [ovirt-users] hosted engine , how to make changes to the VM post deploy<br>
<br>
On Wed, Nov 05, 2014 at 08:11:39AM +0100, Jiri Moskovcak wrote:<br>
> On 11/04/2014 03:52 PM, Alastair Neil wrote:<br>
> > So is this the workflow?<br>
> ><br>
> > set the hosted-engine maintenance to global<br>
> > shutdown the engine VM<br>
> > make changes via virsh or editing vm.conf<br>
> > sync changes to the other ha nodes<br>
> > restart the VM<br>
> > set hosted-engine maintenance to none<br>
><br>
> - well, not official, because it can cause a lot of troubles, so I<br>
> would not recommend it unless you have a really good reason to do it.<br>
<br>
I'd like to move my ovirt-engine VM to a new NFS storage.<br>
I was thinking to adopt this workflow for this use-case (in combination with rsync to mirror the old storage).<br>
<br>
Do you think this would succeed or is there another (and maybe "supported") way to move ovirt-engine to a different storage?<br>
<br>
<br>
Regards<br>
- Frank<br>
</div></div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>