Continuing with our 3 Virtual Design Master finalists, here is the Q&A correspondence I had with Adam Post, our 2nd place winner.
So now that Virtual Design Master Season 5 is in the books, I’ve decided to do a quick Q&A with our 3 finalists and pick their brains around the experience, what’re their key takeaways and of course which mascot was their favorite this year.
Virtual Design Master is hands down, the coolest community project I participated in and not only that, I had the pleasure and privilege to act as one of the judges in this year’s season 5 panel.
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.