ovirt.ovirt.ovirt_vm – Module to manage Virtual Machines in oVirt/RHV
Note
This plugin is part of the ovirt.ovirt collection (version 1.6.6).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install ovirt.ovirt
.
To use it in a playbook, specify: ovirt.ovirt.ovirt_vm
.
New in version 1.0.0: of ovirt.ovirt
Synopsis
This module manages whole lifecycle of the Virtual Machine(VM) in oVirt/RHV.
Since VM can hold many states in oVirt/RHV, this see notes to see how the states of the VM are handled.
Requirements
The below requirements are needed on the host that executes this module.
python >= 2.7
ovirt-engine-sdk-python >= 4.4.0
Parameters
Parameter |
Comments |
---|---|
Mapper which maps affinity name between VM’s OVF and the destination affinity this VM should be registered to, relevant when |
|
Mapper which maps affinity label name between VM’s OVF and the destination label this VM should be registered to, relevant when |
|
Boolean indication whether to allow partial registration of Virtual Machine when Choices:
|
|
Dictionary with values needed to create HTTP/HTTPS connection to oVirt: |
|
A PEM file containing the trusted CA certificates. The certificate presented by the server will be verified using these CA certificates. If Default value is set by |
|
Flag indicating if compression is used for connection. Choices:
|
|
Dictionary of HTTP headers to be added to each API call. |
|
A string containing the hostname of the server, usually something like :emphasis:`server.example.com`. Default value is set by Either |
|
A boolean flag that indicates if the server TLS certificate and host name should be checked. Choices:
|
|
A boolean flag indicating if Kerberos authentication should be used instead of the default basic authentication. Choices:
|
|
The password of the user. Default value is set by |
|
Number of seconds to wait for response. |
|
Token to be used instead of login with username/password. Default value is set by |
|
A string containing the API URL of the server, usually something like :emphasis:`https://server.example.com/ovirt-engine/api`. Default value is set by Either |
|
The name of the user, something like admin@internal. Default value is set by |
|
If true, use memory ballooning. Memory balloon is a guest device, which may be used to re-distribute / reclaim the host memory based on VM needs in a dynamic way. In this way it’s possible to create memory over commitment states. Choices:
|
|
Set bios type, necessary for some operating systems and secure boot. If no value is passed, default value is set from cluster. NOTE - Supported since oVirt 4.3. Choices:
|
|
List of boot devices which should be used to boot. For example Default value is set by oVirt/RHV engine. Choices:
|
|
True enable menu to select boot device, False to disable it. By default is chosen by oVirt/RHV engine. Choices:
|
|
ISO file from ISO storage domain which should be attached to Virtual Machine. If you have multiple ISO disks with the same name use disk ID to specify which should be used or use If you pass empty string the CD will be ejected from VM. If used with If used with |
|
If yes then the disks of the created virtual machine will be cloned and independent of the template. This parameter is used only when Choices:
|
|
If yes then the permissions of the template (only the direct ones, not the inherited ones) will be copied to the created virtual machine. This parameter is used only when Choices:
|
|
Dictionary with values for Unix-like Virtual Machine initialization using cloud init. |
|
Use this SSH keys to login to Virtual Machine. |
|
Cloud-init script which will be executed on Virtual Machine when deployed. This is appended to the end of the cloud-init script generated by any other options. For further information, refer to cloud-init User-Data documentation. |
|
DNS search domains to be configured on Virtual Machine. |
|
DNS servers to be configured on Virtual Machine, maximum of two, space-separated. |
|
Hostname to be set to Virtual Machine when deployed. |
|
Set boot protocol of the network interface of Virtual Machine. Choices:
|
|
Set boot protocol of the network interface of Virtual Machine. Choices:
|
|
If boot protocol is static, set this gateway to network interface of Virtual Machine. |
|
If boot protocol is static, set this gateway to network interface of Virtual Machine. For IPv6 addresses the value is an integer in the range of 0-128, which represents the subnet prefix. |
|
If boot protocol is static, set this IP address to network interface of Virtual Machine. |
|
If boot protocol is static, set this IP address to network interface of Virtual Machine. |
|
Set name to network interface of Virtual Machine. |
|
If boot protocol is static, set this netmask to network interface of Virtual Machine. |
|
If boot protocol is static, set this netmask to network interface of Virtual Machine. |
|
If True SSH keys will be regenerated on Virtual Machine. Choices:
|
|
Password to be set for user specified by |
|
Timezone to be set to Virtual Machine when deployed. |
|
Username to be used to set password to Virtual Machine when deployed. |
|
List of dictionaries representing network interfaces to be setup by cloud init. This option is used, when user needs to setup more network interfaces via cloud init. If one network interface is enough, user should use |
|
Set boot protocol of the network interface of Virtual Machine. Can be one of |
|
Set boot protocol of the network interface of Virtual Machine. Can be one of |
|
If boot protocol is static, set this gateway to network interface of Virtual Machine. |
|
If boot protocol is static, set this gateway to network interface of Virtual Machine. For IPv6 addresses the value is an integer in the range of 0-128, which represents the subnet prefix. |
|
If boot protocol is static, set this IP address to network interface of Virtual Machine. |
|
If boot protocol is static, set this IP address to network interface of Virtual Machine. |
|
Set name to network interface of Virtual Machine. |
|
If boot protocol is static, set this netmask to network interface of Virtual Machine. |
|
If boot protocol is static, set this netmask to network interface of Virtual Machine. |
|
If yes the Choices:
|
|
Name of the cluster, where Virtual Machine should be created. Required if creating VM. |
|
Mapper which maps cluster name between VM’s OVF and the destination cluster this VM should be registered to, relevant when |
|
The name of the destination cluster. |
|
The name of the source cluster. |
|
Comment of the Virtual Machine. |
|
Number of virtual CPUs cores of the Virtual Machine. Default value is set by oVirt/RHV engine. |
|
CPU mode of the virtual machine. It can be some of the following: host_passthrough, host_model or custom. For host_passthrough CPU type you need to set If no value is passed, default value is set by oVirt/RHV engine. |
|
CPU Pinning topology to map virtual machine CPU to host CPU. CPU Pinning topology is a list of dictionary which can have following values: |
|
Number of the host CPU. |
|
Number of the virtual machine CPU. |
|
Set a CPU shares for this Virtual Machine. Default value is set by oVirt/RHV engine. |
|
Number of virtual CPUs sockets of the Virtual Machine. Default value is set by oVirt/RHV engine. |
|
Number of threads per core of the Virtual Machine. Default value is set by oVirt/RHV engine. |
|
Enables a virtual machine to be customized to its own compatibility version. If ‘ |
|
Sets the value of the custom_emulated_machine attribute. |
|
Properties sent to VDSM to configure various hooks. Custom properties is a list of dictionary which can have following values: |
|
Name of the custom property. For example: hugepages, vhost, sap_agent, etc. |
|
Regular expression to set for custom property. |
|
Value to set for custom property. |
|
If yes Virtual Machine will be set as delete protected. If no Virtual Machine won’t be set as delete protected. If no value is passed, default value is set by oVirt/RHV engine. Choices:
|
|
Description of the Virtual Machine. |
|
Specify format of the disk. If If Note that this option isn’t idempotent as it’s not currently possible to change format of the disk via API. This parameter is considered only when Choices:
|
|
List of disks, which should be attached to Virtual Machine. Disk is described by following dictionary. |
|
True if the disk should be activated, default is activated. NOTE - This parameter is used only when Choices:
|
|
True if the disk should be bootable, default is non bootable. Choices:
|
|
ID of the disk. Either |
|
Interface of the disk. Choices:
|
|
Name of the disk. Either |
|
Mapper which maps aaa domain name between VM’s OVF and the destination aaa domain this VM should be registered to, relevant when |
|
The name of the destination aaa domain. |
|
The name of the source aaa domain. |
|
When Choices:
|
|
When |
|
Dictionary of values to be used to export VM as OVA. |
|
The name of the directory where the OVA has to be exported. |
|
The name of the exported OVA file. |
|
The name of the destination host where the OVA has to be exported. |
|
If True the module will fetch additional data from the API. It will fetch IDs of the VMs disks, snapshots, etc. User can configure to fetch other attributes of the nested entities by specifying Choices:
|
|
Please check to Synopsis to more detailed description of force parameter, it can behave differently in different situations. Choices:
|
|
If true, the VM will migrate when placement_policy=user-migratable but not when placement_policy=pinned. Choices:
|
|
Assign graphical console to the virtual machine. |
|
Returns the action that will take place when the graphic console(SPICE only) is disconnected. The options are: none No action is taken. lock_screen Locks the currently active user session. logout Logs out the currently active user session. reboot Initiates a graceful virtual machine reboot. shutdown Initiates a graceful virtual machine shutdown. |
|
If true disable the graphics console for this virtual machine. Choices:
|
|
The keyboard layout to use with this graphic console. This option is only available for the VNC console type. If no keyboard is enabled then it won’t be reported. |
|
The number of monitors opened for this graphic console. This option is only available for the SPICE protocol. Possible values are 1, 2 or 4. |
|
Graphical protocol, a list of spice, vnc, or both. |
|
If yes Virtual Machine will be set as highly available. If no Virtual Machine won’t be set as highly available. If no value is passed, default value is set by oVirt/RHV engine. Choices:
|
|
Indicates the priority of the virtual machine inside the run and migration queues. Virtual machines with higher priorities will be started and migrated before virtual machines with lower priorities. The value is an integer between 0 and 100. The higher the value, the higher the priority. If no value is passed, default value is set by oVirt/RHV engine. |
|
Specify host where Virtual Machine should be running. By default the host is chosen by engine scheduler. This parameter is used only when |
|
Single Root I/O Virtualization - technology that allows single device to expose multiple endpoints that can be passed to VMs host_devices is an list which contain dictionary with name and state of device |
|
ID of the Virtual Machine to manage. |
|
Path to an initial ramdisk to be used with the kernel specified by Ramdisk image must be stored on either the ISO domain or on the host’s storage. |
|
Name of virtual machine’s hardware configuration. By default no instance type is used. |
|
Number of IO threads used by virtual machine. 0 means IO threading disabled. |
|
Kernel command line parameters (formatted as string) to be used with the kernel specified by |
|
If true Choices:
|
|
Path to a kernel image used to boot the virtual machine. Kernel image must be stored on either the ISO domain or on the host’s storage. |
|
Dictionary of values to be used to connect to kvm and import a virtual machine to oVirt. |
|
The name of the ISO containing drivers that can be used during the virt-v2v conversion process. |
|
The name of the KVM virtual machine. |
|
The password to authenticate against the KVM. |
|
Specifies the disk allocation policy of the resulting virtual machine. true for sparse, false for preallocated. Choices:
|
|
Specifies the target storage domain for converted disks. This is required parameter. |
|
The URL to be passed to the virt-v2v tool for conversion. For example qemu:///system. This is required parameter. |
|
The username to authenticate against the KVM. |
|
Name of the storage domain this virtual machine lease reside on. Pass an empty string to remove the lease. NOTE - Supported since oVirt 4.1. |
|
Mapper which maps lun between VM’s OVF and the destination lun this VM should contain, relevant when |
|
The address of the block storage host. |
|
The logical unit number to identify a logical unit, |
|
Password to be used to connect to the block storage host. |
|
The port being used to connect with the LUN disk. |
|
The portal being used to connect with the LUN disk. |
|
The iSCSI specification located on an iSCSI server |
|
Username to be used to connect to the block storage host. |
|
The storage type which the LUN reside on (iscsi or fcp)” |
|
Amount of memory of the Virtual Machine. Prefix uses IEC 60027-2 standard (for example 1GiB, 1024MiB). Default value is set by engine. |
|
Amount of minimal guaranteed memory of the Virtual Machine. Prefix uses IEC 60027-2 standard (for example 1GiB, 1024MiB).
Default value is set by engine. |
|
Upper bound of virtual machine memory up to which memory hot-plug can be performed. Prefix uses IEC 60027-2 standard (for example 1GiB, 1024MiB). Default value is set by engine. |
|
If true, the VM will migrate to any available host. Choices:
|
|
Name of the Virtual Machine to manage. If VM don’t exists |
|
Specifies list of the attributes which should be fetched from the API. This parameter apply only when |
|
If true, the update will not be applied to the VM immediately and will be only applied when virtual machine is restarted. NOTE - If there are multiple next run configuration changes on the VM, the first change may get reverted if this option is not passed. Choices:
|
|
List of NICs, which should be attached to Virtual Machine. NIC is described by following dictionary. |
|
Type of the network interface. Choices:
|
|
Custom MAC address of the network interface, by default it’s obtained from MAC pool. NOTE - This parameter is used only when |
|
Name of the NIC. |
|
Profile name where NIC should be attached. |
|
List of vNUMA Nodes to set for this VM and pin them to assigned host’s physical NUMA node. Each vNUMA node is described by following dictionary: |
|
List of VM CPU cores indexes to be included in this NUMA node. |
|
The index of this NUMA node. |
|
Memory size of the NUMA node in MiB. |
|
List of physical NUMA node indexes to pin this virtual NUMA node to. |
|
Set how the memory allocation for NUMA nodes of this VM is applied (relevant if NUMA nodes are set for this VM). It can be one of the following: interleave, preferred or strict. If no value is passed, default value is set by oVirt/RHV engine. Choices:
|
|
Operating system of the Virtual Machine, for example ‘rhel_8x64’. Default value is set by oVirt/RHV engine. Use the ovirt.ovirt.ovirt_vm_os_info module to obtain the current list. |
|
The configuration of the virtual machine’s placement policy. If no value is passed, default value is set by oVirt/RHV engine. Placement policy can be one of the following values: |
|
Allow manual and automatic migration. |
|
Do not allow migration. |
|
Allow manual migration only. |
|
List of host names. |
|
Number of the seconds the module waits until another poll request on entity status is sent. Default: 3 |
|
Virtual Machine quota ID to be used for disk. By default quota is chosen by oVirt/RHV engine. |
|
Boolean indication whether to reassign bad macs when Choices:
|
|
Random number generator (RNG). You can choose of one the following devices urandom, random or hwrng. In order to select hwrng, you must have it enabled on cluster first. /dev/urandom is used for cluster version >= 4.1, and /dev/random for cluster version <= 4.0 |
|
Mapper which maps role name between VM’s OVF and the destination role this VM should be registered to, relevant when |
|
The name of the destination role. |
|
The name of the source role. |
|
True enable VirtIO serial console, False to disable it. By default is chosen by oVirt/RHV engine. Choices:
|
|
Specify a serial number policy for the Virtual Machine. Following options are supported.
Choices:
|
|
Allows you to specify a custom serial number. This parameter is used only when |
|
If true, use smart card authentication. Choices:
|
|
Snapshot to clone VM from. Snapshot with description specified should exist. You have to specify |
|
Source VM to clone VM from. VM should have snapshot specified by If |
|
If true, the sound card is added to the virtual machine. Choices:
|
|
True enable Single Sign On by Guest Agent, False to disable it. By default is chosen by oVirt/RHV engine. Choices:
|
|
Should the Virtual Machine be running/stopped/present/absent/suspended/next_run/registered/exported/reboot. When present state will create/update VM and don’t change its state if it already exists. running state will create/update VM and start it. next_run state updates the VM and if the VM has next run configuration it will be rebooted. Please check notes to more detailed description of states. exported state will export the VM to export domain or as OVA. registered is supported since 2.4. reboot is supported since 2.10, virtual machine is rebooted only if it’s in up state. Choices:
|
|
If yes Virtual Machine will be set as stateless. If no Virtual Machine will be unset as stateless. If no value is passed, default value is set by oVirt/RHV engine. Choices:
|
|
Name of the storage domain where all template disks should be created. This parameter is considered only when IMPORTANT - This parameter is not idempotent, if the VM exists and you specify different storage domain, disk won’t move. |
|
Dictionary with values for Windows Virtual Machine initialization using sysprep. |
|
Active Directory Organizational Unit, to be used for login of user. |
|
A custom Sysprep definition in the format of a complete unattended installation answer file. |
|
Domain to be set to Windows Virtual Machine. |
|
Hostname to be set to Virtual Machine when deployed. |
|
Input localization of the Windows Virtual Machine. |
|
Organization name to be set to Windows Virtual Machine. |
|
Password to be set for username to Windows Virtual Machine. |
|
System localization of the Windows Virtual Machine. |
|
Timezone to be set to Windows Virtual Machine. |
|
UI language of the Windows Virtual Machine. |
|
Username to be used for set password to Windows Virtual Machine. |
|
License key to be set to Windows Virtual Machine. |
|
Name of the template, which should be used to create Virtual Machine. Required if creating VM. If template is not specified and VM doesn’t exist, VM will be created from Blank template. |
|
Version number of the template to be used for VM. By default the latest available version of the template is used. |
|
If true, in addition return remote_vv_file inside vm dictionary, which contains compatible content for remote-viewer application. Works only Choices:
|
|
The amount of time in seconds the module should wait for the instance to get into desired state. Default: 180 |
|
Sets time zone offset of the guest hardware clock. For example |
|
Type of the Virtual Machine. Default value is set by oVirt/RHV engine. high_performance is supported since Ansible 2.5 and oVirt/RHV 4.2. Choices:
|
|
True enable USB support, False to disable it. By default is chosen by oVirt/RHV engine. Choices:
|
|
Specify if latest template version should be used, when running a stateless VM. If this parameter is set to yes stateless VM is created. Choices:
|
|
Dictionary of values to be used to connect to VMware and import a virtual machine to oVirt. |
|
The name of the ISO containing drivers that can be used during the virt-v2v conversion process. |
|
The password to authenticate against the VMware. |
|
Specifies the disk allocation policy of the resulting virtual machine. true for sparse, false for preallocated. Choices:
|
|
Specifies the target storage domain for converted disks. This is required parameter. |
|
The URL to be passed to the virt-v2v tool for conversion. For example vpx://wmware_user@vcenter-host/DataCenter/Cluster/esxi-host?no_verify=1 |
|
The username to authenticate against the VMware. |
|
Mapper which maps an external virtual NIC profile to one that exists in the engine when |
|
The network name of the source network. |
|
The profile name related to the source network. |
|
The id of the target profile id to be mapped to in the engine. |
|
Choices:
|
|
Assign watchdog device for the virtual machine. Watchdogs is a dictionary which can have following values: |
|
Watchdog action to be performed when watchdog is triggered. For example: none, reset, poweroff, pause or dump. |
|
Model of the watchdog device. For example: i6300esb, diag288 or null. |
|
Dictionary of values to be used to connect to XEN and import a virtual machine to oVirt. |
|
The name of the ISO containing drivers that can be used during the virt-v2v conversion process. |
|
Specifies the disk allocation policy of the resulting virtual machine. true for sparse, false for preallocated. Choices:
|
|
Specifies the target storage domain for converted disks. This is required parameter. |
|
The URL to be passed to the virt-v2v tool for conversion. For example xen+ssh://root@zen.server. This is required parameter. |
Notes
Note
If VM is in UNASSIGNED or UNKNOWN state before any operation, the module will fail. If VM is in IMAGE_LOCKED state before any operation, we try to wait for VM to be DOWN. If VM is in SAVING_STATE state before any operation, we try to wait for VM to be SUSPENDED. If VM is in POWERING_DOWN state before any operation, we try to wait for VM to be UP or DOWN. VM can get into UP state from POWERING_DOWN state, when there is no ACPI or guest agent running inside VM, or if the shutdown operation fails. When user specify UP
state
, we always wait to VM to be in UP state in case VM is MIGRATING, REBOOTING, POWERING_UP, RESTORING_STATE, WAIT_FOR_LAUNCH. In other states we run start operation on VM. When user specify stoppedstate
, and If user passforce
parameter set to true we forcibly stop the VM in any state. If user don’t passforce
parameter, we always wait to VM to be in UP state in case VM is MIGRATING, REBOOTING, POWERING_UP, RESTORING_STATE, WAIT_FOR_LAUNCH. If VM is in PAUSED or SUSPENDED state, we start the VM. Then we gracefully shutdown the VM. When user specify suspendedstate
, we always wait to VM to be in UP state in case VM is MIGRATING, REBOOTING, POWERING_UP, RESTORING_STATE, WAIT_FOR_LAUNCH. If VM is in PAUSED or DOWN state, we start the VM. Then we suspend the VM. When user specify absentstate
, we forcibly stop the VM in any state and remove it.If you update a VM parameter that requires a reboot, the oVirt engine always creates a new snapshot for the VM, and an Ansible playbook will report this as changed.
In order to use this module you have to install oVirt Python SDK. To ensure it’s installed with correct version you can create the following task: pip: name=ovirt-engine-sdk-python version=4.4.0
Examples
# Examples don't contain auth parameter for simplicity,
# look at ovirt_auth module to see how to reuse authentication:
- name: Creates a new Virtual Machine from template named 'rhel7_template'
ovirt.ovirt.ovirt_vm:
state: present
name: myvm
template: rhel7_template
cluster: mycluster
- name: Register VM
ovirt.ovirt.ovirt_vm:
state: registered
storage_domain: mystorage
cluster: mycluster
name: myvm
- name: Register VM using id
ovirt.ovirt.ovirt_vm:
state: registered
storage_domain: mystorage
cluster: mycluster
id: 1111-1111-1111-1111
- name: Register VM, allowing partial import
ovirt.ovirt.ovirt_vm:
state: registered
storage_domain: mystorage
allow_partial_import: "True"
cluster: mycluster
id: 1111-1111-1111-1111
- name: Register VM with vnic profile mappings and reassign bad macs
ovirt.ovirt.ovirt_vm:
state: registered
storage_domain: mystorage
cluster: mycluster
id: 1111-1111-1111-1111
vnic_profile_mappings:
- source_network_name: mynetwork
source_profile_name: mynetwork
target_profile_id: 3333-3333-3333-3333
- source_network_name: mynetwork2
source_profile_name: mynetwork2
target_profile_id: 4444-4444-4444-4444
reassign_bad_macs: "True"
- name: Register VM with mappings
ovirt.ovirt.ovirt_vm:
state: registered
storage_domain: mystorage
cluster: mycluster
id: 1111-1111-1111-1111
role_mappings:
- source_name: Role_A
dest_name: Role_B
domain_mappings:
- source_name: Domain_A
dest_name: Domain_B
lun_mappings:
- source_storage_type: iscsi
source_logical_unit_id: 1IET_000d0001
source_logical_unit_port: 3260
source_logical_unit_portal: 1
source_logical_unit_address: 10.34.63.203
source_logical_unit_target: iqn.2016-08-09.brq.str-01:omachace
dest_storage_type: iscsi
dest_logical_unit_id: 1IET_000d0002
dest_logical_unit_port: 3260
dest_logical_unit_portal: 1
dest_logical_unit_address: 10.34.63.204
dest_logical_unit_target: iqn.2016-08-09.brq.str-02:omachace
affinity_group_mappings:
- source_name: Affinity_A
dest_name: Affinity_B
affinity_label_mappings:
- source_name: Label_A
dest_name: Label_B
cluster_mappings:
- source_name: cluster_A
dest_name: cluster_B
- name: Creates a stateless VM which will always use latest template version
ovirt.ovirt.ovirt_vm:
name: myvm
template: rhel7
cluster: mycluster
use_latest_template_version: true
# Creates a new server rhel7 Virtual Machine from Blank template
# on brq01 cluster with 2GiB memory and 2 vcpu cores/sockets
# and attach bootable disk with name rhel7_disk and attach virtio NIC
- ovirt.ovirt.ovirt_vm:
state: present
cluster: brq01
name: myvm
memory: 2GiB
cpu_cores: 2
cpu_sockets: 2
cpu_shares: 1024
type: server
operating_system: rhel_7x64
disks:
- name: rhel7_disk
bootable: True
nics:
- name: nic1
# Change VM Name
- ovirt.ovirt.ovirt_vm:
id: 00000000-0000-0000-0000-000000000000
name: "new_vm_name"
- name: Run VM with cloud init
ovirt.ovirt.ovirt_vm:
name: rhel7
template: rhel7
cluster: Default
memory: 1GiB
high_availability: true
high_availability_priority: 50 # Available from Ansible 2.5
cloud_init:
dns_servers: '8.8.8.8 8.8.4.4'
nic_boot_protocol: static
nic_ip_address: 10.34.60.86
nic_netmask: 255.255.252.0
nic_gateway: 10.34.63.254
nic_name: eth1
host_name: example.com
custom_script: |
write_files:
- content: |
Hello, world!
path: /tmp/greeting.txt
permissions: '0644'
user_name: root
root_password: super_password
- name: Run VM with cloud init, with multiple network interfaces
ovirt.ovirt.ovirt_vm:
name: rhel7_4
template: rhel7
cluster: mycluster
cloud_init_nics:
- nic_name: eth0
nic_boot_protocol: dhcp
- nic_name: eth1
nic_boot_protocol: static
nic_ip_address: 10.34.60.86
nic_netmask: 255.255.252.0
nic_gateway: 10.34.63.254
# IP version 6 parameters are supported since ansible 2.9
- nic_name: eth2
nic_boot_protocol_v6: static
nic_ip_address_v6: '2620:52:0:2282:b898:1f69:6512:36c5'
nic_gateway_v6: '2620:52:0:2282:b898:1f69:6512:36c9'
nic_netmask_v6: '120'
- nic_name: eth3
nic_boot_protocol_v6: dhcp
- name: Run VM with sysprep
ovirt.ovirt.ovirt_vm:
name: windows2012R2_AD
template: windows2012R2
cluster: Default
memory: 3GiB
high_availability: true
sysprep:
host_name: windowsad.example.com
user_name: Administrator
root_password: SuperPassword123
- name: Migrate/Run VM to/on host named 'host1'
ovirt.ovirt.ovirt_vm:
state: running
name: myvm
host: host1
- name: Migrate/Run VM to/on host named 'host1' on cluster 'cluster1'
ovirt.ovirt.ovirt_vm:
state: running
name: myvm
host: host1
cluster: cluster1
- name: Migrate VM to any available host
ovirt.ovirt.ovirt_vm:
state: running
name: myvm
migrate: true
- name: Change VMs CD
ovirt.ovirt.ovirt_vm:
name: myvm
cd_iso: drivers.iso
- name: Eject VMs CD
ovirt.ovirt.ovirt_vm:
name: myvm
cd_iso: ''
- name: Boot VM from CD
ovirt.ovirt.ovirt_vm:
name: myvm
cd_iso: centos7_x64.iso
boot_devices:
- cdrom
- name: Stop vm
ovirt.ovirt.ovirt_vm:
state: stopped
name: myvm
- name: Upgrade memory to already created VM
ovirt.ovirt.ovirt_vm:
name: myvm
memory: 4GiB
- name: Hot plug memory to already created and running VM (VM won't be restarted)
ovirt.ovirt.ovirt_vm:
name: myvm
memory: 4GiB
# Create/update a VM to run with two vNUMA nodes and pin them to physical NUMA nodes as follows:
# vnuma index 0-> numa index 0, vnuma index 1-> numa index 1
- name: Create a VM to run with two vNUMA nodes
ovirt.ovirt.ovirt_vm:
name: myvm
cluster: mycluster
numa_tune_mode: "interleave"
numa_nodes:
- index: 0
cores: [0]
memory: 20
numa_node_pins: [0]
- index: 1
cores: [1]
memory: 30
numa_node_pins: [1]
- name: Update an existing VM to run without previously created vNUMA nodes (i.e. remove all vNUMA nodes+NUMA pinning setting)
ovirt.ovirt.ovirt_vm:
name: myvm
cluster: mycluster
state: "present"
numa_tune_mode: "interleave"
numa_nodes:
- index: -1
# When change on the VM needs restart of the VM, use next_run state,
# The VM will be updated and rebooted if there are any changes.
# If present state would be used, VM won't be restarted.
- ovirt.ovirt.ovirt_vm:
state: next_run
name: myvm
boot_devices:
- network
- name: Import virtual machine from VMware
ovirt.ovirt.ovirt_vm:
state: stopped
cluster: mycluster
name: vmware_win10
timeout: 1800
poll_interval: 30
vmware:
url: vpx://[email protected]/Folder1/Cluster1/2.3.4.5?no_verify=1
name: windows10
storage_domain: mynfs
username: user
password: password
- name: Create vm from template and create all disks on specific storage domain
ovirt.ovirt.ovirt_vm:
name: vm_test
cluster: mycluster
template: mytemplate
storage_domain: mynfs
nics:
- name: nic1
- name: Remove VM, if VM is running it will be stopped
ovirt.ovirt.ovirt_vm:
state: absent
name: myvm
# Defining a specific quota for a VM:
# Since Ansible 2.5
- ovirt.ovirt.ovirt_quotas_info:
data_center: Default
name: myquota
register: ovirt_quotas
- ovirt.ovirt.ovirt_vm:
name: myvm
sso: False
boot_menu: True
bios_type: q35_ovmf
usb_support: True
serial_console: True
quota_id: "{{ ovirt_quotas[0]['id'] }}"
- name: Create a VM that has the console configured for both Spice and VNC
ovirt.ovirt.ovirt_vm:
name: myvm
template: mytemplate
cluster: mycluster
graphical_console:
protocol:
- spice
- vnc
# Execute remote viewer to VM
- block:
- name: Create a ticket for console for a running VM
ovirt.ovirt.ovirt_vm:
name: myvm
ticket: true
state: running
register: myvm
- name: Save ticket to file
ansible.builtin.copy:
content: "{{ myvm.vm.remote_vv_file }}"
dest: ~/vvfile.vv
- name: Run remote viewer with file
ansible.builtin.command: remote-viewer ~/vvfile.vv
# Default value of host_device state is present
- name: Attach host devices to virtual machine
ovirt.ovirt.ovirt_vm:
name: myvm
host: myhost
placement_policy: pinned
host_devices:
- name: pci_0000_00_06_0
- name: pci_0000_00_07_0
state: absent
- name: pci_0000_00_08_0
state: present
- name: Add placement policy with multiple hosts
ovirt.ovirt.ovirt_vm:
name: myvm
placement_policy: migratable
placement_policy_hosts:
- host1
- host2
- name: Export the VM as OVA
ovirt.ovirt.ovirt_vm:
name: myvm
state: exported
cluster: mycluster
export_ova:
host: myhost
filename: myvm.ova
directory: /tmp/
- name: Clone VM from snapshot
ovirt.ovirt.ovirt_vm:
snapshot_vm: myvm
snapshot_name: myvm_snap
name: myvm_clone
state: present
- name: Import external ova VM
ovirt.ovirt.ovirt_vm:
cluster: mycluster
name: myvm
host: myhost
timeout: 1800
poll_interval: 30
kvm:
name: myvm
url: ova:///path/myvm.ova
storage_domain: mystorage
- name: Cpu pinning of 0#12_1#13_2#14_3#15
ovirt.ovirt.ovirt_vm:
state: present
cluster: mycluster
name: myvm
cpu_pinning:
- cpu: 12
vcpu: 0
- cpu: 13
vcpu: 1
- cpu: 14
vcpu: 2
- cpu: 15
vcpu: 3
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
ID of the VM which is managed Returned: On success if VM is found. Sample: “7de90f31-222c-436c-a1ca-7e655bd5b60c” |
|
Dictionary of all the VM attributes. VM attributes can be found on your oVirt/RHV instance at following url: http://ovirt.github.io/ovirt-engine-api-model/master/#types/vm. Additionally when user sent ticket=true, this module will return also remote_vv_file parameter in vm dictionary, which contains remote-viewer compatible file to open virtual machine console. Please note that this file contains sensible information. Returned: On success if VM is found. |
Authors
Ondra Machacek (@machacekondra)
Martin Necas (@mnecas)