Backup your hosts (VMs)
Create Virtual Machine (VM) snapshots in the DuploCloud Portal.
In the DuploCloud Portal, navigate to Cloud Services -> Hosts. The Hosts page displays.
Select the Host you want to backup from the Name column.
Click Actions and select Snapshot.
Once you take a VM Snapshot, the snapshot displays as an available Image Id when you create a Host.
Dynamically configure Azure agent pools for optimum performance
When you use autoscaling for Azure agent pools, you allow DuploCloud to manage your application's capacity requirements within your limits.
In the DuploCloud Portal, create an Azure agent pool with the Enable Autoscaling option selected. Each agent pool contains nodes backed by the virtual host machines.
Using Hosts in DuploCloud
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. These could be meant for:
AKS Worker Nodes
Worker Nodes (Docker Hosts) if built-in container orchestration is used.
Regular nodes that are not part of any container orchestration, where a user manually connects and installs applications. For example, when using a Microsoft SQL Server in a VM, when running an IIS application and in other custom use cases.
Add a Virtual Machine Host. DuploCloud AWS supports Host (Azure Host) and BYOH (Bring Your Own Host) types. Use BYOH for any VM that is not an Azure Host.
Ensure you have selected the appropriate Tenant from the Tenant list box at the top of the DuploCloud Portal.
In the DuploCloud Portal, navigate to Cloud Services -> Hosts.
Click the tab that corresponds to the type of Host you want to create (HOST or BYOH).
Click Add.
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.
If a VM is used for container orchestration, ensure that the Image ID corresponds to the Image in the container. Any name that begins with Duplo is an image that DuploCloud generates for Built-in container orchestration
For ease of use, from a Host page Action Menu.
It is not necessary to explicitly define Hosts. Instead, you can use and .
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 .
Autoscaling with Azure Agent Pools and Kubernetes
DuploCloud supports various ways to scale the workload, depending on the underlying Azure services being used.