3d5d378769
Currently non-admin users can create extra-routes when the nexthop is on router-interfaces subnets but not on external-network subnet. Indeed user permissions are used to get router ports in order to validate nexthops BUT non-admin users don't "see" router port on its external network. This change uses an elevated context instead of user context to enable non-admins to create "external" extra-routes. APIImpact Closes-Bug: #1538767 Change-Id: I08b1d8586a4cd241a3589e8cb7151b77ab679124
Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
External Resources:
The homepage for Neutron is: http://launchpad.net/neutron. Use this site for asking for help, and filing bugs. Code is available on git.openstack.org at <http://git.openstack.org/cgit/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
- Neutron Administrator Guide
- Networking Guide
- Neutron API Reference:
-
http://docs.openstack.org/api/openstack-network/2.0/content/
- Current Neutron developer documentation is available at:
For help on usage and hacking of Neutron, please send mail to <mailto:openstack-dev@lists.openstack.org>.
For information on how to contribute to Neutron, please see the contents of the CONTRIBUTING.rst file.