How to create an AWS cluster with SIM
The Sunlight Infrastructure Dashboard can be used to manage Sunlight cluster instances for both on-premise clusters (via a secure tunnel) and on-demand in AWS, providing a simple orchestration point to manage and monitor resources.
The following instructions provide information on how to deploy and manage a cluster within AWS. With the correct IAM credentials enabled, users can deploy clusters on demand on AWS baremetal nodes.
First, the user is required to log in with the credentials that were set in the previous setup guide.
At this stage, the user can click on "Create new Cluster", as depicted in the following image, in order to initialise the creation process of a new cluster. A cluster can be deployed with up to 5 baremetal nodes. One node will be defined as the master node, while the other nodes will be the slaves. Each node can be a different type of baremetal instance in the same availability zone:
Then the user is asked to enter the name of the cluster and to select the number of nodes for the cluster to be built.
The available and supported options for each node are as follows:
- The user may choose to use a spotInstance.
- The user must choose the bare metal instance type offered by AWS
- The user must choose the availability zone offered by AWS
- Finally, by clicking on submit, the build process is initiated.
As soon as the process is completed, the "State" changes to "Online".
Apart from the "Online" state, the user can also view the IP of the cluster's UI. By clicking on that IP the user is able to visit the login screen of the Sunlight cluster directly. The cluster is now ready to be configured (Please refer to the Sunlight userguide for the cluster configuration process).
A tooltip with the cluster ID is displayed by hovering the mouse cursor over the "id" field.
Upon clicking on the id link, the user can view the nodes associated with this newly built cluster.
At this stage the user is ready to begin using the cluster via the cluster manager UI and create Virtual Machines (VMs) as per normal operational needs. Upon clicking on the node link, all the virtual machines on that node are displayed. For each VM the user can see the ID, the name, the state of the VM, the public IP and the private IP.
In case the user decides to have a public IP associated with a VM, AWS managed Elastic Network IPs can be allocated to the specific cluster and then associate an IP to a specific VM, running on a particular baremetal node.
The following images describe this process:
The user can select the "Allocate IPs" menu option and choose a number of IPs that wants to reserve for this cluster.
Once the pool of IPs has been allocated, the user can then select the settings
icon next to an individual VM and assign an IP address from the pool. Please note that
on the Sunlight cluster, the VM network interface must be
attached to an external
network, a selection of which are pre-configured when the cluster is initialised.
The network must be one of the ENA NICs networks that are presented in the following picture.
The user can also release an AWS managed Elastic Network IP, by selecting "Release IPs" menu option and choosing the IPs that intends to release.
The user can also delete an AWS cluster, by selecting the "Delete" menu option.
Select "OK", in order to verify the deletion of the AWS cluster.