neutron

[RFE] Self-Aware Network Providers

Bug #1596659 reported by Ankur
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Triaged
Wishlist
Ankur

Bug Description

The issue stemmed up from this bug submitted in Horizon:
https://bugs.launchpad.net/horizon/+bug/1596411

The ability for a new Neutron feature to allow users to find out the network type providers supported in their project.

i.e when doing a "net-create" one can specify the --provider:network_type.
If I were to create a network with Geneve in my current env it will throw an error saying "Invalid input for operation: network_type value 'geneve' not supported.

The proposed solution would return the list of network-types supported (VLAN, GRE, VXLAN...)
from which one can create a network without running into Error messages.

Ability to expose which plugins and drivers are enabled and supported.

Tags: rfe
Ankur (ankur-gupta-f)
Changed in neutron:
assignee: nobody → Ankur (ankur-gupta-f)
Dariusz Smigiel (smigiel-dariusz)
Changed in neutron:
importance: Undecided → Wishlist
Revision history for this message
Assaf Muller (amuller) wrote :

The --provider:network_type is admin-only of course, as would be the new API. I think it's a reasonable request.

Changed in neutron:
status: New → Triaged
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

I am reasonably convinced this is a duplicate, and as such the outcome of the decision should not change, unless sometime else changed :)

Revision history for this message
Akihiro Motoki (amotoki) wrote :

It sounds a reasonable request. On the other hand, we refused a similar feature request which exposes configuration options.
We receive a similar request several time. Do we need this kind of API?

BTW, The referred Horizon bug looks unrelated.

Revision history for this message
Ankur (ankur-gupta-f) wrote :

Akihiro: I am getting all my bug numbers and links all mixed up.

Yes, it along the same lines as the duplicate bug.
For the exact same reasons listed in the duplicate bug as well.

I won't bother editing bug due to the decision to not fix.

Reasons for doing being: avoiding hardcoded network provider types in Horizon, and ease of use for Horizon admins.

Exposing some of the values (type_drivers, mechanism_drivers, etc..) from the ml2_conf.ini so admins can understand what is supported.

These are all the related Horizon bugs reported that I could find:
https://bugs.launchpad.net/horizon/+bug/1419988
https://bugs.launchpad.net/horizon/+bug/1477522
https://bugs.launchpad.net/horizon/+bug/1478887

If it is a concern that has come up multiple times. There should be another discussion about it.
I don't think the "too much engineering" is a valid reason not to do it if resources are available.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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