ovm file server

Overview

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

ovm_file_server { 'default/nfs_server_1':
  ensure          => 'present',
  access_host     => '192.168.56.3',
  admin_servers   => ['ovs.example.com']
  uniform_exports => 'true',
}

Attributes

access_host

IP address used for accessing file server. Here is example how to do this:

ovm_file_server { 'default/nfs_server_1':
  ensure          => 'present',
  access_host     => '172.28.128.49',
}

Back to overview of ovm_file_server

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_file_server

description

The description field of the server pool. Here is example how to do this:

ovm_file_server { ...
  ...
  description => 'My file server'
  ...
}

Back to overview of ovm_file_server

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_file_server

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_file_server

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of ovm_file_server

file_server_name

The name of the ovm_file_server.

Back to overview of ovm_file_server

id

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

Back to overview of ovm_file_server

manager_name

The name of the OVM manager.

Back to overview of ovm_file_server

name

The name of the OVM File Server.

Back to overview of ovm_file_server

plugin

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

ovm_file_server { ...
  ...
  plugin => 'Oracle Generic Network File System'
  ...
}

Back to overview of ovm_file_server

provider

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

simple

Manage OVM File Servers on external machines

Back to overview of ovm_file_server

refresh_servers

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

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

Back to overview of ovm_file_server

uniform_exports

This property is only be manageable if property file_server_type is set to file_server_type NETWORK. Here is example how to do this:

ovm_file_server { 'default/nfs_server_1':
  ensure          => 'present',
  uniform_exports => 'true',
}

Valid values are true, false.

Back to overview of ovm_file_server