VM Template

• Overview

Overview

The VM template object allows you to specify the configuration to deploy 1 or more VMs. This is where you can state how many of a VM type you require, what provisioners to use, firewall rules to create, as well as the OS type (unless defined globally).

All VM templates are defined within the "template" array at the root of the JSON template file, and requires a "type" value of "vm":

{
    "template": [
        {
            "type": "vm"
        }
    ]
}

Properties

Below are the properties that are used in defining the VM template object

Name	Type	Required	Description
count	int	yes	The number of VMs to deploy for the template; must be greater than or equal to 1
firewall	firewall object	no	The local inbound/outbound firewall rules for the current VM template
os	OS object	no (when global os object defined)	The local OS object for this VM template. Note: not required if a global OS object is present and appropriate
port	int	no	The port the VMs are to be load balancer against. Note: Only required if count > 1 and useLoadBalancer is true or not supplied
provisioners	string array	no	A string array of provisioner keys, that will be run in order given to provisioner each VM
tag	string	yes	The tag-name of this VM template. ie, if core then VMs deployed will have the name [rg-name]-core[index]
useAvailabilitySet	boolean	no	Default: true. Whether or not the VMs should be placed into an Availability Set
type	string	yes	Specifies the type of template object, can be either vmor vpn
useLoadBalancer	boolean	no	Default: true. Whether or not the VMs should be load balanced
usePublicIP	boolean	no	Whether or not the VMs should have a public IP address