<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Oct 1, 2014, at 2:05 PM, Fox, Kevin M <<a href="mailto:Kevin.Fox@pnnl.gov">Kevin.Fox@pnnl.gov</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div ocsi="0" fpstyle="1" bgcolor="#FFFFFF" style="font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div style="direction: ltr; font-family: Tahoma; font-size: 10pt;">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?<br></div></div></blockquote><br><div>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.</div><div><br></div><div>[1] <a href="https://github.com/coreos/flannel">https://github.com/coreos/flannel</a></div><div>[2] <a href="https://github.com/vishvananda/wormhole">https://github.com/vishvananda/wormhole</a></div><div>[3] <a href="https://github.com/openshift/geard/blob/master/docs/linking.md">https://github.com/openshift/geard/blob/master/docs/linking.md</a></div><div><br></div><div>Vish</div><br><blockquote type="cite"><div ocsi="0" fpstyle="1" bgcolor="#FFFFFF" style="font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div style="direction: ltr; font-family: Tahoma; font-size: 10pt;">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?<br><br>Also, I ran across:<span class="Apple-converted-space"> </span><a href="http://jperrin.github.io/centos/2014/09/25/centos-docker-and-systemd/" target="_blank">http://jperrin.github.io/centos/2014/09/25/centos-docker-and-systemd/</a><span class="Apple-converted-space"> </span>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.<br><br>Thanks,<br>Kevin<br><div style="font-family: 'Times New Roman'; font-size: 16px;"><hr tabindex="-1"><div id="divRpF836376" style="direction: ltr;"><font size="2" face="Tahoma"><b>From:</b><span class="Apple-converted-space"> </span>Steven Dake [<a href="mailto:sdake@redhat.com">sdake@redhat.com</a>]<br><b>Sent:</b><span class="Apple-converted-space"> </span>Wednesday, October 01, 2014 8:04 AM<br><b>To:</b><span class="Apple-converted-space"> </span>OpenStack Development Mailing List (not for usage questions)<br><b>Subject:</b><span class="Apple-converted-space"> </span>Re: [openstack-dev] [kolla] Kolla Blueprints<br></font><br></div><div></div><div><div class="moz-cite-prefix">On 09/30/2014 09:55 AM, Chmouel Boudjnah wrote:<br></div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 30, 2014 at 6:41 PM, Steven Dake<span class="Apple-converted-space"> </span><span dir="ltr"><<a href="mailto:sdake@redhat.com" target="_blank">sdake@redhat.com</a>></span><span class="Apple-converted-space"> </span>wrote:<br><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><br>I've done a first round of prioritization. I think key things we need people to step up for are nova and rabbitmq containers.<br><br>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 :)</blockquote></div><br><br></div><div class="gmail_extra">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?<br><br></div><div class="gmail_extra">Chmouel<br></div><div class="gmail_extra"><br></div></div></blockquote>Chmouel,<br><br>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.<br><br>Regards,<br>-steve<br><br><br><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><br></div><div class="gmail_extra">[1] from<span class="Apple-converted-space"> </span><a href="https://github.com/jlabocki/superhappyfunshow/" target="_blank">https://github.com/jlabocki/superhappyfunshow/</a><br></div></div><br><fieldset class="mimeAttachmentHeader" target="_blank"></fieldset><br><pre>_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre></blockquote><br></div></div></div>_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></div></blockquote></div><br></body></html>