yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #61499
[Bug 1664461] [NEW] [RFE] Neutron API enhancement - make network and subnets as optional
Public bug reported:
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.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1664461
Title:
[RFE] Neutron API enhancement - make network and subnets as optional
Status in neutron:
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1664461/+subscriptions
Follow ups