4.2. Upgrading from CRM-enabled Heartbeat 2.1 clusters

This section outlines the steps necessary to upgrade a Heartbeat 2.1 cluster with the built-in CRM enabled, to Heartbeat 3.0 with Pacemaker.

Note

When properly planned and executed, the upgrade procedure can be completed in a manner of minutes, with no application down time.

It is strongly recommended to read and understand the steps outlined in this section before attempting a production cluster upgrade.

All commands stated in this section must be run as root. Do not perform the individual steps in parallel on all of your cluster nodes. Instead, complete the procedure on each node before continuing with the next.

4.2.1. Placing the cluster in unmanaged mode

With this step, the cluster temporarily relinquishes control of its resources. This means that the cluster no longer monitors its nodes or resources for the duration of the upgrade, and will not rectify and application or node failures during this time. Currently running resources, however, will continue to run.

# crm_attribute -t crm_config -n is_managed_default -v false

Note

In most configurations, individual resources do not set the is_managed attribute individually, and hence the cluster-wide attribute is_managed_default applies to all of them.

If in your specific configuration you do have resources that have this attribute set, you should remove it to make sure the default applies:

# crm_resource -t primitive -r resource-id -p is_managed -D