ovm statistic management

Overview

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

ovm_statistic_management { 'default':
  enabled              => 'true',
  fs_sampling_interval => '600',
  hold_time            => '60',
  max_queue_size       => '10000',
  per_hour_threshold   => '1000000',
  sampling_interval    => '20',
}

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_statistic_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_statistic_management

enabled

The enabled field of the ovm_statistic_management. Here is example how to do this:

ovm_statistic_management { ...
  ...
  enabled => 'true'
  ...
}

Valid values are true, false.

Back to overview of ovm_statistic_management

fs_sampling_interval

The fs_sampling_interval field of the ovm_statistic_management. Here is example how to do this:

ovm_statistic_management { ...
  ...
  fs_sampling_interval => '1500'
  ...
}

Back to overview of ovm_statistic_management

hold_time

The hold_time field of the ovm_statistic_management. Here is example how to do this:

ovm_statistic_management { ...
  ...
  hold_time => '1500'
  ...
}

Back to overview of ovm_statistic_management

manager_name

The name of the OVM manager.

Back to overview of ovm_statistic_management

max_queue_size

The max_queue_size field of the ovm_statistic_management. Here is example how to do this:

ovm_statistic_management { ...
  ...
  max_queue_size => '1500'
  ...
}

Back to overview of ovm_statistic_management

name

This parameter is the name of OVM Statistic Management.

Back to overview of ovm_statistic_management

per_hour_threshold

The per_hour_threshold field of the ovm_statistic_management. Here is example how to do this:

ovm_statistic_management { ...
  ...
  per_hour_threshold => '1500'
  ...
}

Back to overview of ovm_statistic_management

provider

The specific backend to use for this ovm_statistic_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 Statistic Management.

Back to overview of ovm_statistic_management

sampling_interval

The sampling_interval field of the ovm_statistic_management. Here is example how to do this:

ovm_statistic_management { ...
  ...
  sampling_interval => '1500'
  ...
}

Back to overview of ovm_statistic_management