An init system for cloud-native distributed applications that automates the process of service discovery, configuration, and lifecycle management inside the container, so you can focus on your apps.
Orchestration is the automation of the operations of an application. Most application require operational tasks like connecting them to related components (WordPress needs to know where it's MySQL and Memcached servers are, for example), and some applications require special attention as they start up or shut down to be sure they bootstrap correctly or persist their data. We can do all that by hand, but modern applications automate those tasks in code. That's called "orchestration."
To make this work, every application needs to do the following (at a minimum):
- Register itself in a service catalog (like Consul or Etcd) for use by other apps
- Look to the service catalog to find the apps it depends on
- Configure itself when the container starts, and reconfigure itself over time
We can write our new applications to do that, but existing apps will need some help. We can wrap each application in a shell script that registers itself with the discovery service easily enough, but watching for changes to that service and ensuring that health checks are being made is more complicated. We can put a second process in the container, but as soon as we do that we need an init system running inside the container as well.
ContainerPilot is an init system designed to live inside the container. It acts as a process supervisor, reaps zombies, run health checks, registers the app in the service catalog, watches the service catalog for changes, and runs your user-specified code at events in the lifecycle of the container to make it all work right. ContainerPilot uses Consul to coordinate global state among the application containers.
Check out our "Hello, World" application on GitHub. Assuming you have Docker and Docker Compose available, it's as easy as:
git clone git@github.com:autopilotpattern/hello-world.git
cd hello-world
docker-compose up -d
open http://localhost
This application blueprint demonstrates using ContainerPilot to update Nginx upstream configuration at runtime. Try scaling up via docker-compose scale hello=2 world=3 to see the Nginx configuration updated.
You can also download the latest release of ContainerPilot from GitHub.
Documentation for ContainerPilot and where it fits with the rest of the Triton ecosystem can be found at www.joyent.com/containerpilot. The index below links to the documentation in this repo for convenience.
- What is a job?
- What is an event?
- What is a watch?
- How do events trigger jobs?
- How can jobs be ordered?
Design: the Why of ContainerPilot
- Why active service discovery?
- Why isn't there a "post-start" or "started" event?
- Why Consul and not etcd or Zookeeper?
- Why are jobs not the same as services?
- Why don't watches or metrics have an exec field?
- Why use something other than ContainerPilot?
Configuration
- Installation
- Configuration file
- Consul
- Jobs
- Watches
- Telemetry
- Control plane
- Logging
- Example configurations
You might also read our guide building self-operating applications with ContainerPilot and look at the examples below.
We've published a number of example applications demonstrating how ContainerPilot works.
- Applications on autopilot: a guide to how to build self-operating applications with ContainerPilot
- MySQL (Percona Server) with auto scaling and fail-over
- Autopilot Pattern WordPress
- ELK stack
- Node.js + Nginx + Couchbase
- CloudFlare DNS and CDN with dynamic origins
- Consul, running as an HA raft
- Couchbase
- Mesos on Joyent Triton
- Nginx with dynamic upstreams