Create a Model Using a Built-in Template
Note
Please be aware that the process of creating models in Thinfinity Cloud Manager varies slightly depending on the cloud service provider you are using. While this series of tutorials will focus on IONOS examples, it is important to note that the options available in the wizard depend on the selected cloud provider.
A model is the parametrization of all the characteristics that we can give to a VM. These parameters are what Thinfinity will use to deploy all the instances we will be able to access through Cloud Manager. The following steps will guide you through the process of creating your first template-based model:
Select a Built-In Model
The Model selector helps determine which VM configuration best suits your needs based on the nature and intensity of your workflows. Depending on the tasks to perform—whether it’s simple administrative work, CPU-heavy processing, or GPU-accelerated graphics tasks—you can select the appropriate VM family to ensure optimal performance in your cloud environment.
Here are the models available for each cloud provider.
HyperV
Golden Image cloning*
-
-
VMware
Golden Image cloning*
-
-
Proxmox
Golden Image cloning*
-
-
Verge.io
Golden Image cloning*
-
-
Note
*To create a HyperV or VMware model, you need to previously have a VM Golden Image to clone.
Select the Cloud Provider Credentials
Select or enter your cloud provider credentials: if you already entered them in the Credentials tab, select Existing. If not, define new credentials by clicking in New.
Configure the VDI/DaaS Model Parameters
Configure your model parameters. These will vary depending on the cloud provider. In this case, as previously stated, we are using IONOS as example. After you entered all the required parameters, click Next.
Use custom image
Select this option to use a custom image for your model. An additional field will become available where you can enter the path to the image/snapshot file.
IONOS Image Name
This field is completed by default with the latest edition of the Windows server, edit if necessary.
Cube Type
This field is completed by default with the basic IONOS cube type, edit if necessary.
Datacenter location
This field is completed with the default datacenter location, edit if applicable.
Use existing datacenter
Enable this option to use an existing datacenter to host your model. An associated field will become available and you can enter the name of the existing datacenter.
New Datacenter Name
Enter the name of the new datacenter that will be created and that will host your model.
Use Existing LAN
Enable this option to use an existing LAN for your datacenter. An associated field will become available and you can enter the name of the existing LAN.
New LAN Name
Enter the name of the new LAN for your datacenter.
Public Access LAN
Select this option to enable public access to the LAN of your datacenter.
Assign Public IP Address
Select this option to assign a public IP address to your data center.
Admin Password
Set a password to access the VMs. It must be at least 12 characters long and include both letters and numbers. The default username to access the VMs is "administrator".
Configure the VM Access Options
In the next step of the wizard define how instances will be accessed:
Public IP
Assigns a public IP address, allowing direct internet access.
Private IP
Assigns a private IP address, allowing only connections from within the virtual network.
Agent ID
Assigns a Agent ID value, allowing only connections from registered agents on the Thinfinity Workspace network.
None
Instances are not part of a pool, operating independently without load balancing. For details, see Connection options.
Breadth-First
Distributes new connections evenly across available hosts in a pool.
Depth-First
Assigns new connections to a single host until capacity is reached, then moves to the next.
Use naming prefix: Use the Prefix and Digits fields to easily identify your new instances with a prefix and/or digits if needed.
Configure VM Deployment Options
In the next step of the wizard configure the Deployment options.
The default option is On Demand, which will trigger a deployment when an Access Profile is accessed. When selecting Scheduled, instances are automatically deployed at specific times according to the predefined schedule.
You can also set the initial number of instances, the number of standby (lazy) instances, and the maximum instances for this model. This maximum defines the upper limit for automated deployment; however, admins retain the ability to manually add further instances beyond this threshold.
Configure How VMs Turn On and Off
In the next step of the wizard define how instances turn on and off.
On Demand
Manually set a fixed number of minutes to turn an instance off after disconnecting from it.
Start/Stop Ranges
Instances automatically turn on and off at specific times according to a predefined schedule.
Add Schedule
Click to set schedules for automatically powering instances on and off. This will reveal additional fields to configure the schedule settings.
If both options are enabled (On Demand - enabled and at least one schedule defined) you will be able to use a hybrid deployment mode that combines On Demand and Scheduled methods, allowing VMs to be automatically created as users request them while also pre-provisioning a set number of desktops during peak hours to ensure availability.
Once the model wizard is complete, a new option - Both - will appear in the Power tab within the model editing menu:
Next Steps
Having successfully created a model using a built-in template, the next steps are to move on to:
Exporting and importing built-in models for backup, sharing and migration.
Deployment of instances, which is the next step in the provisioning process, and
Access Profile creation, which acts as a bridge that grants end users access to the newly created instances.
Additionally, explore how to create a model using Terraform templates.
Last updated