<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Michael,<div class=""><br class=""></div><div class="">If you are creating an external network it will more than likely not be VXLAN/GRE but would be of type VLAN or FLAT. In the ML2 configuration file there is a mapping under [linux_bridge] labeled ‘physical_interface_mappings’. In an OSAD deployment, it may look like this:</div><div class=""><br class=""></div><div class=""><div class=""><font face="Courier" class="">[linux_bridge]</font></div><div class=""><font face="Courier" class="">physical_interface_mappings = vlan:eth11</font></div><div class=""><br class=""></div><div class="">The provider label is ‘vlan’ and the physical interface (in the container, anyway) is eth11. To create an external provider network you would need to use the following:</div><div class=""><br class=""></div><div class=""><font face="Courier" class="">neutron net-create EXTERNAL_NET --provider:network_type=<vlan/flat> --provider:physical_network=<label> --provider:segmentation_id=<vlan id> --router:external=true</font></div><div class=""><br class=""></div><div class="">In your case, it looks like a flat network would work, so you could try:</div><div class=""><br class=""></div><div class=""><div class=""><font face="Courier" class="">neutron net-create EXTERNAL_NET --provider:network_type=flat --provider:physical_network=vlan --router:external=true</font></div></div><div class=""><br class=""></div><div class="">Neutron should automatically put eth11 in the bridge. If it were a vlan network, Neutron would put eth11.xxx in the bridge instead.</div><div class=""><br class=""></div><div apple-content-edited="true" class="">
<div class=""><div class="">James Denton</div><div class="">Network Architect</div><div class="">Rackspace Private Cloud</div><div class=""><a href="mailto:james.denton@rackspace.com" class="">james.denton@rackspace.com</a></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Sep 2, 2015, at 12:39 AM, Michael Gale <<a href="mailto:gale.michael@gmail.com" class="">gale.michael@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div dir="ltr" class="">Hello,<div class=""><br class=""></div><div class=""> I am running the Kilo release using os-ansible-deployment and have a functioning OpenStack installation using VXLANs however I am running into an issue adding an external network.</div><div class=""><br class=""></div><div class="">From the Horizon interface I can create private tenant networks without an issue and I have created an external network:</div><div class="">- Subnet <a href="http://1.2.10.0/24" class="">1.2.10.0/24</a></div><div class="">- GW 1.2.10.1</div><div class="">- VXLAN ID: 999</div><div class=""><br class=""></div><div class="">Inside OpenStack the instances can access each other and the public IP's that exist on the external subnet however they can not access the external subnet gateway which exist outside of OpenStack.</div><div class=""><br class=""></div><div class="">On the neutron agent node where I have the neutron L3 agent:</div><div class="">- I can see my external network interface (eth11) and it is working</div><div class="">- I can see a bridge device that has a VXLAN ID interface attached that matches my external network plus 2 tap devices</div><div class=""><br class=""></div><div class="">If I check the network namespace I find a router exists with ports, routers, etc and matches the Horizon Network Topology graph.</div><div class=""><br class=""></div><div class="">Now from my understanding I need to update /etc/neutron/l3_agent.ini and set my external interface and that neutron will automatically add that interface to the router when it is marked as external:</div><div class=""><div class="">external_network_bridge = eth11 </div></div><div class=""><br class=""></div><div class="">However that did not work, I was able to make it work by adding eth11 to the bridge interface that got created:</div><div class=""><br class=""></div><div class=""><b class="">Neutron Node - Before change</b></div><div class="">--snip--</div><div class=""><div class="">bridge name bridge id STP enabled interfaces</div><div class="">brq321e79ee-60 8000.629228307545 no tap69cab170-04</div><div class=""> vxlan-77</div><div class="">brqd8c6a159-03 8000.16ed469b44d8 no tap83dc2c50-ef</div><div class=""> vxlan-999</div></div><div class=""><br class=""></div><div class="">--snip--</div><div class=""><br class=""></div><div class=""><b class="">Neutron Node - After change</b></div><div class="">--snip--</div><div class=""><div class="">bridge name bridge id STP enabled interfaces</div><div class="">brq321e79ee-60 8000.9225a6292c5c no tap277296ef-97</div><div class=""> tape55e2167-98</div><div class=""> vxlan-77</div><div class="">brqd8c6a159-03 8000.00163ee12e11 no eth11</div><div class=""> tap124723f9-2e</div><div class=""> tap5f9dc7ba-d6</div><div class=""> vxlan-999</div></div><div class=""><br class=""></div><div class="">--snip--</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Obviously I am missing something, any help is appreciated.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Thanks</div><div class="">Michael</div><div class="">
</div></div>
_______________________________________________<br class="">Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br class="">Post to : <a href="mailto:openstack@lists.openstack.org" class="">openstack@lists.openstack.org</a><br class="">Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br class=""></div></blockquote></div><br class=""></div></body></html>