Hosts (VMs)
Using Hosts in DuploCloud
Last updated
Was this helpful?
Using Hosts in DuploCloud
Last updated
Was this helpful?
Once we have the Infrastructure (Networking, Kubernetes cluster, and other common configurations) and an environment (Tenant) set up, the next step is to create VMs. In DuploCloud, you can create the following types of hosts for your workloads:
Host (VM): Standard virtual machines for general-purpose workloads, including application hosting and databases.
VM Scale Set: A group of identical VMs that can automatically scale based on demand, ideal for horizontally scalable applications.
Azure Agent Pool: A set of VMs used in container orchestration environments like Azure Kubernetes Service (AKS).
Availability Set: A collection of VMs spread across fault and update domains to ensure high availability and minimize downtime.
BYOH (Bring Your Own Host): For users with pre-configured VMs or non-Azure infrastructure that they want to bring into DuploCloud. Use BYOH for any VM that is not an Azure Host.
Select the appropriate Tenant from the Tenant list box.
Navigate to Cloud Services -> Hosts.
Select the Host tab.
Click Add. The Add Virtual Machine pane displays.
In the Friendly Name field, specify a unique name for the Host.
Define the Subnet for the Host.
Select the Instance Type that fits your requirements.
Enter the Username and Password for the Host.
Specify whether to enable a Public IP for the Host.
Optionally, check the Advanced Options box and configure advanced settings.
Click Add.
Select the appropriate Tenant from the Tenant list box.
Navigate to Cloud Services → Hosts.
Select the VM Scale Set tab.
Click Add. The Add VM Scale Set pane displays.
In the Name field, provide a unique name for the VM Scale Set.
Select the Subnet from the available options.
Choose the Instance Type for the VMs in the scale set (e.g., 2GB, 4GB, etc.).
Define the Capacity, specifying the desired number of VMs for the scale set.
Select the Image Id for the base image of the VMs (e.g., Ubuntu20_04).
Choose the Fleet to which the VM Scale Set will belong.
Optionally, enter an Allocation Tag for organizational purposes.
Provide the Username and Password for accessing the VMs in the scale set.
Click Add to create the VM Scale Set.
Select the appropriate Tenant from the Tenant list box.
Navigate to Cloud Services → Hosts.
Select the Azure Agent Pool tab.
Click Add. The Add Azure Agent Pool pane displays.
In the Name field, enter a unique name for the agent pool.
Choose the Instance Type (e.g., 2GB, 4GB, etc.).
Set the Min Capacity, specifying the minimum number of nodes in the agent pool.
Set the Max Capacity, specifying the maximum number of nodes in the agent pool.
Set the Desired Capacity, specifying the desired number of nodes.
Select the OS for the agent pool (e.g., Linux, Windows).
Choose the OS SKU, (e.g., Ubuntu).
Optionally, enter an Allocation Tag for organizational purposes.
Specify the Availability Zones in which the agent pool nodes should be located.
Choose the Scale Set Priority (e.g., Regular, Spot).
Set the Max Pods Per Node, specifying the maximum number of pods for each node.
Optionally, select Enable Autoscaling to automatically scale the agent pool based on usage.
Click Add to create the Azure Agent Pool.
Select the appropriate Tenant from the Tenant list box.
Navigate to Cloud Services → Hosts.
Select the BYOH tab.
Click Add. The Add BYOH pane displays.
In the Friendly Name field, enter a unique name for the Host.
In the Direct Address field, enter the direct IP address of the Host.
In the Fleet Type field, select the appropriate fleet type (e.g., Linux Docker/Native).
In the Username field, enter the username for accessing the Host (optional).
In the Password field, enter the password for the Host (optional).
Optionally, provide a Private Key for SSH access if necessary.
Click Add to create the BYOH Host.
To view your Hosts (VMs), navigate to Cloud Services -> Hosts and select the Host tab.
While lower-level details such as IAM roles and security groups are abstracted, deriving instead from the Tenant, only the most application-centric inputs are required to set up Hosts.
Most of these inputs are optional and some are available as list box selections, set by the administrator in the Plan (for example, Image ID, in Host Advanced Options).
There are two additional parameters
None: To be used for non-Container Orchestration purposes and contents inside the VM are self-managed by the user.
Allocation Tags (Optional): If the VM is used for containers, you can optionally set a label on the VM. This label is specified during Docker application deployment to ensure that the application containers are pinned to a specific set of nodes, giving you the ability to split a tenant further into separate pools of servers and deploy applications on them.
It is not necessary to explicitly define Hosts. Instead, you can use and .
For detailed instructions, see the .
See .
Fleet: This is applicable if the VM is to be used as a host for by the platform. The choices are:
Linux Docker/Native: To be used for hosting Linux containers using the .
Docker Windows: To be used for hosting Windows containers using the .
