If you are planning to add Linux Images to your Azure Stack deployment, first I would recommend reading through the documentation on the Azure Stack pages for Adding a VM Image and Using Custom Linux Images. From there you can get the base images and the process for adding the images to Azure Stack. What they don’t include is the Azure Cloud information for the various images, and if you would like to be able to use a JSON template against both Azure and Azure Stack without changing the image information, then you will want the publisher, offer, sku, and version to match. In this post I will walk through the basics of adding one Linux image, how to get the necessary information from Azure Cloud, and the current information for the images you may want to run.
You’ve got brains in your head…
I think it’s fair to say that most of us have followed an interesting path to end up in IT. As you continue to progress, you may start considering what the next steps are in that path. Here are some of the questions to consider. FYI – this post was inspired by an excellent post that I absolutely cannot find and really wished I had bookmarked.
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”
Earlier this week Amazon Web Service’s Simple Storage Service, better known as S3, was experiencing higher than normal error rates in the us-east-1 region, i.e. S3 was down. To put that into perspective, it also means that several high-profile websites and applications were experiencing major issues. As you may know, S3 has a 99.9% SLA uptime, and it’s been down for a couple hours now. I’m no math genius, but that’s more than the 44 minutes a 99.9% uptime per month requires. Continue reading “Everything is Broken…Still”