[RFE] Neutron API enhancement - make network and subnets as optional

Bug #1664461 reported by Sukhdev Kapur on 2017-02-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Lets enhance Neutron API to make it flexible so that newer networking use cases can be accommodated.

More specifically, remove the inter-dependency of network, subnets, and ports upon each other. One should be allowed to create any of these resources independently without forced to create higher precedence resource. For example, one has to create a network first in order to create a port (neutron port-create). This forces the back-ends/plugins/drivers to create dummy networks in many instance to be able to create ports. This creates a scale issue.

If we removed these inter-dependencies by making these resources as optional attributes, one should be able to create a port first, and then, depending upon the applications behavior, be able to attach this port to a network. By making these as optional attributes, we keep the API backward compatible while making it flexible for newer use cases.

Tags: rfe Edit Tag help
Reedip (reedip-banerjee) on 2017-02-14
tags: added: api
Akihiro Motoki (amotoki) on 2017-02-22
tags: added: rfe
tags: removed: api

Please elaborate on your proposal. Creating a network creates no scale issue as without subnets networks are just weightless logical objects.

Changed in neutron:
importance: Undecided → Wishlist
status: New → Confirmed

No feedback since last solicitation.

Changed in neutron:
status: Confirmed → Incomplete
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  Edit
Everyone can see this information.

Other bug subscribers