This bug has been solved in trunk[1] (icehouse) and backported to stable/havana[2]: When external_network_bridge and gateway_external_network_id are empty, l3-agent uses provider attributes to deploy the external network
[1] https://review.openstack.org/59359 [2] https://review.openstack.org/68601 ** Changed in: neutron Status: Confirmed => Fix Released ** Tags removed: havana-backport-potential l3-ipam-dhcp ** Tags added: in-stable-havana ** Tags added: l3-ipam-dhcp -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1056437 Title: L3 agent should support provider external networks Status in OpenStack Neutron (virtual network service): Fix Released Bug description: The l3-agent requires an "external" quantum network, and creates ports on that network, but does not actually use the external quantum network for network connectivity. Instead, it requires manual configuration of an external_network_bridge for connectivity. Now that the provider network extension allows creation of quantum networks that do provide external connectivity, the l3-agent should support external connectivity through such networks. This can be done in a backward-compatible way by interpreting an empty external_network_bridge configuration variable as indicating that the external network should actually be used for connectivity. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1056437/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
