This announcement affects people running older versions of 2.0.x ***in CRM mode***.
If you do not know in which mode you are running, check ha.cf and if you see "crm yes", then this announcement concerns you. The publicly stated goal of the Heartbeat team is to allow your cluster to be online for 100 years. As such, when releasing newer versions we always take care to make sure we are backwardly compatible with older versions. While you will always be able to upgrade from version x to x+1, in order to continue to produce high quality software it may occasionally be necessary to drop compatibility with older versions. There will always be an upgrade path from any series-2 release to any other series-2 release. With the release of 2.0.5 we will be removing the ability to perform a rolling upgrade from any version lower than 2.0.4 _in a single pass_. However other upgrade strategies exist and include the ability to upgrade without service interruption. More information on upgrading Heartbeat can be found here: http://linux-ha.org/v2/upgrade and each approach clearly details the version requirements and some of the advantages/disadvantages. For those desperate to perform a rolling upgrade to 2.0.5 (and beyond) in a single pass, you will continue to be able to do so when compiling from scratch for some time yet as the relevant code has been disabled, not removed. Details are available on request. -- Andrew Beekhof "Would the last person to leave please turn out the enlightenment?" - TISM _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
