On last week’s Buffer Overflow we were talking about this very strange blog post from Microsoft about a “Modern OS” and what it should include. It’s obvious that Microsoft has something big brewing over in Redmond. In the build-up to \build, rumors were flying fast and free that Microsoft was going to unveil their new Lite OS and provide a roadmap for development. That did not happen, and the blog post from Computex seems to indicate that while Microsoft is definitely developing something that is not Windows, they aren’t quite ready to share with the world what that “Modern OS” actually is. The more I think about it, I believe that Microsoft might be poised to come barreling back into the mobile market from a totally unexpected direction.
Recently at two separate client meetings, I heard two people say that they hate Microsoft. As you may have guessed, both people were happily using some type of Apple device, and were complaining about having to use some form of Microsoft technology. In one case it was Office 365, and the other was Active Directory. And listen everyone, I get it. Sometimes I hate Microsoft too. Except not really.
Sigh. There’s an old adage that I always come back to. Just because you can do something, doesn’t mean that you should. In this case I am thinking about the recent announcement by Microsoft that Azure would be supporting bare metal deployments of VMware on Azure hardware. In case you’ve been living under a rock, AWS went GA with a very similar offering back in late August. Of course there are some specifics that differ, but the overall theme is the same. You can run your VMware workloads in their public cloud on bare metal, but still have close proximity to their respective public cloud services. Alas, just because it’s on Azure now, doesn’t make the idea any better, and I stand by my previous post.
In a previous post I covered how to add a Linux image to Azure Stack. In this post I am going to detail a simple (if slow) way of adding a Server 2012 R2 image to Azure Stack as well. With Azure Stack TP3 (original and extra-crispy) there are no default VM Images included in the install. You are prompted to download a Windows Server 2016 ISO as part of the Azure Stack POC download, and there is a script in the AzureStack.ComputeAdmin module called New-Server2016Image that will take that ISO and turn it into a Core or Datacenter image. But what if you wanted that good ole Server 2012 R2 image?
First off, let me quell your anticipation. I got it working! It was not as straightforward as I might like, but it will work. If you haven’t already read post three, I would recommend doing so. The long and short of it is that the build task Azure Resource Group deployment in TFS doesn’t understand the Azure Stack environment. It doesn’t know how to talk to it, so any build task is going to fail. One of the engineers at Microsoft suggested I use a PowerShell task to deploy instead, which I did. That was not as simple as I would have liked, but here is what I had to do. Continue reading “CICD Pipeline with Azure Stack – Part 4”