We setup a dev env for DC/OS in AWS (subnets, multi-az, ags groups, ami images, etc), tagged everything as
Included are the cloudformation and packer scripts. Hope it helps you get setup. Feedback is welcome.
We in this case is our client, DC/OS support, Amazon support, and Mammatus. We did this instead of using the canned Amazon support because we needed to run masters, and agents in multiple AZs per region.
Production servers are setup, and integration servers are also setup. It is all immutable infrastructure (for the most part). We have scripts that build a DC/OS cluster from nothing to the full network, security, ELB, auto-scale groupsfor public agents & private agents, master instances, user-data etc. stack using AWS cloud formation.
The two parts that are not yet automated are the enterprise
All the AMI image creation is automated as well. The cloud formations point to AMI images which we create using Packr that have all of the advance prequisites for DC/OS. Packr has excellent support for Amazon AMIs as well as Docker, and just about every other image container that exists. We choose CentOS over Amazon Linux so we are less locked in and could move images to other clouds or containers more readily.
The cloudformation script has a drop down cloudformation parameter which picks which env (prod, int, dev) and it sets up all of the CIDR addresses etc. via cloudformation mappings.
The DC/OS advanced install tar files and config were uploaded to S3. We use IAM roles, and s3 bucket policies to lock down the S3 bucket where the DC/OS advanced install params are. (We run
The cloudformation script supports multiple AWS regions and multiple AZs. To do this support we use cloudformation
We plan on improving the cloudformation scripts and packer script as follows:
You can get the full cloud formation script using this gist-Using CloudFormation, Packr, etc. for Immutable Infrastructure to build DC/OS and deploy it to Amazon Web Services.
Cloud News >