[RFE] Neutron API enhancement for visibility into multi-segmented networks
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Expired
|
Wishlist
|
Unassigned |
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:/
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:/
However, this does not have any port specific information - i.e. ability to see which port is bound to which segment.
description: | updated |
Changed in neutron: | |
status: | Incomplete → Triaged |
Changed in neutron: | |
importance: | Undecided → Wishlist |
tags: | added: rfe |
Isn't this a dup of this spec, that is in progress? https:/ /review. openstack. org/#/c/ 225384/ 22/specs/ newton/ routed- networks. rst