iib deployment

Overview

This resource allows you to manage process of deployment of IBM IIB.

Here is an example on how you should use this:

iib_deployment { 'IIB107/IB10NODE1/server_2/Hello':
  ensure => 'present',
  source => '/tmp/Helloproject.TestMode.bar',
}

In this example you are ensuring that deployment is done from provided source.

Attributes

application

This shared parameter specifies application for iib_server in IBM IIB realm.

In example

'NODE1/server_1/Hello'

Back to overview of iib_deployment

broker

This parameter specifies custom name for iib_broker in IBM IIB realm.

In example

'NODE1'

Back to overview of iib_deployment

deployment_name

This parameter specifies custom name for iib_deployment in IBM IIB realm.

In example

'Hello'

Back to overview of iib_deployment

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 iib_deployment

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 iib_deployment

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of iib_deployment

instance

This shared parameter specifies iib_instance in IBM IIB realm.

Example name

'iib8'

Back to overview of iib_deployment

name

This parameter specifies uniqe custom name for iib_deployment in Puppet realm.

In example

'iib8/NODE1/server_1/Hello'

Back to overview of iib_deployment

provider

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

simple

Manage IIB deployments

Back to overview of iib_deployment

server

This parameter specifies custom name for iib_server in IBM IIB realm.

In example

'server_1'

Back to overview of iib_deployment

source

This property is the bar file for deployment.

The deployment process will run with the identity of the iibadmin user. Makes sure the file is accessible by the iibadmin user.

iib_deployment { 'IIB107/IB10NODE1/server_2/Hello':
  ensure => 'present',
  source => '/tmp/Helloproject.TestMode.bar',
}

Back to overview of iib_deployment