From template code to deployment… If we really want to control this, then we’ll be pushing these templates through a CI/CD (continuous integration / continuous deployment) pipeline. What does that mean? We are going to put our template in a source code repository (like Github). Everytime we update the code, we’ll going to kick in a “build”. During this build we’ll be packaging it (read : create a zip file of it) and it is also strongly advised to do testing here too. Next up, if all goes well, we’ll be using that package to deploy to all our environments. And in the end, we want to be able to have a nice view on this too…
Why do it like this? Quality! We all make mistakes. We want to detect them early and not repeat them. And every change, we want to put it through the exact same process… time and time again!
Starting off, I’m assuming you already have VSTS (Visual Studio Team Services) in place. If not, register for it! It’s free up till 5 users. And let’s be honest, at about 5€ per user / month & 8€ per build agent per month, … it’s still a steal! 😉
Continue reading “Azure : Pushing Azure Resource Manager Templates through a CI/CD (release) pipeline with Visual Studio Team Services”
In the past I’ve noticed a lot of people are afraid of “Azure Resource Manager Templates“. I can imagine that a bulk of JSON code isn’t always that user friendly… So today we’ll take a look at another IaC (Infrastructure-as-Code) approach you might like. We’re going to do a small demo where we’ll be using “Terraform” to deploy a network on Azure. So how to get started?
- We’ll be creating a kind of service user in Azure which Terraform will use to log in.
- We’ll be authoring a small configuration file that will serve as the input for our network
- We’ll be applying that configuration file.
Seem simple enough? Let’s get started!
Continue reading “An alternative way to landscaping in Azure… Terraform!”
Today I’m going to show you how you can leverage the combination of Visual Studio Team Services & Rancher to kickstart your continuous deployment of your docker containers. So every time we update our containers, we want a smooth upgrade process on our container setup. What do you think? Let’s see what this can look like?
The scenario of today will have the following flow ;
- We’ll use a git(hub) repository to store our docker-compose & rancher-compose file that powers our solution.
- Next up, we’ll be using VSTS as the orchestrator for your CI/CD-pipeline.
- Rancher is our preferred container workflow / management tool, and we’ll be using the “rancher-compose” on our VSTS build agent.
Continue reading “Using Visual Studio Team Services & Rancher for continuous deployment for your docker containers”
A few weeks ago there was an announcement that the Azure Container Registry has went into public preview. That is great to hear! So let’s test drive it today… We’re going to set up the registry in Azure. Push a container image into it. And pull/run it via rancher towards our cluster. (To do this, I basically followed a lot of the following guide.
Setting up the Azure Container Registry (ACR)
So start by searching for the “Container Registry” in the marketplace ;
Continue reading “Testdriving the Azure Container Registry Service with Rancher”
When talking to customers about DevOps, I often get the two following questions ;
- Does this mean I have to get rid of ; ITIL / COBIT / … ?
- Do I have to start moving people around and creating new units?
The quick answer is ; No.
A typical parabel in any project methodology is ;
How do you eat an elephant? Take snack sized bites and work your way through it.
And the same goes for DevOps!
Continue reading “DevOps : What’s the impact on my ITIL/COBIT/… based shop?”
So you’ve already deployed Windows based systems in Azure. Very good! You’ve probably joined those systems into a domain, as you’ve always done this by going through the GUI. Did you know you can join a machine without logging into the machine? No? Then today’s post will be very interesting for you!
If you knew this was possible, then I’ll show you that there are various methods of doing so. And that each approach will have clear advantages and even disadvantages. So let’s get ready to domainjoin those systems!
Continue reading “Domain Join : ARM Extension versus Azure Automation DSC”
Given my affinity towards containers & azure, it will not come as a surprise when I say I published a small container from which you can launch AzureRM commands!
- Docker Hub (build) : https://hub.docker.com/r/kvaes/docker-powershell-azure/
- GitHub (source) : https://github.com/kvaes/docker-powershell-azure
First of all, we’ll launch the container ;
docker run -ti kvaes/docker-powershell-azure
Next up you do the device login ;
And check out which commands are available…
As you notice, the current preview release is quite limited in available commands. Expect more to be added over time off course!
- Powershell on Linux works
- The AzureRM module is in preview, and limited in commands
- It all works inside a container too! 😀