Public bug reported: Some deployments (private/enterprise clouds) would like to disable snat by default. For example some enterprise policies disallow snat as it anonymizes/hides source ips and some private clouds don't use snat/nat features.
But it's currently not possible to change enable_snat default value. A workaround is to allow and enforce neutron users to set enable_snat attribute to False on external_gateway_info update through policy, but it's not user friendly as neutron users must specify enable_snat=False and if they do not neutron returns a 404 error. ** Affects: neutron Importance: Undecided Assignee: Cedric Brandily (cbrandily) Status: In Progress ** Tags: l3-ipam-dhcp -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1388858 Title: Neutron disallows to change default enable_snat value Status in OpenStack Neutron (virtual network service): In Progress Bug description: Some deployments (private/enterprise clouds) would like to disable snat by default. For example some enterprise policies disallow snat as it anonymizes/hides source ips and some private clouds don't use snat/nat features. But it's currently not possible to change enable_snat default value. A workaround is to allow and enforce neutron users to set enable_snat attribute to False on external_gateway_info update through policy, but it's not user friendly as neutron users must specify enable_snat=False and if they do not neutron returns a 404 error. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1388858/+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