Hosts (VMs)
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.
For ease of use, create a link to the Azure Console from a Host page Action Menu.
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.
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 DevOps -> Hosts.
Click the tab that corresponds to the type of Host you want to create (HOST or BYOH).
Click Add.
It is not necessary to explicitly define Hosts. Instead, you can use Azure Agent Pools and VM Scale Sets.
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.
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
Last updated
