On Oct 1, 2014, at 2:05 PM, Fox, Kevin M <kevin....@pnnl.gov> wrote:
> Has anyone figured out a way of having a floating ip like feature with docker > so that you can have rabbitmq, mysql, or ceph mon's at fixed ip's and be able > to migrate them around from physical host to physical host and still have > them at fixed locations that you can easily put in static config files? There are[1] many[2] ways[3] to do this, but in general I don’t think they pass the “too much magic” sniff test. I think the standard docker approach of passing in the necessary ips via environment variables is probably the most user friendly option. Containers are light-weight enough to restart if the data changes. [1] https://github.com/coreos/flannel [2] https://github.com/vishvananda/wormhole [3] https://github.com/openshift/geard/blob/master/docs/linking.md Vish > Maybe iptables rules? Maybe adding another bridge? Maybe just disabling the > docker network stack all together and binding the service to a fixed, static > address on the host? > > Also, I ran across: > http://jperrin.github.io/centos/2014/09/25/centos-docker-and-systemd/ and it > does seem to work. I was able to get openssh-server and keystone to work in > the same container without needing to write custom start/stop scripts. This > kind of setup would make a nova compute container much, much easier. > > Thanks, > Kevin > From: Steven Dake [sd...@redhat.com] > Sent: Wednesday, October 01, 2014 8:04 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [kolla] Kolla Blueprints > > On 09/30/2014 09:55 AM, Chmouel Boudjnah wrote: >> >> On Tue, Sep 30, 2014 at 6:41 PM, Steven Dake <sd...@redhat.com> wrote: >> >> I've done a first round of prioritization. I think key things we need >> people to step up for are nova and rabbitmq containers. >> >> For the developers, please take a moment to pick a specific blueprint to >> work on. If your already working on something, this hsould help to prevent >> duplicate work :) >> >> >> As I understand in the current implementations[1] the containers are >> configured with a mix of shell scripts using crudini and other shell >> command. Is it the way to configure the containers? and is a deployment tool >> like Ansible (or others) is something that is planned to be used in the >> future? >> >> Chmouel >> > Chmouel, > > I am not really sure what the best solution to configure the containers. It > is clear to me the current shell scripts are fragile in nature and do not > handle container restart properly. The idea of using Puppet or Ansible as a > CM tool has been discussed with no resolution. At the moment, I'm satisified > with a somewhat hacky solution if we can get the containers operational. > > Regards, > -steve > > > >> >> [1] from https://github.com/jlabocki/superhappyfunshow/ >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
