Open Stack

From: Jay Lau <jay.lau.513 at gmail.com<mailto:jay.lau.513 at gmail.com>>
Reply-To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Wednesday, November 25, 2015 at 3:15 PM
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [magnum] Using docker container to run COE daemons

Hi,

It is becoming more and more popular to use docker container run some applications, so what about leveraging this in Magnum?


What I want to do is that we can put all COE daemons running in docker containers, because now Kubernetes, Mesos and Swarm support running in docker container and there are already some existing docker images/dockerfiles which we can leverage.

Jay,

It is my understanding that we have blueprints to address this topic:

https://blueprints.launchpad.net/magnum/+spec/run-kube-as-container
https://blueprints.launchpad.net/magnum/+spec/mesos-in-container

In addition to the COE daemons, the run-kube-as-a-container blueprint will address additional processes such as etcd and flannel. Swarm-agent/manager is already running as containers.


So what about update all COE templates to use docker container to run COE daemons and maintain some dockerfiles for different COEs in Magnum? This can reduce the maintain effort for COE as if there are new versions and we want to upgrade, just update the dockerfile is enough. Comments?

I would expect the templates to be updated as part of the blueprints above. As with the swarm template, I believe each coe service would correlate to a systemd unit file that specifies a docker pull/run of a specific image.


--
Thanks,

Jay Lau (Guangya Liu)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151129/1ee14271/attachment.html>