105 lines (97 loc) · 5.59 KB

sidebar_position	9
sidebar_label	vCenter VM From Template
hide_table_of_contents	true

vCenter VM From Template Deployment Path Attributes

The following attributes would be used to define the vCenter VM From Template:

Attribute	vCenter shell version	Description
Cloud Provider	All	Name of the vCenter cloud provider resource to be used
vCenter Template	All	Path to the vCenter template to use in the virtual machine's creation. Path is relative to the datacenter and must include the template name, for example: `My-Templates/Template1`
Behavior During Save	All	(Applies to the Save and Restore paid add-on) The VM's state while the sandbox is being saved. Options are Remain Powered On and Power Off. Inherit: (Default) Uses the setting defined on the vCenter cloud provider resource Remain Powered On: The VM will remain powered on during the saving state. Power Off: If the VM was powered on before the sandbox entered the saving state, the VM will shut down (power off) for the duration of the save. :::note Notes The value configured here overrides the configuration in the vCenter cloud provider resource, see Add VMware vCenter Cloud Provider Resource. After save has ended, the VM returns to its state prior to saving, regardless of the behavior during the save. :::
Saved Sandbox Storage	All	(Applies to the Save and Restore paid add-on) During the saving process, CloudShell creates a clone of the sandbox's App VMs in this vCenter storage, which CloudShell will later use to restore the VM when the user restores the saved sandbox. See Save a Sandbox for more information. For storage purposes, these VM clones can be stored in a different data storage than the one configured in the VM Storage attribute defined on the vCenter cloud provider resource. The storage can be either a datastore or a datastore cluster. For example: datastore1 or clustername/datastore1. :::note Setting a value in the App template’s attribute will override the value in the Saved Sandbox Storage attribute on the vCenter resource. See Add VMware vCenter Cloud Provider Resource. :::
Customization Spec	2^nd Gen only	Name of the vSphere VM Customization Specification to apply to the App's VM.
Hostname	2^nd Gen only	(Only applies to Windows and Linux VMs) The hostname to set on the VM. :::note If Customization Spec is specified, the value specified in the Hostname attribute will be used. If Customization Spec is not specified, a new one will be created for the VM. For Windows VMs, make sure to specify a password in the App resource page :::
Private IP	2^nd Gen only	(Only applies to Windows and Linux VMs) The private static IP to set on the first vNIC of the VM. If there's a default gateway, specify it after the private IP. For example: "192.168.4.124:80.114.1.87" where 80.114.1.87 is the default gateway :::note Notes If there is no gateway, the .1 IP of the same subnet will be used as the gateway. So, for private IP "192.168.4.124", gateway "192.168.4.1" will be used. It is also possible to provide a subnet mask here. For example: "192.168.4.124/24:80.114.1.87" If Customization Spec is specified, the value specified in the Private IP attribute will be used. If Customization Spec is not specified, a new one will be created for the VM. For Windows VMs, make sure to specify a Password in the App resource page. If Customization Spec is specified, the value specified in the Private IP attribute will be used. If Customization Spec is not specified, a new one will be created for the VM. For Windows VMs, make sure to specify a Password in the App resource page. :::
CPU	2^nd Gen only	Number of CPU core s to configure on the VM.
RAM	2^nd Gen only	Amount of RAM (GB) to configure on the VM.
HDD	2^nd Gen only	Allows to add/edit hard disk size to the VM. The syntax is semi-colon separated disk pairs 'Hard Disk Label: Disk Size (GB)'. For example: 'Hard Disk 1:100;Hard Disk 2:200'. Short-hand format is also valid: '1:100;2:200'.