<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Century Gothic";
panose-1:2 11 5 2 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
mso-fareast-language:EN-CA;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Century Gothic","sans-serif";
color:blue;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-CA link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Century Gothic","sans-serif";color:blue'>Good catch, you’re right that should say “On all hosted-engine hosts, edit hosted-engine.conf”. It does not automatically sync the changes between the hosts.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Century Gothic","sans-serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Alastair Neil [mailto:ajneil.tech@gmail.com] <br><b>Sent:</b> November-06-14 11:06 AM<br><b>To:</b> Groten, Ryan<br><b>Cc:</b> Frank Wall; Jiri Moskovcak; users<br><b>Subject:</b> Re: [ovirt-users] hosted engine , how to make changes to the VM post deploy<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>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?<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On 6 November 2014 11:10, Groten, Ryan <<a href="mailto:Ryan.Groten@stantec.com" target="_blank">Ryan.Groten@stantec.com</a>> wrote:<o:p></o:p></p><p class=MsoNormal>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. <span style='color:blue'>On all hosted-engine hosts, e</span>dit /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<o:p></o:p></p><div><div><p class=MsoNormal><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<o:p></o:p></p></div></div><div><div><p class=MsoNormal>_______________________________________________<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><o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>