search

Creating a Model through Terraform

hashtag
Prerequisite: Prepare your Terraform Templates

Before starting, you must have your Terraform configuration files (.tf) ready and organized. Cloud Manager expects a specific structure:

  • Main Folder: This must contain the .tf files that define the resources for each individual VM instance (the VM itself, network interfaces, etc.). It is mandatory that the virtual machine resource has the vdi_instance tag for Cloud Manager to recognize it.

  • Shared Folder (Optional): You can use this folder to define resources that will be shared by all instances, such as security groups, virtual networks, or subnets.

circle-info

Note

To learn more about the composition of a Terraform template, see VM Template and Multiple Instantiation.

circle-exclamation

Important

The automation capability is limited by the resources that the Verge.IO supports. Your template must conform to what Verge.IO makes available.

1

hashtag
Start the Wizard and Select "Custom" Mode

  1. In Cloud Manager, click on Add and select VDI/DaaS Model.

  2. Choose Verge.IO as your provider.

  3. On the Model Selector screen, select Use custom configuration. This will tell the wizard that you want to upload your own Terraform templates instead of using a preconfigured one.

2

hashtag
Upload Your Template Files

  1. Select the Verge.IO credentials.

  2. The wizard will present you with two tabs to upload your template folders:

    • VM Template: Upload your main folder here.

    • Shared Template: Upload the folder with shared resources (if you have one).

3

hashtag
Set the VM Template Parameters

The Parameters step allows setting the template parameters as defined in the uploaded JSON file.

Option
Description

Image Name

Enter the exact name of the Snapshot you obtained in the Prerequisites step above. The deployment will use this snapshot as a template (Golden Image) for all new VMs.

ISO Name

(Optional) Select a driver or application ISO file. Leave blank if your snapshot already contains necessary drivers, such as VirtIO.

CPU

Specify the number of virtual processors (vCPUs) to be allocated to each VM instance created by this model.

Memory

Define the maximum storage capacity for the VM's primary disk. Ensure this is equal to or greater than the source Snapshot size.

Disk size

Define the maximum storage capacity for the VM's primary disk. Ensure this is equal to or greater than the source Snapshot size.

Admin Username

Enter the local administrative username for the guest OS. This account is used by the broker to perform initial configuration tasks.

Admin Password

The password associated with the local Admin username. This is required for the automated customization of the VM.

Set Specific DNS

Enable this to manually define preferred and alternate DNS servers if the VM should not use the defaults provided by the network.

Join to a Domain

Enabling this option will reveal the following fields.

DC Server Address

(Visible if Domain Join is enabled) Enter the IP address or FQDN of the Domain Controller responsible for the target domain.

Domain User with Join Permissions

Provide the credentials of an account authorized to add new computer objects to the domain.

Domain User Password

The password for the authorized domain user.

Set Distinguished Name

Enable this to specify a particular Organizational Unit (OU) in Active Directory where the computer objects will be stored.

Distinguished Name

(Visible if Set Distinguished Name is enabled) Enter the full LDAP path (e.g., OU=VDI,DC=company,DC=com) for the computer account.

Network Name

Go to Networks Dashboard > Networks in your Verge.IO Dashboard and select the Verge.IO virtual network to which the new VMs will connect.

The provider-specific steps for creating a Verge.IO model from Terraform Templates end here. The rest of the configurations in the wizard are universal.

hashtag
Return to the Main Workflow to Finish the Configuration:

PreviousCreating a Model from a Golden Image

Last updated