Please visit the Managed Object Reference section to know more about these references.Īfter a VM Template is instantiated, the life-cycle of the resulting virtual machine (including creation of snapshots) can be controlled through OpenNebula. Please visit the Managed Object Reference section to know more about these references. Managed Object Reference of the vCenter cluster related with the template. Managed Object Reference of the vCenter datastore.
The Deployment Folder is a path which uses slashes to separate folders. (Optional) If you use folders to group your objects like VMs and you want a VM to be placed inside an specific folder, you can specify a Deployment Folder where the VM will be created. If this attribute is set, its value will be used to confine this the VM in the referred resource pool. (Optional) By default, the VM will be deployed to the default resource pool. You can find more information about contextualization in the vcenter Contextualization section. Multi-value - Only VNC supported, check the VM template reference.Īll sections will be honored. Valid MODELs are: virtuale1000, virtuale1000e, virtualpcnet32, virtualsriovethernetcard, virtualvmxnetm, virtualvmxnet2, virtualvmxnet3. This does not have to relate to the CPUs used by the vCenter VM Template, OpenNebula will change the value accordingly Physical Memory in MB to be used by the VM. OpenNebula creates VM Templates using the import tools, but for your reference a VM Template definition in OpenNebula that represents a vCenter VM Template should contain the following attributes:
#CREATE VMDK FROM FOLDER HOW TO#
To learn how to use VMs and VM Templates you can read the Managing Virtual Machines Instances and Managing Virtual Machine Templates, but first take into account the following considerations. VCenter Virtual Machines ¶ vCenter VM and VM Templates ¶