ovm manager

Overview

This resource allows you to register OVM Manager access. Using Puppet you can setup connection credentials to different Oracle VM managers and control address them just using specified name. Here is an example on how to use this:

ovm_manager { 'default':
  password    => 'welcome1',
  verify_ssl  => false,
  manager_url => 'https://192.168.59.10:215',
}

All the other OVM types use this information to connect to the Oracle VM Manager. You can use this type on multiple machines.

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 ovm_manager

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_manager

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of ovm_manager

manager_url

The url to connect to the Oracle VM Manager. Here is example how to do this:

ovm_manager { my_ovm_manager:
  ...
  manager_url => 'https://192.168.59.10:7002',
  ...
}

Back to overview of ovm_manager

name

The name of the Oracle VM manager. This is used to distinguish different OVM manager setups and allow to manage more than one manager in the Puppet setup.

Back to overview of ovm_manager

password

The password used to connect to the OVM Manager. After the setup the password is encrypted and not visible. Here is example how to do this:

ovm_manager {my_ovm_manager:
  ...
  password => 'very_secret',
  ...
}

Back to overview of ovm_manager

port

The port of ovm to connect to the OVM Manager. Default port for https connection is 7002. Here is example how to do this:

ovm_manager { my_ovm_manager:
  ...
  port => 7002,
  ...
}

Back to overview of ovm_manager

provider

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

simple

Manage OVM Manager access through yaml file

Back to overview of ovm_manager

username

The username used to connect to the OVM Manager. Here is example how to do this:

ovm_manager {my_ovm_manager:
  ...
  username => 'admin',
  ...
}

Back to overview of ovm_manager

verify_ssl

Verify the SSL connection. e.g. Check if it has a valid SSL key. Here is example how to do this:

ovm_manager {my_ovm_manager:
  ...
  verify_ssl => 'true',
  ...
}

Valid values are true, false.

Back to overview of ovm_manager