Configurable External Gateway Modes
This blueprint is a follow up of the discussion around bug 1121129.
In a nutshell, the goal is to allow users of the quantum API for specifying how a quantum router should behave when an external network is connected. For more details, please refer to the specification page.
In order to guarantee full backward compatibility the current behaviour (default SNAT and DNAT - floating IPs) enabled will be the default selection.
Plugins supporting the L3 API should not be required to support this feature too.
To this aim, this change should be implemented as an API extension.
Blueprint information
- Status:
- Complete
- Approver:
- Mark McClain
- Priority:
- Medium
- Drafter:
- Salvatore Orlando
- Direction:
- Approved
- Assignee:
- Salvatore Orlando
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
- Implemented
- Milestone target:
- 2013.2
- Started by
- Salvatore Orlando
- Completed by
- Mark McClain
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Configurable external gateway modes
Addressed by: https:/
Ensure no duplicate rule in IPTablesManager
Question:nati
There is usecase we need SNAT or DNAT on the others port.
How about keep external_
dnat_ports= [
port_
]
snat_ports= [
port_
]
?
--> I am replying to Your Question at: https:/
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Preparatory work on extension framework for configurable gateway modes
Addressed by: https:/
Enable policy control over external_
Bumping out to H-2 as we did not manage to complete another review cycle
Addressed by: https:/
Configurable external gateway modes