em entitlement

Overview

Using this Puppet type, you can manage the nodes entitled to use a specific module.

Here is an example on how to use this:

em_entitlement { 'license_id/my_module@mynode2.domain.nl->puppet.server.com':
  ensure => 'present',
}

The way to read this is:

The license provided by Enterprise Modules with license_id, allows you to use the module my_module on a number of named nodes. This puppet declaration enables node puppet.server.com connected to puppet server puppet.server.com one of these entitlements.

You can also use the variant without a specified pupet server. The syntax is then:

em_entitlement { 'licenseid/module@mynode2.domain.nl':
  ensure => 'present',
}

It will then use the current puppet server as the default.

Attributes

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 em_entitlement

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 em_entitlement

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of em_entitlement

entitled_module

The Puppet module you want to entitle on specified node.

Back to overview of em_entitlement

license_id

This is the license id you want to use for this entitlement. This is the number given to you by Enterprise Modules when you purchase the entitlement subscription.

Back to overview of em_entitlement

name

The full name of the node and module to be entitled.

Back to overview of em_entitlement

node_name

The FQDN of the node you want to entitle the use of ths specfied Puppet module for.

Back to overview of em_entitlement

provider

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

simple

Manage Enterprise Modules entitlements for indivudual nodes

Back to overview of em_entitlement

puppet_server

The full name of the puppet server that provides the catalog to the node you want to use the specified Puppet module on.

Back to overview of em_entitlement