On Thu, Mar 13, 2014 at 10:28:02AM -0700, Steven Dake wrote: > With the docker plugin, no heat-cfntools or other python > dependencies are required. One way to think about how the docker > plugin works is as a management tool for building composite > applications out of separate containers. Heat is the management Awesome. Those are the magic words I'm looking for. > Not an issue for Heat docker-plugin based containers Also those. :) > I would like to point out that the docker driver is in the /contrib > directory of the heat repository and is not generally supported by > upstream. The heat community doesn't have the same policy around [...] > The docker plugin is in the fedora repositories, but not installed > by default in the packaging. I'll have someone take a look at the > plugin to see if it even makes sense to enable it by default, since > I doubt any of the heat-core personally tested it. Okay, thanks. I'll look and talk to people too. The other related issue is whether we want to expose the docker remote API over http; I will talk to some of the security people about that. -- Matthew Miller -- Fedora Project -- <mattdm@xxxxxxxxxxxxxxxxx> _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
