yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1573197@xxxxxxxxxxxxxxxxxx>]

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

** Changed in: neutron
       Status: Incomplete => Expired

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

Title:
  [RFE] Neutron API enhancement for visibility into multi-segmented
  networks

Status in neutron:
  Expired

Bug description:
  This RFE is filed for Manila-Neutron integration in mind.
  Manila is shared FS as a Service and wants to leverage neutron networks for multi-tenancy support. Typically, storage clusters will be connected to select TORs, therefore, most of the neutron networks utilized by Manila deployments will be multi-segmented networks.

  Please see Manila use case here -
  https://wiki.openstack.org/wiki/Manila/design/manila-newton-hpb-
  support

  With HPB, as ML2 drivers dynamically create segments, they select the
  segmentation-type and segmentation-Ids dynamically as they are binding
  the port of a specific instance to host (and or TOR). While this
  information is available in ML2 drivers, it is not visible to users or
  admins. There is no mechanism in neutron API to provide such
  information to users.

  For example, in a typical deployment, a user creates a neutron network
  (net-A) and boots an instance and attaches to the net-A. For any
  reason (such as debug-ability), they can see what segmentation-type or
  segmentation-id is associated with the instance by simply using
  "neutron net-show net-A". They can build automation by using neutron
  API to get visibility into the connectivity information. With HPB,
  this information is not available. Therefore, for the users of multi-
  segmented networks, such information is lost - hence, Manila is
  looking for a cleaner way from Neutron to provide such information.
  Moreover, this is a generic problem for operators with the HPB - i.e
  no visibility.

  Routed networks is providing visibility into the multi-segmented networks through a new CRUD API described here - https://review.openstack.org/#/c/225384/22/specs/newton/routed-networks.rst
  However, this does not have any port specific information - i.e. ability to see which port is bound to which segment.

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