Create Virtual Machine (VM) snapshots in the DuploCloud Portal.

Creating a Virtual Machine(VM) Host Snapshot

1. In the DuploCloud Portal, navigate to Cloud Services -> Hosts. The Hosts page displays.

2. Select the Host you want to backup from the Name column.

3. Click Actions and select Snapshot.

Using VM Snapshot as an Image for creating a new host

Once you take a VM Snapshot, the snapshot displays as an available Image Id when you create a Host.

When you use autoscaling for Azure agent pools, you allow DuploCloud to manage your application's capacity requirements within your limits.

Creating an autoscaled Azure agent pool

In the DuploCloud Portal, with the Enable Autoscaling option selected. Each agent pool contains nodes backed by the virtual host machines.

DuploCloud supports various ways to scale the workload, depending on the underlying Azure services being used.

• Autoscaling Azure Agent Pools

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.

Adding a Host (VM)

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.

1. Ensure you have selected the appropriate Tenant from the Tenant list box at the top of the DuploCloud Portal.

2. In the DuploCloud Portal, navigate to Cloud Services -> Hosts.

3. Select the tab that corresponds to the type of Host you want to create (HOST or BYOH), and click Add.

1. In the Friendly Name field, specify a unique name for the Host.

2. Define the Subnet, select the Instance Type, enter your Username and Password, and specify whether to enable a Public IP.

3. Optionally, enter a computer name in Computer Name field in the Advanced Options.

4. In the Encryption list box, select Off or On.

5. Optionally, select the Disk Controller Type in the Advanced Options. The disk controller type is set to SCSI by default. If you select NVME, specify the supported instance size.

6. Optionally, select Standard or Trusted Launch in the Security Type field. If you select Trusted Launch, enable or disable Enable Secure Boot and vTPM.

7. Click Add.

Viewing Hosts (VMs)

To view your Hosts (VMs), navigate to Cloud Services -> Hosts and select the Host tab.

Creating Kubernetes StorageClass and PVC constructs in the DuploCloud Portal.

See Kubernetes StorageClass and PVC.

Host abstraction and isolation

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

Fleet: This is applicable if the VM is to be used as a host for container orchestration by the platform. The choices are:

• Linux Docker/Native: To be used for hosting Linux containers using the Built-in Container orchestration.

• Docker Windows: To be used for hosting Windows containers using the Built-in Container orchestration.

• 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.