pcmkr database

Overview

This resource allows you to manage an Pacemaker cluster. Here is an example on how to use this:

pcmkr_database { 'db2inst1/MYDB':
  ensure     => 'present',
}

All of these properties are read-only. If you need to add nodes, or change interfaces, the cluster must be recreated. At this point in time Puppet does not take care of this.

Attributes

database_name

The name of the database.

Back to overview of pcmkr_database

disable_corrective_change

Disable the modification of a resource when Puppet decides it is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet Server, Puppet knows about adaptive and corrective changes. A corrective change is when Puppet notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet is managing. The normal Puppet process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the disable_corrective_change parameter, you can disable corrective changes on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ...
  disable_corrective_change => true,
  ...
}

When a corrective ensure does happen on the resource Puppet will not modify the resource and signal an error:

    Error: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/parameter: change from '10' to '20' failed: Corrective change present requested by catalog, but disabled by parameter disable_corrective_change. (corrective)

Back to overview of pcmkr_database

disable_corrective_ensure

Disable the creation or removal of a resource when Puppet decides is a corrective change.

(requires easy_type V2.11.0 or higher)

When using a Puppet Server, Puppet knows about adaptive and corrective changes. A corrective change is when Puppet notices that the resource has changed, but the catalog has not changed. This can occur for example, when a user, by accident or willingly, changed something on the system that Puppet is managing. The normal Puppet process then repairs this and puts the resource back in the state as defined in the catalog. This process is precisely what you want most of the time, but not always. This can sometimes also occur when a hardware or network error occurs. Then Puppet cannot correctly determine the current state of the system and thinks the resource is changed, while in fact, it is not. Letting Puppet recreate remove or change the resource in these cases, is NOT wat you want.

Using the disable_corrective_ensure parameter, you can disable corrective ensure present or ensure absent actions on the current resource.

Here is an example of this:

crucial_resource {'be_carefull':
  ensure                    => 'present',
  ...
  disable_corrective_ensure => true,
  ...
}

When a corrective ensure does happen on the resource Puppet will not create or remove the resource and signal an error:

    Error: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure.
    Error: /Stage[main]/Main/Crucial_resource[be_carefull]/ensure: change from 'absent' to 'present' failed: Corrective ensure present requested by catalog, but disabled by parameter disable_corrective_ensure. (corrective)

Back to overview of pcmkr_database

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of pcmkr_database

instance_name

The name of the instance.

Back to overview of pcmkr_database

location

The location of the software the instance is running from.

Back to overview of pcmkr_database

managed

The managed state of the Pacemaker instance.

This is a read-only property and cannot be changed.

Back to overview of pcmkr_database

name

The full name of the Pacemaker database. This includes the instance and the database separated by a slash.

Back to overview of pcmkr_database

primary_instance

The instance name on the primary node for this HADR database. This is a read-only property.

Back to overview of pcmkr_database

primary_node

The primary node for this HADR database. This is a read-only property.

Back to overview of pcmkr_database

primary_state

The state of the primary node for this HADR database. This is a read-only property.

Back to overview of pcmkr_database

provider

The specific backend to use for this pcmkr_database resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform.Available providers are:

db2cm

Manage an Pacemaker database

Back to overview of pcmkr_database

standby_instance

The instance name on the standby node for this HADR database. This is a read-only property.

Back to overview of pcmkr_database

standby_node

The standby node for this HADR database. This is a read-only property.

Back to overview of pcmkr_database

standby_state

The state of the standby node for this HADR database. This is a read-only property.

Back to overview of pcmkr_database