Open Stack

>
>
>  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
>

First, thank you for looking at this.

Docker already listens on a unix socket. I'm not as familiar with Heat's
'software config' as I should be, although I attended a couple sessions on
it last week. I'm not sure how this solves the problem? Is the plan to have
the software-config-agent communicate over the network to/from Heat, and to
the instance's local unix socket?

-- 
Regards,
Eric Windisch
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140520/811dddc6/attachment.html>