Experimenting with Docker, Registrator, and Consul
Over the last few days, I’ve been experimenting with Docker, Registrator, and Consul in an effort to explore some of the challenges involved in building a robust containerized infrastructure. While I haven’t finished fully exploring the idea (and documenting what I’ve learned), I did discover one interesting—and unexpected—interaction.
Here’s a quick overview of my testing environment:
- I used two OpenStack Heat templates to spin up two clusters of 5 instances each.
- The first cluster is a set of CoreOS Linux instances, customized via cloud-init to not run etcd. These instances are attached to a VMware NSX-powered logical network using IP addresses from the 10.1.1.0/24 subnet.
- On each CoreOS Linux instance, I have Registrator running as a Docker container and listening to the Docker socket (thus listening to Docker events).
- The second cluster is a set of Ubuntu 14.04 instances running Consul. These instances are connected to an NSX-powered logical network using IP addresses from the 10.1.2.0/24 subnet.
- The two logical networks are connected by a logical router and thus have full connectivity.
Registrator, if you’re not already familiar with it, is a service registry tool that listens to the Docker Continue reading