We have two working DC/OS clusters, one on Azure and another on vSphere – Great progress so far! Now, it’s time deploy Azure Container Registry (ACR) which will be used as a private catalog for our Docker images.

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.

Now that we have the Docker engine up and running and all of our network & security related configurations in place, it’s time to get the DC/OS cluster rolling on top of VMware vSphere. This is the first major milestone in our entire platform setup.

After clearing out all the security-related tweaks, configurations, and having all of our DC/OS cluster nodes installed with the Docker engine. We will dive into part 3 for this series, when it’s time to create the SSH authorized keys file and establish the trust relationships between the bootstrap node to all other nodes in the cluster.

In part 2 of this series, we will start to dive into DC/OS 1.9 installation on top of vSphere. Mesosphere offers few ways to deploy a fully working cluster and since I wanted to see how everything is really connected, I have chosen the advanced installation method. We will start with some Linux related adjustments and the Docker engine deployment.

These days, I try to be involved in any Containers, DevOps, Automation, etc. related discussion. Part of my role is to consult my customers around how to architect their containers platform and orchestration tools in Azure. But what happens when you have a chance to do something cool like architecting a solution which involves Mesosphere DC/OS, Azure Container Service, Azure Container Registry, Docker, and VMware vSphere?!