Microsoft Azure

Azure is Microsoft's cloud computing platform allowing users to create and run Virtual Machines. We have a Tillered VM Image hosted in the Azure Marketplace allowing for a easy cloud node setup.

Prerequisites

• Have an Microsoft Azure account and access to the Azure Console.
• Create an account on the Tillered Hub.

Setting Up a Tillered Node

1. Log into Azure and navigate to Virtual Machines.
2. Click Create and select Azure virtual machine.
3. In the Image field, click See all images to open the marketplace and search for Tillered. Select the Tillered Virtual Machine image.

4. Select a VM size with at least 2 vCPUs and 4 GB RAM. The Standard B2s is a good starting point.
5. Configure your authentication (SSH public key or password) and any other settings, then review the summary and click Create.

6. The deployment may take 10-12 minutes. Azure will show the progress on the deployment overview page.

7. Once the deployment completes, go to the VM overview page and note the Computer name and Private IP address. You will need both when registering the node.

Enable IP Forwarding

Tillered CEN nodes forward network traffic that is not addressed to the VM itself. By default, Azure drops any traffic where the VM is not the source or destination. You must enable IP forwarding on the VM's network interface so tunneled traffic is not silently dropped.

Using the Portal

1. Go to your Tillered VM, select Networking > Network settings, and click the network interface name.

2. Under Settings, select IP configurations.
3. Set Enable IP forwarding to Enabled and click Apply.

Using the CLI

az network nic update \
    --name <nic-name> \
    --resource-group <resource-group> \
    --ip-forwarding true

Replace <nic-name> and <resource-group> with the NIC name and resource group of your deployed VM.

Register Your Node

After deploying the VM and enabling IP forwarding, register the node with your Tillered account. You will need the Computer name and Private IP address from the VM overview page.

The node will configure itself to the virtual Tillered network. It may reboot during this phase, but it will be ready to use when the Tillered Hub node page shows the node as Provisioned.