[RFE]: Provider network creation for non admins

Bug #1630880 reported by Gergely Csatari
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Expired
Undecided
Unassigned

Bug Description

In several cases the cloud admin and network admin of a cloud are different entities, therefore it should be possible that non-(cloud)admin users can also create provider networks. To make it configurable probably a policy based control would be required.

One specific case is in the NVF universe where VNF-s often use provider networks due to their special networking requirements, the cloud is administered by the telecom network operator while the VNF (a group of VM-s, let's say) is deployed by a VNFM what should not have admin rights.
A more detailed description of the NFV case is described in Chapter 2.4 of the netready requirements document [1].

[1]: http://artifacts.opnfv.org/netready/colorado/docs/requirements/index.html

Tags: rfe
Revision history for this message
Doug Wiegley (dougwig) wrote :

I think this is already possible via policy.json, isn't it?

Changed in neutron:
status: New → Incomplete
Revision history for this message
Gergely Csatari (gergely-csatari) wrote :

According to my knowledge currently only administrators can manage provider network. OpenStack Networking Guide is also stating the same [1].

[1]: http://docs.openstack.org/newton/networking-guide/scenario-provider-ovs.html

Revision history for this message
Gergely Csatari (gergely-csatari) wrote :

Now looking into this a bit more deeply it seems that @dougwig is correct. However the default setting is that only the admins can create provider networks, it is possible to change these default values.
The relevant policy.json parameters are: "create_network:provider:network_type",
 "create_network:provider:physical_network" and
 "create_network:provider:segmentation_id".

OpenStack networking guide [1] is not correct.

[1]: http://docs.openstack.org/newton/networking-guide/scenario-provider-ovs.html

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.