D.3.2. Changed

Syntax

The stonith-enabled option now defaults to true.

The cluster will refuse to start resources if stonith-enabled is true (or unset) and no STONITH resources have been defined

resource-failure-stickiness has been replaced by migration-threshold. See Section 9.3, “Handling Resource Failure”

The parameters for command-line tools have been made consistent

Switched to RelaxNG schema validation and libxml2 parser

id fields are now XML IDs which have the following limitations:
- id’s cannot contain colons (:)
- id’s cannot begin with a number
- id’s must be globally unique (not just unique for that tag)
Some fields (such as those in constraints that refer to resources) are IDREFs.
This means that they must reference existing resources or objects in order for the configuration to be valid. Removing an object which is referenced elsewhere will therefore fail.
The CIB representation, from which a MD5 digest is calculated to verify CIBs on the nodes, has changed.
This means that every CIB update will require a full refresh on any upgraded nodes until the cluster is fully upgraded to 1.0. This will result in significant performance degradation and it is therefore highly inadvisable to run a mixed 1.0/0.6 cluster for any longer than absolutely necessary.

Ping node information no longer needs to be added to ha.cf.

Simply include the lists of hosts in your ping resource(s).