L3 agent should support provider external networks
Bug #1056437 reported by
Robert Kukura
This bug affects 10 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Robert Kukura |
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_
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_
tags: | added: folsom-rc-potential |
tags: |
added: folsom-backport-potential removed: folsom-rc-potential |
Changed in quantum: | |
assignee: | nobody → Robert Kukura (rkukura) |
importance: | Undecided → High |
Changed in quantum: | |
milestone: | none → grizzly-2 |
status: | Confirmed → In Progress |
tags: | added: l3-ipam-dhcp |
Changed in quantum: | |
milestone: | havana-1 → havana-2 |
Changed in neutron: | |
milestone: | havana-2 → havana-3 |
Changed in neutron: | |
milestone: | havana-3 → havana-rc1 |
tags: |
added: havana-backport-potential removed: havana-rc-potential |
To post a comment you must log in.
I agree the external network might benefit from the provider networks extension.
It seems the intention here is to map the external gateway to a physical network if external_ network_ bridge = ""
So the external gateway, for instance, could be eth0.
Floating IPs and the gateway itself are currently configured as quantum ports on the external network bridge; in this case we'll need to find alternative; configuring multiple IPs on the physical interface is a possibility which is however different from what the agent currently does.
I am thinking whether we can keep the external_network_ bridge and just use the provider network extension to map it to a physical network, or not use it as you propose but instead attach floating IPs to br-int.