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.
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. Let’s get moving…
After clearing out all the security-related tweaks and configurations and having all of our DC/OS cluster nodes installed with the docker engine, 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 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?! Let’s find out…
Azure DevTest Labs solution is a nice one. During the past year or so, I have been working with it I noticed that the number of improvements added to DevTest is good. I wanted to bring your attention to a couple of new features in the platform – Multiple Instances Deployment and Shared IP.
A new Azure Marketplace feature has come to life called “Test Drives”. This will give you the opportunity to deploy and play with some applications on Azure for a limited amount of time (2hr) without the need to open an Azure subscription or give your credit card details.
In the last part for this series, we will tie up all the loose ends after a successful ASR Unplanned Failover.