<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Feb 26, 2015 at 9:12 AM, Sean M. Collins <span dir="ltr"><<a href="mailto:sean@coreitpro.com" target="_blank">sean@coreitpro.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I have proposed a recent patch, that when using Neutron as the<br>
networking component in DevStack, the PUBLIC_INTERFACE that has been set<br>
should automatically be added to the OVS_PHYSICAL_BRIDGE.<br>
<br>
<a href="https://review.openstack.org/#/c/158424/" target="_blank">https://review.openstack.org/#/c/158424/</a><br>
<br></blockquote><div>Thanks for taking this work on Sean!<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
There are a couple motivations for this patch. The first is that in my<br>
Vagrant project, I've been using chef[0] to attach the public interface<br>
to the OVS bridge, so that when a floating IP is NAT'd traffic flows<br>
from the interface attached to the router where the floating IP range is<br>
advertised, into the L3 agent.<br>
<br>
This is basically the same step documented for setting up a production<br>
Neutron install[1]. The fact that we are not doing this for DevStack<br>
installations is an oversight that should be corrected.<br>
<br>
The second motivation for this patch is to help transition DevStack<br>
users from Nova-Networking. Recently, we tried to move Neutron to being<br>
the default, but the lack of code to configure DevStack on machines with<br>
a single network interface caused a lot of issues and had to be<br>
reverted.<br>
<br>
In cases where DevStack is being run on a developer machine, where only<br>
one physical interface is present, DevStack will remove the IP address<br>
that has been assigned to the machine and adds it to the<br>
OVS_PHSYICAL_BRIDGE, so that the machine as well as the OpenStack APIs<br>
are reachable, while also allowing the usage of floating IPs.<br>
</blockquote><div>This all sounds good to me. I'll review the patch in more detail and provide specific comments there.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
An example local.conf shows how this is configured. On this machine, we<br>
have a router that advertises the <a href="http://192.168.27.0/24" target="_blank">192.168.27.0/24</a> prefix. The DevStack<br>
machine will be assigned 192.168.27.2 from DHCP, and the remaining IPs<br>
in the /24 will be used for floating IP addresses.<br>
<br>
HOST_IP=192.168.27.2<br>
FLAT_INTERFACE=eth0<br>
PUBLIC_INTERFACE=eth0<br>
FIXED_RANGE=<a href="http://10.0.0.0/24" target="_blank">10.0.0.0/24</a><br>
FLOATING_RANGE=<a href="http://192.168.27.0/24" target="_blank">192.168.27.0/24</a><br>
PUBLIC_NETWORK_GATEWAY=192.168.27.1<br>
<br>
disable_service n-net<br>
enable_service q-svc<br>
enable_service q-agt<br>
enable_service q-dhcp<br>
enable_service q-meta<br>
enable_service q-l3<br>
<br>
Q_USE_SECGROUP=True<br>
ENABLE_TENANT_VLANS=True<br>
TENANT_VLAN_RANGE=3001:4000<br>
OVS_PHYSICAL_BRIDGE=br-ex<br>
Q_L3_ENABLED=True<br>
Q_FLOATING_ALLOCATION_POOL=start=192.168.27.3,end=192.168.27.254<br>
<br>
I'd be interested in feedback from everyone about my thought process,<br>
code, and if I'm on the right track.<br>
<br>
[0]: <a href="https://github.com/sc68cal/chef-devstack/blob/master/recipes/default.rb#L50" target="_blank">https://github.com/sc68cal/chef-devstack/blob/master/recipes/default.rb#L50</a><br>
[1]: <a href="http://docs.openstack.org/admin-guide-cloud/content/install_neutron-l3.html" target="_blank">http://docs.openstack.org/admin-guide-cloud/content/install_neutron-l3.html</a><br>
[2]: <a href="https://review.openstack.org/#/c/153208/" target="_blank">https://review.openstack.org/#/c/153208/</a><br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Sean M. Collins<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></span></blockquote></div><br></div></div>