<div dir="ltr">Hi,<div><br></div><div> It would not do that as before shutting down the engine vm we are setting maintenance mode to global. Main use is to allow the administrator to start/stop/modify the engine VM with out any worry of interference from the HA agents.</div><div><br></div><div>Thanks</div><div>kasturi</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 9, 2017 at 2:16 PM, Moacir Ferreira <span dir="ltr"><<a href="mailto:moacirferreira@hotmail.com" target="_blank">moacirferreira@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div id="m_-3788048043331502243divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif" dir="ltr">
<p>That is great Kasturi, thanks!</p>
<p><br>
</p>
<p>I will go over these steps just to make sure nothing is missing. But it looks the right way to do it. The only step that looks strange is the step 6 to shutdown. I always though that if I shutdown a HA protected machine oVirt would then launch it back again.
So in my thoughts I would do the step 6 before step 4. This said, am I missing something?<br>
</p>
<br>
Moacir<br>
<br>
<div style="color:rgb(49,55,57)">
<hr style="display:inline-block;width:98%">
<div id="m_-3788048043331502243divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Kasturi Narra <<a href="mailto:knarra@redhat.com" target="_blank">knarra@redhat.com</a>><br>
<b>Sent:</b> Wednesday, August 9, 2017 5:51 AM<br>
<b>To:</b> Moacir Ferreira<br>
<b>Cc:</b> Erekle Magradze; <a href="mailto:users@ovirt.org" target="_blank">users@ovirt.org</a><div><div class="h5"><br>
<b>Subject:</b> Re: [ovirt-users] How to shutdown an oVirt cluster with Gluster and hosted engine</div></div></font>
<div> </div>
</div><div><div class="h5">
<div>
<div dir="ltr">Hi,
<div><span style="font-size:12.8px"> You can follow the steps below to do that.</span><br>
</div>
<p style="font-size:12.8px">1) Stop all the virtual machines.<br>
</p>
<p style="font-size:12.8px">2) Move all the storage domains other than hosted_storage to maintenance which will unmount them from all the nodes.<br>
</p>
<p style="font-size:12.8px">3) Move HE to global maintenance 'hosted-engine --set-maintenance --mode =global'</p>
<p style="font-size:12.8px">4) stop HE vm by running the command 'hosted-engine --vm-shutdown'</p>
<p style="font-size:12.8px">5) confirm that engine is down using the command 'hosted-engine --vm-status'</p>
<p style="font-size:12.8px">6) stop ha agent and broker services on all the nodes by running the command 'systemctl stop ovirt-ha-broker' ; 'systemctl stop ovirt-ha-agent'</p>
<p style="font-size:12.8px">7) umount hosted-engine from all the hypervisors 'hosted-engine --disconnect-storage'</p>
<p style="font-size:12.8px">8) stop all the volumes.</p>
<p style="font-size:12.8px">9) power off all the hypervisors.</p>
<p style="font-size:12.8px"><br>
</p>
<p style="font-size:12.8px">To bring it up back again below steps will help.</p>
<p style="font-size:12.8px"><br>
</p>
<p style="font-size:12.8px">1) Power on all the hypervisors.</p>
<p style="font-size:12.8px">2) start all the volumes</p>
<p style="font-size:12.8px">3) <span style="font-size:12.8px">start ha agent and broker services on all the nodes by running the command 'systemctl start ovirt-ha-broker' ; 'systemctl start ovirt-ha-agent'</span></p>
<p style="font-size:12.8px"><span style="font-size:12.8px">4) Move hosted-engine out of global maintenance by running the command </span><span style="font-size:12.8px">hosted-engine --set-maintenance --mode =none</span></p>
<p style="font-size:12.8px"><span style="font-size:12.8px">5) give some time for the HE to come up. check for hosted-engine --vm-status to see if HE vm is up.</span></p>
<p style="font-size:12.8px"><span style="font-size:12.8px">6) Activate all storage domains from UI.</span></p>
<p style="font-size:12.8px">7) start all virtual machines.</p>
<p style="font-size:12.8px">Hope this helps !!!</p>
<p style="font-size:12.8px"><span style="font-size:12.8px">Thanks</span><br>
</p>
<p style="font-size:12.8px">kasturi.</p>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Aug 8, 2017 at 2:27 AM, Moacir Ferreira <span dir="ltr">
<<a href="mailto:moacirferreira@hotmail.com" target="_blank">moacirferreira@hotmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div id="m_-3788048043331502243m_3544374521327452776divtagdefaultwrapper" dir="ltr" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif">
<p>Sorry Erekle, I am just a beginner...</p>
<p><br>
</p>
<p>From the hosted engine I can put the two other servers, that are not hosting the hosted-engine, on maintenance, and that was what I did. When I tried to put the last one on maintenance it did not allow me due to the hosted-engine and I force it shunting
down from the ssh CLI.</p>
<p><br>
</p>
<p>So, what should I do? My guess is that I should ssh to the hosted engine and shut it down. As it would not have another node to re-launch itself, then it would stay down. After this I should shutdown the oVirt node. Is it?</p>
<p><br>
</p>
<p>Anyway, I made a mistake and I forced it. When I try to bring the cluster back, I noticed that glusterd was not enabled to start when the node power-on. As I am a beginner, I "think" that there must be a reason to not start glusterd when the node comes up.
So I started glusterd on the arbitrator (3rd server), then on the second node and finally on the host that was hosting the hosted-engine. It worked, but when I try to change the maintenance mode on the two nodes (2nd and 3rd) back to normal, the hosted-engine
went down and I had to start it manually.</p>
<p><br>
</p>
<p>All this said, I would like to know how to bring the cluster down and how to bring it back on in the "right way" so I don't get problems. And yes, no VM is running but the hosted-engine.</p>
<p><br>
</p>
<p>Thanks for sharing your knowledge.</p>
<p>Moacir<br>
</p>
<br>
<br>
<div style="color:rgb(49,55,57)">
<hr style="display:inline-block;width:98%">
<div id="m_-3788048043331502243m_3544374521327452776divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Erekle Magradze <<a href="mailto:erekle.magradze@recogizer.de" target="_blank">erekle.magradze@recogizer.de</a>><br>
<b>Sent:</b> Monday, August 7, 2017 9:12 PM<br>
<b>To:</b> Moacir Ferreira; <a href="mailto:users@ovirt.org" target="_blank">users@ovirt.org</a><br>
<b>Subject:</b> Re: [ovirt-users] How to shutdown an oVirt cluster with Gluster and hosted engine</font>
<div> </div>
</div>
<div><span>
<p>Hi Moacir,</p>
<p>First switch off all VMs.<br>
</p>
<p>Second you need to declare hosts maintenance mode, don't start with SRM (of course if you are able use the ovirt-engine), it will ask you to shutdown the glusterfs on a machine.<br>
</p>
<p>Third if all machines are in maintenance mode, you can start shutting down them.</p>
<p><br>
</p>
<p>If you have hosted engine setup follow this [1]</p>
<p><br>
</p>
<p>Cheers</p>
<p>Erekle</p>
<p><br>
</p>
<p>[1] <a class="m_-3788048043331502243m_3544374521327452776moz-txt-link-freetext" href="https://github.com/rharmonson/richtech/wiki/OSVDC-Series:-oVirt-3.6-Cluster-Shutdown-and-Startup" id="m_-3788048043331502243m_3544374521327452776LPlnk698479" target="_blank">
https://github.com/rharmonson/<wbr>richtech/wiki/OSVDC-Series:-oV<wbr>irt-3.6-Cluster-Shutdown-and-<wbr>Startup</a></p>
</span>
<div id="m_-3788048043331502243m_3544374521327452776LPBorder_GT_15021385378540.44953526762016005" style="margin-bottom:20px;overflow:auto;width:100%;text-indent:0px">
<table id="m_-3788048043331502243m_3544374521327452776LPContainer_15021385378430.1557026540095915" style="width:90%;background-color:rgb(255,255,255);overflow:auto;padding-top:20px;padding-bottom:20px;margin-top:20px;border-top:1px dotted rgb(200,200,200);border-bottom:1px dotted rgb(200,200,200)" cellspacing="0">
<tbody>
<tr style="border-spacing:0px" valign="top">
<td id="m_-3788048043331502243m_3544374521327452776ImageCell_15021385378460.2075482803057317" colspan="1" style="width:250px;display:table-cell;padding-right:20px">
<div id="m_-3788048043331502243m_3544374521327452776LPImageContainer_15021385378460.6401999319370751" style="background-color:rgb(255,255,255);height:250px;margin:auto;display:table;width:250px">
<a id="m_-3788048043331502243m_3544374521327452776LPImageAnchor_15021385378480.780110251720861" href="https://github.com/rharmonson/richtech/wiki/OSVDC-Series:-oVirt-3.6-Cluster-Shutdown-and-Startup" style="display:table-cell;text-align:center" target="_blank"><img id="m_-3788048043331502243m_3544374521327452776LPThumbnailImageID_15021385378480.309951069136171" style="display:inline-block;max-width:250px;max-height:250px;height:250px;width:250px;border-width:0px;vertical-align:bottom" width="250" height="250" src="https://avatars1.githubusercontent.com/u/7966126?v=4&s=400"></a></div>
</td>
<td id="m_-3788048043331502243m_3544374521327452776TextCell_15021385378500.42406867055408104" colspan="2" style="vertical-align:top;padding:0px;display:table-cell">
<div id="m_-3788048043331502243m_3544374521327452776LPRemovePreviewContainer_15021385378500.09648672645925471">
</div>
<div id="m_-3788048043331502243m_3544374521327452776LPTitle_15021385378500.5741607502358855" style="color:rgb(0,120,215);font-weight:400;font-size:21px;font-family:"wf_segoe-ui_light","Segoe UI Light","Segoe WP Light","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif;line-height:21px">
<a id="m_-3788048043331502243m_3544374521327452776LPUrlAnchor_15021385378510.9292682478026467" href="https://github.com/rharmonson/richtech/wiki/OSVDC-Series:-oVirt-3.6-Cluster-Shutdown-and-Startup" style="text-decoration:none" target="_blank">OSVDC Series: oVirt 3.6 Cluster Shutdown
and Startup ...</a></div>
<div id="m_-3788048043331502243m_3544374521327452776LPMetadata_15021385378520.7560393279127221" style="margin:10px 0px 16px;color:rgb(102,102,102);font-weight:400;font-family:"wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif;font-size:14px;line-height:14px">
<a href="http://github.com" target="_blank">github.com</a></div>
<div id="m_-3788048043331502243m_3544374521327452776LPDescription_15021385378530.7666884664788362" style="display:block;color:rgb(102,102,102);font-weight:400;font-family:"wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif;font-size:14px;line-height:20px;max-height:100px;overflow:hidden">
Contribute to richtech development by creating an account on GitHub.</div>
</td>
</tr>
</tbody>
</table>
</div>
<div>
<div class="m_-3788048043331502243h5"><br>
<div class="m_-3788048043331502243m_3544374521327452776moz-cite-prefix">On 08/07/2017 08:58 PM, Moacir Ferreira wrote:<br>
</div>
<blockquote type="cite">
<div id="m_-3788048043331502243m_3544374521327452776divtagdefaultwrapper" dir="ltr" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif">
<p>I have installed a oVirt cluster in a KVM virtualized test environment. Now, how do I <span>properly shutdown the oVirt cluster, with Gluster and the hosted engine</span>?</p>
<p>I.e.: I want to install a cluster of 3 servers and then send it to a remote office. How do I do it properly? I noticed that glusterd is not enabled to start automatically. And how do I deal with the hosted engine?</p>
<p><br>
</p>
<p>Thanks,<br>
</p>
<p>Moacir<br>
</p>
</div>
<br>
<fieldset class="m_-3788048043331502243m_3544374521327452776mimeAttachmentHeader"></fieldset> <br>
<pre>______________________________<wbr>_________________
Users mailing list
<a class="m_-3788048043331502243m_3544374521327452776moz-txt-link-abbreviated" href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a>
<a class="m_-3788048043331502243m_3544374521327452776moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a>
</pre>
</blockquote>
<br>
<pre class="m_-3788048043331502243m_3544374521327452776moz-signature" cols="72">--
Recogizer Group GmbH
Dr.rer.nat. Erekle Magradze
Lead Big Data Engineering & DevOps
Rheinwerkallee 2, 53227 Bonn
Tel: +49 228 29974555
E-Mail <a class="m_-3788048043331502243m_3544374521327452776moz-txt-link-abbreviated" href="mailto:erekle.magradze@recogizer.de" target="_blank">erekle.magradze@recogizer.de</a>
Web: <a class="m_-3788048043331502243m_3544374521327452776moz-txt-link-abbreviated" href="http://www.recogizer.com" target="_blank">www.recogizer.com</a>
Recogizer auf LinkedIn <a class="m_-3788048043331502243m_3544374521327452776moz-txt-link-freetext" href="https://www.linkedin.com/company-beta/10039182/" target="_blank">https://www.linkedin.com/compa<wbr>ny-beta/10039182/</a>
Folgen Sie uns auf Twitter <a class="m_-3788048043331502243m_3544374521327452776moz-txt-link-freetext" href="https://twitter.com/recogizer" target="_blank">https://twitter.com/recogizer</a>
------------------------------<wbr>------------------------------<wbr>-----
Recogizer Group GmbH
Geschäftsführer: Oliver Habisch, Carsten Kreutze
Handelsregister: Amtsgericht Bonn HRB 20724
Sitz der Gesellschaft: Bonn; USt-ID-Nr.: DE294195993
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und löschen Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail und der darin enthaltenen Informationen ist nicht gestattet.</pre>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div></div></div>
</div>
</div>
</blockquote></div><br></div>