Multai load balancer uses Runtime instances as hosts to run the Load Balancers.
We want to allow our users to effortlessly run Runtime Nodes as Elastigroups, meaning that the Runruntimes will be fully managed by Elastigroups. Using Elastigroups as a workload management solution will also include scaling rules and monitoring for the Runtimes.
To integrate the Elastigroup with Multai please follow these instructions:
Step One - Creating a Deployment and Runtime
Navigate to the Multai Runtime screen and create a deployment
Provide a name for the Deployment That will be a logical container for the Runtimes
After the Deployment is created, Copy on the Deployment ID to be used in the next section
Step Two - Create an Elastigroup
Follow this guide: Creating an Elastigroup while following these steps:
- We recommend starting with a Capacity of 2 instances setting the target and minimum to "2"
- The subnets that you choose will have access to an Internet Gateway
- We recommend using "m" type instances such as: m3.xlarge or m4.xlarge instance types
- Select one of the following AMIs according to the region
us-east-1 (N. Virginia) spotinst.io/runtime-0.3.14-amazon-linux-2-amd64-hvm-ebs-2018-03-20 ami-c6af7abb us-west-2 (Oregon) spotinst.io/runtime-0.3.14-amazon-linux-2-amd64-hvm-ebs-2018-03-20 ami-58c75b20 ap-southeast-1 (Singapore) spotinst.io/runtime-0.3.14-amazon-linux-2-amd64-hvm-ebs-2018-03-20 ami-fd590481 eu-west-1 (Ireland) spotinst.io/runtime-0.3.14-amazon-linux-2-amd64-hvm-ebs-2018-03-20 ami-5aefba23
* If you wish to create the deployment in another region please reach out to email@example.com
- Use the following User data script in the "Compute" tab under Additional Configurations
#!/usr/bin/env bash SPOTINST_ACCOUNT_ID=act-xxxxx \ SPOTINST_DEPLOYMENT_ID=dp-xxxxx \ SPOTINST_TOKEN=<ENTER YOUR TOKEN HERE> \ lb-installer --log.verbosity=5
- Selecting the Multai integration in the Integrations section under "Compute" tab and selecting the deployment from the drop-down menu
- Hit next to move to the scaling Tab
Optional - Step three - Create Scaling Rules
This is an optional step introducing load-based scaling to the deployment cluster. For CPU centric loads you can create a target scaling rule based on desired CPU usage. We recommend setting the CPU usage to 60% for optimal utilization of resources.
If your workload has more network consumption than CPU please contact our support (firstname.lastname@example.org) to get advice on scaling based on active connections etc.
Continue with the group creation and launch you Runtimes
Step four - Create Load Balancer
Create the Load balancer in the console:
Step five - Validate the runtime show under the deployment
After the instances finished launching, you should see new hosts under the Deployment Runtime screen.