yahoo-eng-team team mailing list archive

[Kevin Benton <1469668@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Both the get-me-a-network spec and the use cases laid out by several
large deployers (Neutron networks limited to a single rack or other
subset of datacenter) could benefit from a port scheduler. This port
scheduler would allow Nova (or another caller) to request a port via
port create without providing a network ID. The port scheduler would
then populate the appropriate network ID depending on the request
details and port creation would continue as normal.

In lieu of the network ID, the client can pass optional hints to
constrain the network selection (e.g. an external network that the
network can reach). If the client doesn't pass any hints, this would
become the 'get-me-a-network' use case where it's entirely up to
Neutron.

In order to satisfy the use case where not all Neutron networks are
available everywhere, this scheduler should also expose an API that
allows a Nova scheduling filter to be written that can ask Neutron which
hosts can be used for the Neutron port details it was given.

** Affects: neutron
     Importance: Undecided
     Assignee: Kevin Benton (kevinbenton)
         Status: New


** Tags: rfe

** Changed in: neutron
     Assignee: (unassigned) => Kevin Benton (kevinbenton)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1469668

Title:
  Add a neutron port-scheduler component

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Both the get-me-a-network spec and the use cases laid out by several
  large deployers (Neutron networks limited to a single rack or other
  subset of datacenter) could benefit from a port scheduler. This port
  scheduler would allow Nova (or another caller) to request a port via
  port create without providing a network ID. The port scheduler would
  then populate the appropriate network ID depending on the request
  details and port creation would continue as normal.

  In lieu of the network ID, the client can pass optional hints to
  constrain the network selection (e.g. an external network that the
  network can reach). If the client doesn't pass any hints, this would
  become the 'get-me-a-network' use case where it's entirely up to
  Neutron.

  In order to satisfy the use case where not all Neutron networks are
  available everywhere, this scheduler should also expose an API that
  allows a Nova scheduling filter to be written that can ask Neutron
  which hosts can be used for the Neutron port details it was given.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1469668/+subscriptions