Calico’s Docker support has moved along a lot since this post.
To get started using Calico on Docker see: Getting Started on Docker
Or you can find the latest code and docs here: https://github.com/Metaswitch/calico-docker.
Original post below in full:
While for much of the team November has been dominated with thoughts of OpenStack (what with the submission of our nova and neutron blueprints and, of course, the Paris summit), this hasn’t been our sole focus. When we put together the Calico architecture we always expected that our networking model would work equally well for containers as for VMs, but the past few weeks have seen us put this to the test.
Based on the Calico components described in http://dev-project-calico.pantheonsite.io/technical/architecture/, we used Docker to set up several containers on a host:
We then created a script which acts as the “plug-in” in our architecture; this also runs in a container and is responsible for informing Felix and the ACL manager about any “guest” containers in the system. Putting all of these together on a couple of hosts, we were able to demonstrate the following:
All of this, along with instructions on how to reproduce this on your own system is available on github – https://github.com/Metaswitch/calico-docker.
No – this is not a fully-fledged demo by any means. It is a proof of concept, which means
That said, we’re excited about it as it validates one of our key architectural principles, which is that Calico provides a networking model which is platform agnostic.
While we’ve got some ideas on where to go next with Docker and containers, we’re not planning on doing any more in the short term with this prototype. As always, though, we’re very interested in any comments from the community and if someone wants to pick this up and integrate it with a Docker orchestrator, then you’ll have no complaints from us!
Get updates on blog posts, new releases and more!