Microsoft Azure Deployment Guide
Use this guide to plan an Apporto hybrid cluster in your own Microsoft Azure subscription. On Azure there is no VM file to import. Apporto deploys the cluster nodes from Apporto’s Azure image with a deployment template: a file that tells Azure which resources to create. After that, you create the cluster from the node UI, the same way as on-premises.
The template also creates the front door: an Azure Application Gateway that receives your users’ traffic and passes it to the cluster.
On Azure, the front door is the only supported way in for your users. Your own load balancer cannot be used in its place.
Prerequisites
Security
-
SSH access to the cluster nodes is not permitted, the same as on-premises. Azure requires an SSH key on every Linux VM, so the installer makes one and deletes its private half before anything is deployed. Nobody keeps it. Nodes are built on Ubuntu LTS.
-
During the install, the manager node has a public address so that the installer’s browser can open the node UI. Only the installer’s own address can reach it.
Also complete Prerequisites and Prerequisites for Cluster Install. Prepare these items in Azure before the install:
|
Item |
Details |
|---|---|
|
Image access |
Send your Azure subscription ID and tenant ID to Apporto. Apporto then gives your subscription access to the Apporto image. |
|
A resource group |
A new resource group for the cluster only, in the region you want. Do not put anything else in it, so that the cluster can be removed by deleting the group. |
|
Rights for the installer |
Contributor (or Owner) on the resource group. The resource providers Microsoft.Compute, Microsoft.Network and Microsoft.KeyVault must be registered on the subscription. |
|
Quota |
For the default cluster: 2 vCPUs of the DSv5 VM family and 4 vCPUs of the ESv5 VM family in the region. More or larger workers need more. |
|
The front door certificate |
A Key Vault with the certificate for your users’ host name. It holds two secrets:
On the vault, turn on Azure Resource Manager for template deployment. This lets Azure read the certificate while it deploys. The installer needs the permission |
|
A DNS name for users |
You point it at the front door after the deployment. The certificate must be for this name. |
|
Who may reach the front door |
The whole internet, or a range of addresses such as your own network. |
|
Your servers |
The cluster has its own virtual network, If these servers are not in this Azure network, connect the two networks by peering or VPN. Then |
Install Steps
Your Apporto technical services manager (TSM) runs these steps with you.
-
Apporto confirms that your subscription can read the Apporto image.
-
Apporto runs read-only checks against your subscription: the resource group, the resource providers, the quota, the image access, the Key Vault settings, and that your Apporto control plane answers. These checks change nothing.
-
Apporto previews the deployment, then deploys the template into your resource group. In Apporto’s testing, the deployment took about 11 minutes. The template creates:
-
a virtual network with one subnet for the nodes and one for the front door
-
a network security group with the rules on the Prerequisites page
-
a NAT gateway, the nodes’ only way out to the internet
-
the front door: an Azure Application Gateway that receives your users’ traffic on port 443
-
one manager node (
Standard_D2s_v5) and two worker nodes (Standard_E2s_v5), unless you agreed other counts or sizes with Apporto
-
-
Point your users’ DNS name at the front door’s public address.
Post-Deployment
-
Your TSM gives you the manager node’s public address. Open
https://[manager node public address]in a browser. The node uses a self-signed certificate, so the browser shows a warning. Accept it. -
This opens the On-Premises Cluster Management tool, which is included in every node. Every node appears in its Node Discovery list within about 2 minutes.
If a node is still missing after about 2 minutes, click Refresh.
Create Cluster
Review the following:
Prerequisites for Cluster Install
-
Select all the nodes, then click Create Cluster.
-
The browser signs in to your Apporto control plane. Use an MSP Admin account.
-
Click Allow when the browser asks. You then return to the install wizard.
-
Continue with Running the on-prem cluster install wizard from its step 2. Step 1 is not needed on Azure.
-
In the wizard’s step 3, enter your users’ DNS name as the hyperstream FQDN, in lowercase.
After the install
When the install has finished, your Apporto TSM removes the manager node’s public address. After that, the node UI can be opened only from a network that is connected to the cluster’s virtual network, by peering or VPN.
Removing the cluster
These resources are billed until you delete them: the VMs, the front door, the NAT gateway and the public addresses. To remove the cluster, delete its resource group in Azure.