Documentation and examples for how to leverage various linux technologies with Microsoft Azure.
I write tutorials with a bit of automation code about things I didn't see documented elsewhere, or where I want to add context and details to existing docs and blog posts. I also list a set of links to relevant docs or blog posts that I found useful.
- Installing a CoreOS cluster on Azure Docker orchestration with Fleet. Deploying a Java 8 application using Spring Boot and MongoDB on a CoreOS cluster on Azure, using Docker and Fleet. Deploying @NetflixOSS containers.
- Installing Deis on a CoreOS cluster on Azure Docker orchestration with Deis. Fun and games with DNS settings, then deploy a ruby app with git, and a Docker image for a Java 8 app.
- Azure CoreOS cluster deployment tool Python script to deploy a CoreOS cluster in one shot.
- Installing Kubernetes on a CoreOS cluster on Azure (Work in Progress), Docker orchestration with Kubernetes. Cf links below for 2 approaches to networking that need testing on Azure: Weave and Flannel.
The main issue installing Kubernetes on Azure is networking: Kubernetes needs to assign 1 IP address per pod, which works fine on Google Cloud Platform, where advanced routing allows you to configure your VMs so that each get assigned a /24 address space. On Azure today, you need to leverage some kind of overlay network to accomplish that. There are different approaches in how to do this:
- Kubernetes, Getting started on Microsoft Azure uses Ubuntu images, OpenVPN for networking.
- Weave for Kubernetes on CoreOS seems promising, and should be a good approach for Azure
- Deploying Kubernetes on CoreOS with Fleet and Flannel the other main approach
Snappy Ubuntu Core is a minimal server image of Ubuntu, coupled with a transactional OS update mechanism, similar to CoreOS, and an application model inspired by mobile app stores called snappy. It was announced 12/9/2014, with initial support for Azure first.
I assume you already know Docker basics: there are plenty of resources and tutorials out there about it. If you don't, get started with @kartar's excellent book The Docker book - Containerization is the new virtualization, then read the official docs.
Here are resources to understand how Docker works internally, where it is going, and what kind of innovation is happening in different part of the ecosystem as it matures: orchestration, networking, storage, management and monitoring.
- Azure Docs Using the Docker VM Extension from Azure Cross-Platform Interface (xplat-cli)
- Creating containers @crosbymichael's series on the internals of what containers are is a very good read, to understand how Docker works.
- @jpetazzo's articles and decks also go pretty deep.
- Using Fig and Flocker to build, test, deploy and migrate multi-server Dockerized apps One area of innovation for Docker is storage. One issue with Docker is that stateless containers are easy to move to a different host (typically done by an orchestration engine), but stateful containers for database services are tied to a host. Flocker is an interesting answer to this issue, allowing you to snapshot and migrate your data volumes using a port of zfs for Linux. Flocker provides multi host container orchestration, supporting part of the fig format (which will be the format supported in Docker groups), but the most differentiating aspect they provide is the zfs based volume migration capability.
- Life and Docker networking Networking is another big area of innovation in the Docker ecosystem. Thoughtful essay by @monadic about the various approaches to Docker networking these days, and the need for a plugin system for Docker.
- Docker groups The Docker stack composition proposal, for Docker native orchestration. There's a release implementing it that you can try. This is the replacement for Fig.
- Docker clustering with swarm
- Docker plugins proposal
- Docker hosts management with machine there is an Azure driver for it