ovm storage array

Overview

This resource allows you manage Oracle VM Storage Array. Here is an example on how to use this:

ovm_storage_array { 'default/Unmanaged FibreChannel Storage Array':
  ensure                  => 'present',
  storage_type            => 'ISCSI',
  admin_password          => '****************',
}

Attributes

access_hosts

The access_hosts field of the Storage Array. It takes array of hash object. Each hash contains the the hostname of storage server, port, username and password used for access. Here is example how to do this:

ovm_storage_array { 'default/array_name':
  ...
  access_hosts => ['.
  {
    'hostname' => '192.168.56.10',
    'port' => 3260,
    'username' => 'admin',
    'password' => 'secretstuff',
  }],        ...
}

Back to overview of ovm_storage_array

admin_hostname

The admin_hostname field of the Storage Array. Here is example how to do this:

ovm_storage_array { 'default/array_name':
  ...
  admin_hostname => '...',
  ...
}

Back to overview of ovm_storage_array

admin_password

The admin_password field of the Storage Array. Here is example how to do this:

ovm_storage_array { 'default/array_name':
  ...
  admin_password => '...',
  ...
}

Back to overview of ovm_storage_array

admin_servers

The admin_server_names is used only in the process of file server discovery. Here is example how to do this:

ovm_file_server { ...
  ...
  admin_servers => ['ovs33.fr.oracle.com']
  ...
}

or:

ovm_storage_array { ...
...
admin_servers => ['ovs33.fr.oracle.com']
...   }

Back to overview of ovm_storage_array

admin_username

The admin_username field of the Storage Array. Here is example how to do this:

ovm_storage_array { 'default/array_name':
  ...
  admin_username => '...',
  ...
}

Back to overview of ovm_storage_array

description

The description field of the Storage Array. Here is example how to do this:

ovm_storage_array { 'default/array_name':
  ...
  description => '...',
  ...
}

Back to overview of ovm_storage_array

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 ovm_storage_array

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 ovm_storage_array

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of ovm_storage_array

extra_information

The extra_information field of the Storage Array. Here is example how to do this:

ovm_storage_array { 'default/array_name':
  ...
  extra_information => '...',
  ...
}

Back to overview of ovm_storage_array

id

This parameter is responsible for the mapping of the id of the Oracle VM object.

Back to overview of ovm_storage_array

manager_name

The name of the OVM manager.

Back to overview of ovm_storage_array

name

This parameter is the full name of ovm_storage_array.

Back to overview of ovm_storage_array

plugin

The storage_array_plugin_id field of the Storage Array. Here is example how to do this:

ovm_storage_array { 'default/array_name':
  ...
  plugin => '...',
  ...
}

Back to overview of ovm_storage_array

provider

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

simple

Manage Oracle VM Storage Array.

Back to overview of ovm_storage_array

storage_array_name

The name of the ovm_storage_array.

Back to overview of ovm_storage_array

storage_name

The storage_name field of the Storage Array. Here is example how to do this:

ovm_storage_array { 'default/array_name':
  ...
  storage_name => '...',
  ...
}

Back to overview of ovm_storage_array

storage_type

The type of storage array you want to add. Here is example how to do this:

ovm_storage_array { 'default/array_name':
  ...
  storage_type => 'ISCSI'
  ...
}

Valid values are FIBRECHANNEL, ISCSI, LOCAL, UNKNOWN.

Back to overview of ovm_storage_array

use_chap

The use_chap field of the Storage Array. Here is example how to do this:

ovm_storage_array { 'default/array_name':
  ...
  use_chap => '...',
  ...
}

Back to overview of ovm_storage_array