How to manually size your Azure Virtual Machine Scale Sets (vmss)?

Whilst exploring the Azure container service preview. One of the key components here is the “virtual machine scale set“. But as you can see, at the moment there isn’t much to configure via the portal…

2016-02-22 22_10_21-Properties - Microsoft Azure

So how can you (manually) update your virtual machine scale set? Use the following arm template :

2016-02-22 22_11_11-Parameters - Microsoft Azure

Here you can enter the name of your virtual machine scale set and the new scale set capacity (or size). Execute the deployment and wait for a bit…

2016-02-22 22_11_41-Microsoft.Template - Microsoft Azure

Even before the deployment finishes, you’ll see that the capacity has been changed.

2016-02-22 22_11_59-Properties - Microsoft Azure

Azure Resource Manager : Deployment variants within one script

Today a quick post to show you that you can setup a deployment with several variants within the current template functions.
So for this post we’ll be combining the deploment for the rancher <a href="”>server & nodes into one script.

2016-02-19 10_53_14-Parameters - Microsoft Azure

Continue reading “Azure Resource Manager : Deployment variants within one script”

Docker : Storage Patterns for Persistence


One of the sensitive areas when it comes to docker is persistent storage… A typical service upgrade involves shutting down the “V1” container and pulling/starting the “V2” container. If no actions are taken, then all your data will be wiped… This is not really the scenario we want off course!


So today we’ll go over several variants when it comes down to data persistence ;

  • Default : No Data Persistence
  • Data Volumes : Container Persistence
  • Data Only Container : Container Persistence
  • Host Mapped Volume : Container Persistence
  • Host Mapped Volume, backed by Shared Storage : Host Persistence
  • Convoy Volume Plugin : Host Persistence

What do I mean with the different (self invented) persistence level ;

  • Container : An upgrade of the container will not scratch the data
  • Host : A host failure will not result in data loss

So let’s go through the different variants, shall we?

Continue reading “Docker : Storage Patterns for Persistence”

Rancher End-to-End Service Example using an Owncloud-plus-mysql Deployment


So what will we be doing today? We are going to leverage the power of the combination between docker containers & the rancher eco system. As a demonstration, we’ll be publishing “Owncloud” with a “mysql” backend. As we tend to like it a bit more secure, we’ll introduce a loadbalancer service as SSL termination. This as we want to keep our “Owncloud” as “vanilla” as possible. We’ll be pointing that service towards the outside world and will make it accessible via the “external dns”.


What can we optimize further about the design? (but is out-of-scope for today)

  • Add sidekick containers for backup purposes
  • Add data volume containers
  • Introduce scalable worker containers (“Owncloud”)
  • Introduce convoy for our data containers

Continue reading “Rancher End-to-End Service Example using an Owncloud-plus-mysql Deployment”