ovm virtual disk

Overview

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

ovm_virtual_disk { 'default/VirtualDisk1':
  ensure      => 'present',
  description => 'First Virtual Disk',
}

Here is an example on how to add iso to repository:

ovm_virtual_disk { 'default/repo_1/CentOS 7 minimal iso':
  ensure      => 'present',
  description => 'minimal image of CentOS 7',
  disk_type   => 'VIRTUAL_CDROM',
  shareable   => true,
  urls        => ['http://ftp.pbone.net/pub/centos/7/isos/x86_64/CentOS-7-x86_64-Minimal-1708.iso'],
  async       => false,
}

Attributes

async

The async field of the ovm_virtual_disk. This applies only to the virtual disk iso download VIRTUAL_CDROM. If the async is set to true than the iso is downloaded in async and the job is not validated. This defaults to false. Here is example how to do this:

ovm_virtual_disk { ...
  ...
  async => true
  ...
}

Valid values are true, false.

Back to overview of ovm_virtual_disk

description

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

ovm_virtual_disk { ...
  ...
  description => 'description'
  ...
}

Back to overview of ovm_virtual_disk

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_virtual_disk

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_virtual_disk

disk_type

The disk_type field of the ovm_virtual_disk, VIRTUAL_CDROM or VIRTUAL_DISK. Here is example how to do this:

ovm_virtual_disk { ...
  ...
  disk_type => 'VIRTUAL_CDROM'
  ...
}

Valid values are VIRTUAL_CDROM, VIRTUAL_DISK.

Back to overview of ovm_virtual_disk

ensure

The basic property that the resource should be in.

Valid values are present, absent.

Back to overview of ovm_virtual_disk

id

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

Back to overview of ovm_virtual_disk

manager_name

The name of the OVM manager.

Back to overview of ovm_virtual_disk

name

This parameter specify name of the ovm_virtual_disk.

Back to overview of ovm_virtual_disk

provider

The specific backend to use for this ovm_virtual_disk 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 Virtual Disk.

Back to overview of ovm_virtual_disk

proxy

The proxy field of the ovm_virtual_disk. Here is example how to do this:

ovm_virtual_disk { ...
  ...
  proxy => 'proxy goes here'
  ...
}

Back to overview of ovm_virtual_disk

repository_name

The name of the repository.

Back to overview of ovm_virtual_disk

shareable

The shareable field of the ovm_virtual_disk. Here is example how to do this:

ovm_virtual_disk { ...
  ...
  shareable => 'true'
  ...
}

Valid values are true, false.

Back to overview of ovm_virtual_disk

size

The size of the disk. If this is a sparse image, this number does not reflect the actual size of the image on disk, but rather the maximum size of the file. For a non-sparse image this is the same as the size of the file on disk. This field not applies to the VIRTUAL_CDROM type of Virtual Disk. Here is example how to do this:

ovm_virtual_disk { ...
  ...
  size =>
  ...
}

Back to overview of ovm_virtual_disk

sparse

This parameter determines the type of resize operation. If true, unused portions of the disk are not replicated in the image file.

Valid values are true, false.

Back to overview of ovm_virtual_disk

urls

The urls field of the ovm_virtual_disk. This field only applies to the VIRTUAL_CDROM type of Virtual Disk. Here is example how to do this:

ovm_virtual_disk { ...
  ...
  urls => ['https://buildlogs.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-Minimal-1609-99.iso']
  ...
}

Back to overview of ovm_virtual_disk

virtual_disk_name

The name of the ovm_virtual_disk.

Back to overview of ovm_virtual_disk