It is been a bit more than two years now at Microsoft. After acting as an Azure Cloud Solutions Architect it is now time to move on in my career, and boy, so many changes at once.
There are some announcements that make you feel like a kid again! about two hours ago, Microsoft announced the “Transforming your VMware environment with Microsoft Azure” program. This is our way to show VMware customers that there is another way, there are more options and that Azure is that cool!
In my continuing journey to become more of an “Automation, APIs and DevOps” kinda architect, I try to find or come up with cool “pet projects” for myself. This time, I did a nice an easy Terraform VMware vSphere Provider and Slack integration using webhooks.
It’s time to become a member of the DevOps team and deploy our application to production. If you think we used Azure Container Registry only to deploy containers on top of DC/OS in Azure, well, think again.
Now, when Azure Container Registry contains our repository, new containers can be deployed out of it. Let’s switch role and become members of the Integration team as our role now is to deploy the application at scale on the DC/OS cluster deployed on Azure.
Now that we have all our puzzle pieces in place the real fun begins as we start to move containers around. From the developer laptop through the integration team tests and finally to a running container in production. Let’s get it on with playing the developer role…
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.
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.