Allow the NVP plugin to use configurable gateway modes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Wishlist
|
Salvatore Orlando |
Bug Description
As of the current implementation, the Nicira plugin always adds a default SNAT rule before creating the floating IPs.
This means that we are unable to clearly separate the 'floating IP (DNAT)' and 'external gateway access (SNAT)' offered by the Quantum logical router.
- One can configure a router for SNAT, but not do DNAT (just doing PUT /routers/
- However one cannot decide to allow a router to connect floating IPs without doing SNAT.
To this aim the 'external_
For instance:
{
'external_
{
'network_id': <net_id>,
'snat': false,
'dnat': true
}
}
The blueprint l3-ext-gw-modes adds this kind of support in the API layer and the OVS plugin. The NVP plugin might benefit from this feature too.
tags: | added: api nicira |
description: | updated |
Changed in quantum: | |
milestone: | grizzly-3 → grizzly-rc1 |
Changed in quantum: | |
milestone: | grizzly-rc1 → havana-1 |
Changed in quantum: | |
importance: | Medium → Wishlist |
status: | New → Triaged |
Changed in quantum: | |
milestone: | havana-1 → havana-2 |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | havana-2 → 2013.2 |
I have the similar demand and it looks a reasonable direction to me. In my case we want 'external gateway access' without SNAT and just to use 'router:external' to determine a default gateway to the external network.
As 'snat' and 'dnat' proposed take a boolean value, how about adding 'enable_' as a prefix to them?