# What Changed in 1.0

## New

- Failure timeouts. See

- New section for resource and operation defaults. See and

- Tool for making offline configuration changes. See

- `Rules, instance_attributes, meta_attributes` and sets of operations can be defined once and referenced in multiple places. See

- The CIB now accepts XPath-based create/modify/delete operations. See the `cibadmin` help text.

- Multi-dimensional colocation and ordering constraints. See and

- The ability to connect to the CIB from non-cluster machines. See

- Allow recurring actions to be triggered at known times. See

## Changed

- Syntax

  - All resource and cluster options now use dashes (-) instead of underscores (_)

  - `master_slave` was renamed to `master`

  - The `attributes` container tag was removed

  - The operation field `pre-req` has been renamed `requires`

  - All operations must have an `interval`, start/stop must have it set to zero

- 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

- The attributes of colocation and ordering constraints were renamed for clarity. See and

- `resource-failure-stickiness` has been replaced by `migration-threshold`. See

- The arguments for command-line tools has 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 therefor fail.

  - The CIB representation from which the MD5 digest used to verify CIBs 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 therefor 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).

## Removed

- Syntax

  - It is no longer possible to set resource meta options as top-level attributes. Use meta attributes instead.

  - Resource and operation defaults are no longer read from `crm_config`. See and instead.