In the previous posts we’ve been using Azure Resource Manager (ARM) templates for deploying our nodes. Today we’ll be using the same method to deploy a Rancher Server.
Be aware that this is to be used for demo / labo / source-for-inspiration, and not for production usage! Azure has a strict policy that server that are not setup in a redundant manner will not benefit from Service Level Agreements. So you definitely need a “High Availability” setup for that.
Continue reading “Deploying Rancher Server via an Azure Resource Manager template”
A quick post in relation to the previous one ; Deploying Rancher Hosts via an Azure Manager Template
The template that was used at that time had a bug, where the “rancher overlay network” wasn’t working. Adding a public IP per host & introducing network security groups to publish the VPN ports (as mentioned before).
So if you’re using it, be sure to update to the latest version!
In Azure there are two “generations” (so to speak) ;
- “Service Management” : the backend of the “old” portal
- “Resource Manager” : the backend of the “new” portal
The technology underneath differs quite a bit…Though the “Azure Resource Manager” (or “ARM”) has the possibility to work with templates for deployments.
In the last blog post, I showed you how you can deploy nodes in Azure from your Rancher host. Today we’ll do it the other way around… We’ll deploy hosts using an “ARM”-template and will connect back to our Rancher host in one quick move!
Continue reading “Deploying Rancher Hosts via an Azure Resource Manager Template”
At this time, Rancher has a great support for a variety of Cloud Providers, except… Azure. Though it possible to provision hosts to Azure via your Rancher interface!
We’ll be doing this via the “Other” link…
Steps for today?
- Setup Docker Machine
- Validate integration between Docker Machine & Azure
- Use Rancher to provision a host in Azure
Continue reading “Rancher : Provisioning hosts on Azure”
Persistent storage is a though cookie for Docker… We’ve seen things like Flocker, Convoy, … Today, we’ll do a very rough (and experimental!) setup with an Azure storage account (via Azure File Share) as shared storage. How would such a design look?
Continue reading “Azure & Docker : Shared storage anyone?”
Today we’ll try to understand a bit more about the Rancher cross-host networking capabilities.
Rancher supports cross-host container communication by implementing a simple and secure overlay network using IPsec tunneling. To leverage this capability, a container launched through Rancher must select “Managed” for its network mode or if launched through Docker, provide an extra label “–label io.rancher.container.network=true”. Most of Rancher’s network features, such as load balancer or DNS service, require the container to be in the managed network.
Under Rancher’s network, a container will be assigned both a Docker bridge IP (172.17.0.0/16) and a Rancher managed IP (10.42.0.0/16) on the default docker0 bridge. Containers within the same environment are then routable and reachable via the managed network.
Note:The Rancher managed IP address will be not present in Docker meta-data and as such will not appear in the result of a Docker “inspect.” This sometimes causes incompatibilities with certain tools that require a Docker bridge IP. We are already working with the Docker community to make sure a future version of Docker can handle overlay networks more cleanly.
Source : http://docs.rancher.com/rancher/concepts/#networking
So in short… You can create a virtual network spanned accross all hosts using Rancher. At the time of writing, this is still based upon an IPsec VPN implementation underneath, where RancherLabs is looking to implement the “new” overlay networking of the native Docker. Be aware that Weave is also pretty known, and used, within the community. Though at this point I want to keep it as simple as possible…
High Level Setup
Anyhow, let’s look at our labo for the day…
Continue reading “Azure & Cross-Host Container Networking using Rancher”
The mailinglist of Luper’s learning featured the following article ;
“Introducing a simplified configuration experience for SQL Server in Azure Virtual Machines”
To me, this is a very cool and shows the innovation that’s going on in the whole Azure landscape. Underneath, any azure enthousiast, will see that this is powered by the ARM JSON templates. Though from a business perspective, the right questions are posed!
- Who should be able to access it and how?
- What are the storage capacity & performance expectations?
- What about (technical) maintenance aspects like backup & patching?
How to find the machine?
Go to the marketplace in the Azure portal and find the following SQL server ;
What will it bring to the table?
Continue reading “Azure : Enterprise Grade SQL Provisioning”