ovm log management

Overview

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

ovm_log_management { 'default':
  configured_level => 'INHERITED',
  effective_level  => 'INFORMATIONAL',
  inherited_from   => 'root',
}

Attributes

configured_level

The configured_level field of the Oracle VM Log Management. Here is example how to do this:

ovm_log_management { ...
  ...
  configured_level => 'INHERITED'
  ...
}

Valid values are DEBUG, INFORMATIONAL, WARNING, ERROR, FATAL, OFF, INHERITED.

Back to overview of ovm_log_management

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_log_management

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_log_management

effective_level

The effective_level field of the Oracle VM Log Management. Here is example how to do this:

ovm_log_management { ...
  ...
  effective_level => 'DEBUG'
  ...
}

Valid values are DEBUG, INFORMATIONAL, WARNING, ERROR, FATAL, OFF, INHERITED.

Back to overview of ovm_log_management

inherited_from

The inherited_from field of the Oracle VM Log Management. Here is example how to do this:

ovm_log_management { ...
  ...
  inherited_from => 'root'
  ...
}

Back to overview of ovm_log_management

manager_name

The name of the OVM manager.

Back to overview of ovm_log_management

name

This parameter is the name of ovm_log_management.

Back to overview of ovm_log_management

provider

The specific backend to use for this ovm_log_management 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 Clone Log Management.

Back to overview of ovm_log_management