Resource Type: pacemaker_colocation

Defined in:

lib/puppet/type/pacemaker_colocation.rb

Providers:

xml
noop

Overview

Type for manipulating corosync/pacemaker colocation. Colocation is the grouping together of a set of primitives so that they travel together when one of them fails. For instance, if a web server vhost is colocated with a specific ip address and the web server software crashes, the ip address with migrate to the new host with the vhost.

More information on Corosync/Pacemaker colocation can be found here:

• www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/_ensuring_resources_run_on_the_same_host.html

Properties

• ensure (defaults to: present)

  The basic property that the resource should be in.

  Supported values:

  • present
  • absent
• first

  First Corosync primitive.

• score (defaults to: INFINITY)

  The priority of this colocation. Primitives can be a part of multiple colocation groups and so there is a way to control which primitives get priority when forcing the move of other primitives. This value can be an integer but is often defined as the string INFINITY.

• second

  Second Corosync primitive.

Parameters

• debug (defaults to: false)

  Don’t actually make changes

  Supported values:

  • true
  • false
  • yes
  • no
• name (namevar)

  Identifier of the colocation entry. This value needs to be unique across the entire Corosync/Pacemaker configuration since it doesn’t have the concept of name spaces per type.

• provider

  The specific backend to use for this ‘pacemaker_colocation` resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform.