<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hello,</div>
<div> </div>
<div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><br/>
<br/>
> While the Pacemaker versions support rolling upgrades, those Corosync<br/>
> versions do not, so you'll have to do the detach-and-reattach method.<br/>
<br/>
> The main reason to do a new cluster instead is if you want to do some<br/>
> testing before making it live.<br/>
> --<br/>
> Ken Gaillot <kgaillot@redhat.com><br/>
</div>
</div>
</div>
</div>
<div> </div>
<div class="signature">thanks for your answer. So upgrading detached nodes will result in downtime of haproxy and may disclose some other surprises...</div>
<div class="signature">I think building a new cluster is the best way to avoid downtimes. In my case i could switch by DNS to new clusterservers and achive a mostly seemless transition of use.</div>
<div class="signature"> </div>
<div class="signature">Thank you,</div>
<div class="signature">Hajo</div>
<div class="signature"> </div>
<div class="signature"> </div></div></body></html>