<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi all,</p>
<p>I'm planning on upgrading the Proxmox cluster this Wednesday,
2020-05-06. <br>
</p>
<p>I'll be following the official upgrade guide at:
<a class="moz-txt-link-freetext" href="https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0">https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0</a> and I've
successfully tested the upgrade procedure on the test cluster
without any issues.</p>
<p>The upgrade will take place in 3 phases:</p>
<ol>
<li>Cluster wide upgrade to Corosync 3: Corosync must be upgraded
across the whole cluster before the move to Proxmox 6, during
this phase VM's will continue to run normally, however the
cluster will become non-quorate and users will be unable to
manage the cluster until the Corosync upgrade is complete.</li>
<li>Rolling Upgrade to Proxmox 6: Nodes will be upgraded one at a
time with VM's migrated off the node being upgraded. I've
confirmed that VM's can be safely migrated from a v5.4 node to a
v6.0 node allowing us to upgrade the cluster without any
downtime.</li>
<li>Ceph upgrade: Once the cluster has been fully upgraded there
is a ceph update that can be applied. As I have not yet tested
this process this step is likely to be deferred to a later date.</li>
</ol>
<p>Users should not expect any noticeable downtime for most VM's,
with the exception of salmon and the discord-irc bridge as these
machines are containers and thus cannot be live migrated. <br>
</p>
<p>Regards,</p>
<p>Zack [CFE]<br>
</p>
</body>
</html>