We should probably favor effort [1] rather than customize the existing logic. If [1] gets implemented, then possibilities are endless.
[1] https://bugs.launchpad.net/neutron/+bug/1690438 ** Changed in: neutron Importance: Undecided => Wishlist ** Changed in: neutron Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1664534 Title: [RFE] Auto allocated topology with no SNAT Status in neutron: Won't Fix Bug description: Today the neutron auto-allocated-topology (aka "get me a network") plugin/service allocates a router using the default enable_snat value for routers (True); so the resulting topology always has SNAT enabled. Some deployments would benefit from the ability to provision auto-allocated topologies that disable SNAT routing directly into the address space of the external network. One such way to support this ability would be to provide a simple configuration option such as `auto_topology_enable_snat` that's used by the service plugin when provisioning the router (for `enable_snat`). This would allow deployers the ability to configure the default SNAT behavior for auto-allocated topologies. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1664534/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
