Hello All, The purpose of this email is to document a few discussions from the summit, and to facilitate communication between parties at Docker and the Heat community.
The way the Docker resource is currently implemented requires the remote Docker api to be enabled on the compute instances that Heat wants to create containers on. The way Docker suggests securing the remote api is by using tls client certificates signed by a trusted CA used to start up the docker api (http://docs.docker.io/examples/https/). This presents a problem for Heat because certificates would have to be added to Heat for each Docker resource (or per stack) in order to have secure communication, which creates a scalability problem, and requires Heat to store customer secrets. The solution I propose to this problem is to integrate docker with software config, which would allow the Docker api running on a compute instance to listen on an unix socket while still being able to communicate with the Heat engine. I have created a blueprint to capture this proposal: https://blueprints.launchpad.net/heat/+spec/software-config-docker Any input on this proposal is welcome. Thanks everyone! -Andrew Plunk
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
