No Problem. As the Docker resource in Heat currently works, it will require Docker running on a customer's vm to listen over a network socket. With software config you could allow Docker to listen on the instance's local unix socket, and communicate with Docker via Heat's in instance software config agents.
-Andrew Plunk From: Eric Windisch <[email protected]<mailto:[email protected]>> Date: Tuesday, May 20, 2014 3:45 PM To: andrew plunk <[email protected]<mailto:[email protected]>> Cc: "OpenStack Development Mailing List (not for usage questions)" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [Heat] [Docker] Resource 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
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
