ovm server pool

Overview

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

ovm_server_pool { 'default/server_pool_1':
  ensure          => 'present',
  description     => 'Server Pool number 1',
  keymap          => 'en-us',
  virtual_ip      => '123.10.1.1',
  vm_start_policy => 'BEST_SERVER',
}

Attributes

description

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

ovm_server_pool { ...
  ...
  description => 'My test pool'
  ...
}

Back to overview of ovm_server_pool

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_server_pool

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_server_pool

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of ovm_server_pool

id

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

Back to overview of ovm_server_pool

keymap

Specifies keymap to use for the console. Here is example how to do this:

ovm_server_pool { ...
  ...
  keymap => 'en-us'
  ...
}

Back to overview of ovm_server_pool

locked

This parameter allows you manage user_name of the Oracle VM Server Controller. Here is an example on how to use this:

ovm_server_pool { 'default/mypool1':
  ensure          => 'present',
  locked          => true,
}

Valid values are true, false.

Back to overview of ovm_server_pool

manager_name

The name of the OVM manager.

Back to overview of ovm_server_pool

master_server

Specifies master_server of the server pool. Here is example how to do this:

ovm_server_pool { ...
  ...
  master_server => 'master_server.example.com'
  ...
}

Back to overview of ovm_server_pool

name

The full name of the Server Pool.

Back to overview of ovm_server_pool

provider

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

simple

Manage a pool on a OVM manager.

Back to overview of ovm_server_pool

secure_vm_migrate

Specifies the Secure Migrate of the Server Pool. Here is example how to do this:

ovm_server_pool { ...
  ...
  secure_vm_migrate => 'true',
  ...
}

Valid values are true, false.

Back to overview of ovm_server_pool

server_pool_name

The name of the storage pool.

This is the second part of the title.

ovm_...{my_manager:pool/....:
  ...
}

Back to overview of ovm_server_pool

servers

Specifies the servers that are part of this pool. Here is example how to do this:

ovm_... { ...
  ...
  servers => ['server1.example.com','server2.example.com'],
  ...
}

Back to overview of ovm_server_pool

tags

Specifies the tags enabled for the resource. This property can be used for a lot of resources. Here is example how to do this:

ovm_... { ...
  ...
  tags => ['tag-1','tag-2'],
  ...
}

Back to overview of ovm_server_pool

virtual_ip

Specifies The virtual IP address of the server pool. Here is example how to do this:

ovm_server_pool { ...
  ...
  virtual_ip => '10.1.100.3'
  ...
}

Back to overview of ovm_server_pool

vm_start_policy

Specifies Vm Start Policy of the Server Pool. Here is example how to do this:

ovm_server_pool { ...
  ...
  vm_start_policy => 'BEST_SERVER'
  ...
}

Back to overview of ovm_server_pool