Open Stack

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 <ewindisch at docker.com<mailto:ewindisch at docker.com>>
Date: Tuesday, May 20, 2014 3:45 PM
To: andrew plunk <andrew.plunk at rackspace.com<mailto:andrew.plunk at rackspace.com>>
Cc: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>, "alex.gaynor at gmail.com<mailto:alex.gaynor at gmail.com>" <alex.gaynor at gmail.com<mailto:alex.gaynor at gmail.com>>
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140520/a5ee2b38/attachment.html>