NetApp Manila Driver: When using flat networks, do not modify broadcast groups

Bug #1706358 reported by chad morgenstern on 2017-07-25
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

When using flat networks, there is no need for the NetApp Manila driver to take explicit control of the ONTAP physical interface by moving it to a dedicated broadcast domain as all ip addresses in a single flat network need to be unique.

Lets modify the driver to leave the NetApp network port in the default broadcast domain, only moving the port if the requested MTU is different than the MTU wherein the port currently resides.

Changed in manila:
importance: Undecided → Low
status: New → Confirmed
tags: added: drivers netapp vendor
Changed in manila:
milestone: none → pike-3
chad morgenstern (mchad) wrote :

Further, when selecting interfaces, add logic to determine if the interface selected already has lifs assigned, if it does continue on looking for a port to use until one without a lif is found

Changed in manila:
milestone: pike-3 → pike-rc1
Changed in manila:
assignee: nobody → Goutham Pacha Ravi (gouthamr)
Ben Swartzlander (bswartz) wrote :

Missed pike, untargetting

Changed in manila:
milestone: pike-rc1 → none
Changed in manila:
assignee: Goutham Pacha Ravi (gouthamr) → nobody
Tom Barron (tpb) on 2018-06-19
tags: added: driver
removed: drivers
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers