Resources for a 3 master, 30 private agent and 3 public agent (3-30-3) compute cluster.
Resources for a 3 master, 30 private agent and 3 public agent (3-30-3) compute cluster.
Mesosphere (creator of Mesos and DC/OS) has great documentation on how to establish a DC/OS cluster on Amazon that can be found here.
Step 1: Navigate to the Mesosphere Amazon launch page and click the 'Get Started on AWS For Free' button. Read through the 'System' and 'Software' requirements. As a prerequisite you must have an Amazon EC2 Key Pair for the same region as your cluster. Key pairs cannot be shared across regions. The AWS key pair uses public-key cryptography to provide secure login to your AWS cluster. If you don't already have a key pair for the region you wish to deploy a DC/OS cluster follow these instructions
Step 2:
After reviewing Installing DC/OS on AWS documentation
launch the DC/OS Template on CloudFormation and select the region and number of masters (1 or 3). You must have a key pair for your selected region.
Step 3:Out of the box, the template supplied by Mesosphere, allocates instances of type m3.xlarge. We have found that using instances of type m3.2xlarge works better for this demo. So we recommend downloading the default template and modifying it to use m3.2xlarge for its instance type. To do that, open the link in the default page that shows up in the Select Template page and save it to disk.
Step 4:
Step 5:
After saving the file to disk, open it in your favorite text editor and look for the three JSON entries: Mappings.Paramters.MasterInstanceType, Mappings.Paramters.PublicSlaveInstanceType, and SlaveInstanceType. For all three, change m3.xlarge to m3.2xlarge and save the file.
Step 6:
Step 7:
Once you modify and save the file, go back to the Create stack -> Select Template screen and choose the "Upload a template to Amazon S3" option and choose the json file you just saved to disk and click the "Next" button.
Step 8:
On the "Specify Details" page, do the following:
- Provide a "Stack Name"
- For KeyName, select the private key to use to create the instances. Make sure you have access to the private key as you may need it to ssh to your cluster later.
- Set OAuthEnabled to false
- Set PublicSlaveInstanceCount to 3 for a Highly Available (HA) Master (you can leave this to one, but your demo will not be HA)
- Set SlaveInstanceCount to 10
- Click Next
Note: You can modify the instance counts as you see fit, but during testing these are the configurations that provided the best experience.
Step 9:
Under Options, you can set any metadata you want. We recommend adding a cluster-owner key/value pair so you know who to contact if there any issues that arise with the cluster. Once you've entered the data you'd like, hit Next.
Step 10: ...
Step 11:
Click the checkbox next to "I acknowledge that AWS CloudFormation might create IAM resources" and push the Create button.
Step 12:
If you haven't created any clusters before, you might see this screen. If you do, then push the refresh button in the top right hand corner.
Step 13:
You'll see updates as all the various components are created.
Step 14:
Step 15:
Once the cluster is done creating, you'll see the status of your cluster set to "CREATE_COMPLETE."
Step 16:
To see the pulic hostname of your DC/OS Dashboard, select the cluster you just created in the grid, and then select the "Outputs" tab. You can get to your DC/OS dashboard by copying the value of the DnsAddress row andpasting it into a browser.
Step 17:
Congratulations: You now have a DC/OS cluster in place on Amazon Web Services.