This post is part of the “Mesosphere DC/OS, Azure, Docker, VMware & Everything Between” multiple blog post series. In the previous posts for this series, I looked at the following topics:
Mesosphere DCOS, Azure, Docker, VMware and everything between – Architecture and CI/CD Flow
Mesosphere DCOS, Azure, Docker, VMware and everything between – Security & Docker Engine Installation
Mesosphere DCOS, Azure, Docker, VMware & Everything Between – SSH Authorized Keys
Mesosphere DCOS, Azure, Docker, VMware & Everything Between – Deploying DC/OS with Azure Container Service
What a joy! We have a working DC/OS cluster on top of vSphere but now, it’s time to deploy another cluster using Azure Container Service (ACS). Fear not, it will be much quicker to get this baby up & running in Azure with no pain what so ever.
As you remember, in our scenario, we will have two DC/OS clusters. One will be used to run the “Production” Docker containers and the second one for “Integration & Testing”.
To deploy the cluster in Azure, we will use the magic of Azure Container Service which is a semi-managed containers orchestration platform. It supports all big-3 – DC/OS, Kubernetes and Docker Swarm. Unlike a manual on-premises deployment, ACS will do the heavy lifting for us. All you need to do is to state how many Master and Slave nodes you want and that’s it.
Another major difference between ACS deployment and an on-premises one is that in Azure, DC/OS must be deployed with both private and public slave nodes. If you remember, in our vSphere based deployment, we didn’t install any public agents.
Now, there are many blog posts, KBs and articles around how to use and deploy DC/OS using ACS so I’ll try to make it short but comprehensive as possible. IMHO, Microsoft ACS documentation is a very good place to start with.
Read more about all the details around DC/OS 1.9 deployment on top of VMware vSphere on my personal blog.