Goutham, is there any use case at all for a manila user, even a manila admin, actually *needing* to get the network type or segmentation id of an underlying neutron network via the manila share-network api rather than via the neutron api itself?
I'm inclined to think the answer is no and that we should simply remove these fields from the manila share-network view builder altogether rather than having manila policy control their display. Neutron owns these fields, not manila, so neutron policy should have exclusive control of who can view them.
Goutham, is there any use case at all for a manila user, even a manila admin, actually *needing* to get the network type or segmentation id of an underlying neutron network via the manila share-network api rather than via the neutron api itself?
I'm inclined to think the answer is no and that we should simply remove these fields from the manila share-network view builder altogether rather than having manila policy control their display. Neutron owns these fields, not manila, so neutron policy should have exclusive control of who can view them.