<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 29, 2017 at 10:36 PM, Liron Aravot <span dir="ltr"><<a href="mailto:laravot@redhat.com" target="_blank">laravot@redhat.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"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Wed, Mar 29, 2017 at 4:35 PM, Nicolas Ecarnot <span dir="ltr"><<a href="mailto:nicolas@ecarnot.net" target="_blank">nicolas@ecarnot.net</a>></span> wrote:<br></span><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">[Please ignore the previous msg]<br>
<br>
Hello,<br>
<br>
One of our DC is a very small one, though quite critical.<br>
It's almost hyper converged : hosts are compute+storage, but the engine is standalone.<br>
<br>
It's made of :<br>
<br>
Hardware :<br>
- one physical engine : CentOS 6.7<br>
- 3 physical hosts : CentOS 7.2<br>
<br>
Software :<br>
- oVirt 3.6.5<br>
- glusterFS 3.7.16 in replica-3, sharded.<br>
<br>
The goal is to upgrade all this to oVirt 4.1.1, and also upgrade the OSes. (oV 4.x only available on cOS 7.x)<br>
<br>
At present, only 3 VMs here are critical, and I have backups for them.<br>
Though, I'm quite nervous with the path I have to follow and the hazards. Especially about the gluster parts.<br>
<br>
At first glance, I would go this way (feel free to comment) :<br>
- upgrade the OS of the engine : 6.7 -> 7.3<br>
- upgrade the OS of the hosts : 7.2 -> 7.3<br>
- upgrade and manage the upgrade of gluster, check the volumes...<br>
- upgrade oVirt (engine then hosts)<br></blockquote><div><br></div></span><div>Hi Nicolas,</div><div>Regards the gluster update - have your tried to ask in the gluster ml?</div><div>I'm adding Sahina to share her opinion on that flow. </div><div>Export domain as Didi suggested is indeed the easy way from oVirt perspective - but it'll take a long time to copy/restore, Gluster backup should perform faster if there's a solution that fit your needs.</div></div></div></div></blockquote><div><br></div><div>Gluster does work with rolling upgrades - so there's no need to bring your system offline. <br></div><div>Which glusterfs version are you on? Are you planning to update to gluster 3.10<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
But when upgrading the OSes, I guess it will also upgrade the gluster layer.<br>
<br>
During this upgrade, I have no constraint to keep everything running, total shutdown is acceptable.<br>
<br>
Is the above procedure seems OK, or may am I missing some essential points?<br>
<br>
Thank you.<span class="m_524900442687069360HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Nicolas ECARNOT<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>
______________________________<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>
</font></span></blockquote></span></div><br></div></div>
</blockquote></div><br></div></div>