<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 24, 2017 at 9:28 PM, Odilon Junior <span dir="ltr"><<a href="mailto:odilon.junior93@gmail.com" target="_blank">odilon.junior93@gmail.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">Hi everyone, i've just subscribed to the maling list, I was going to ask one thing about ovirt in the IRC channel but no one was there.<br><br>I've been using ovirt since 3.1, today we have one enviroment with 1 Ovirt Engine and 3 baremetal that we use for virtualization running the Ovirt 3.6.3. We have 3 NFS share from our colocation provider that are used as Storage.<br><br>Our collocation will be rolling one emergency maintenance to upgrade the firmware on the routers that provides our Private Network, the NFS service run on this Private Network,the downtime should be no more than 3 minutes.<br><br>I'm concerned, what is the best way to approach this, should we shutdown all the VMs and the hypervisor? Or we can just let the Ovirt handle this? The communication between the Ovirts and the Engine are from another network that will not be affected.<br></div></blockquote><div><br></div><div>You should put everything into maintenance.</div><div>Unlike other storages, NFS will hang and you'll have stale mounts eventually, which cannot be recovered from. </div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"></div>
<br>______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br></div></div>