AZure

Set up Kupboard clusters

Introduction

This section describes how to create and configure Virtual Machine instances to build a kupboard cluster on AZure.

Virtual Machine Instance

Kupboard clusters can be configured in a variety of ways depending on the service and application. In this example, we will create 1 server for the admin cluster, 1 server for the gateway cluster, and 4 servers for the service cluster.

You need to create six Virtual Machine instances as in the table below. OS for all instances must be Ubuntu18.04 or 20.04. The size of additional disks should change depending on services or packages installed on the service cluster

Cluster	Instance Type	Quantity	Boot Disk	Additional Disk
Admin	B2s <	1	50GB	N/A
Gateway	B2s <	1	50GB	N/A
Service	B2ms <	4	50GB	50GB <

B2s 2 vCPUs, 4G RAM
B2ms 2 vCPUs, 8G RAM

Firewall

Create a firewall for a subnet.

Cluster	Inbound	Source
All	22	0.0.0.0/0
	1 - 65535	Subnet
Admin	80,443	0.0.0.0/0
Gateway	80,443	0.0.0.0/0

Cluster	Outbound	Destination
All	1 - 65535	0.0.0.0/0

SSH Key

In order to set up the servers, you need a SSH key pair to enable automatic azureuser account login to the individual server. AZure provides the SSH public key service whereby a new SSH key pair is generated. The private key is downloaded into the local PC. The public key is mapped into a server as it is created.

The downloaded private key is moved into the local PC’s data/certs. It should be renamed to ssh.pem. You can log into the server like below.

$ ssh -i ssh.pem azureuser@<server-ip>

At the user initialization stage of kupboard setup, the azureuser account login is automatically done.

$ kupboard setup --init-user --root-username azureuser

Server Configuration Result

Virtual machines

SSH public key

As the first Virtual Machine instance is created, a new SSK key pair must be generated. The next Virtual Machine servers should use the SSK public key created by the first instance.

Port Rules

Virtual Network

Data

Move to Data