Public bug reported: The option max_fixed_ips_per_port was introduced under the idea of preventing users from eating up IP addresses on shared networks that they don't own. However, we already prevent users from updating the fixed_ips of their port on networks that they don't own.[1]
Unless there is a use case for this option that I am missing, we should just deprecate this option. Please provide use cases if you think otherwise. 1. https://github.com/openstack/neutron/blob/82866276b0cf7a10cbb9f5e92a12680b096a3770/etc/policy.json#L78 ** Affects: neutron Importance: Low Assignee: Kevin Benton (kevinbenton) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Kevin Benton (kevinbenton) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1502356 Title: max_fixed_ips_per_port appears to be unnecessary Status in neutron: In Progress Bug description: The option max_fixed_ips_per_port was introduced under the idea of preventing users from eating up IP addresses on shared networks that they don't own. However, we already prevent users from updating the fixed_ips of their port on networks that they don't own.[1] Unless there is a use case for this option that I am missing, we should just deprecate this option. Please provide use cases if you think otherwise. 1. https://github.com/openstack/neutron/blob/82866276b0cf7a10cbb9f5e92a12680b096a3770/etc/policy.json#L78 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1502356/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
