Resource Type: pacemaker_order

Defined in:

lib/puppet/type/pacemaker_order.rb

Providers:

xml
noop

Overview

Type for manipulating Corosync/Pacemkaer ordering entries. Order entries are another type of constraint that can be put on sets of primitives but unlike colocation, order does matter. These designate the order at which you need specific primitives to come into a desired state before starting up a related primitive.

More information can be found at the following link:

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

Properties

• ensure (defaults to: present)

  The basic property that the resource should be in.

  Supported values:

  • present
  • absent
• first

  (Mandatory) Name of the resource that the then resource depends on.

• first_action

  The action that the first resource must complete before the second action can be initiated for the then resource. Allowed values: start, stop, promote, demote.

  Default: undef (means start)

  Supported values:

  • start
  • stop
  • promote
  • demote
• kind

  How to enforce the constraint. Allowed values:

  • optional: Just a suggestion. Only applies if both resources are executing the specified actions. Any change in state by the first resource will have no effect on the then resource.

  • mandatory: Always. If first does not perform first-action, then will not be allowed to performed then-action. If first is restarted, then (if running) will be stopped beforehand and started afterward.

  • serialize: Ensure that no two stop/start actions occur concurrently for the resources. First and then can start in either order, but one must complete starting before the other can be started. A typical use case is when resource start-up puts a high load on the host.

  Supported values:

  • optional
  • mandatory
  • serialize
• require_all

  Whether all members of the set must be active before continuing.

  Default: undef (means true)

• score

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

  Default: undef

• second

  (Mandatory) Name of the dependent resource

• second_action

  The action that the then resource can execute only after the first action on the first resource has completed. Allowed values: start, stop, promote, demote.

  Default: undef (means the value of the first action)

  Supported values:

  • start
  • stop
  • promote
  • demote
• symmetrical

  If true, the reverse of the constraint applies for the opposite action (for example, if B starts after A starts, then B stops before A stops).

  Default: undef (means true)

Parameters

• debug (defaults to: false)

  Don’t actually make changes.

  Default: false

  Supported values:

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

  Name identifier of this ordering 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_order` resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform.