Enhance floating IP router lookup to consider extra routes
Allow floating IP association, not only to ports directly connected to the router, but also to internal addresses that are reachable by extra routes.
The use case is to allow "deep" network topologies with servers that are separated from the router by an intermediate device such as a multi-homed firewall or VPN gateway. The proposed to change will enable assigning floating IP addresses to the servers.
Please also see: https:/
Blueprint information
- Status:
- Complete
- Approver:
- Mark McClain
- Priority:
- Low
- Drafter:
- Ofer Barkai
- Direction:
- Needs approval
- Assignee:
- Ofer Barkai
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Needs Code Review
- Milestone target:
- None
- Started by
- Ofer Barkai
- Completed by
- Armando Migliaccio
Related branches
Related bugs
| Bug #1250105: Cannot assign a floating IP to an instance that is reachable by an extra route | Expired |
Sprints
Whiteboard
Nov-13-2015(armax): If someone is interested in pursuing it, this must be re-submitted according to guidelines defined in [1].
[1] http://
-----------------
September-3 (mestery): Moving out of Juno, this spec will need to be proposed again for Kilo once Kilo opens.
17-July (mestery): Moving to Juno-3.
6-Jun (mestery): Moving to Juno-2.
5-Mar(markmcclain): Deferring to Juno
Gerrit topic: https:/
Addressed by: https:/
Enhance floating IP router lookup
Mailing list thread:
http://
[gong yong sheng] I think, it makes sense.
Addressed by: https:/
Add blueprint floating-
