Make share shrinking support a capability

Registered by Goutham Pacha Ravi on 2018-11-07

Manila supports end users discovering capabilities with the help of tenant-visible extra specs. This approach makes it very easy for cloud administrators (that understand their backend storage systems) to provide a storage service catalog on their clouds.

Shared file systems are inherently elastic, however, there are many shared file system storage providers in the wild that do not support "shrinking" file shares. So, it is not a "required" feature to implement on storage drivers within manila. See the feature support martix for the Rocky cycle here: https://docs.openstack.org/manila/rocky/admin/share_back_ends_feature_support_mapping.html

Currently there is no way for end users to know before hand if the storage backend their shares end up on will support shrinking. If we included "shrinking_support" as a capability, we would be able to reject share shrinking requests via the API directly. The UI could discover if a given share was provisioned on a backend that supported shrinking shares, and disallow shrinking to lend a better user experience.

Blueprint information

Status:
Not started
Approver:
Tom Barron
Priority:
Undefined
Drafter:
Goutham Pacha Ravi
Direction:
Needs approval
Assignee:
Goutham Pacha Ravi
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:capability-improvements,n,z

Addressed by: https://review.openstack.org/616383
    Share and back end capabilities improvements

Gerrit topic: https://review.openstack.org/#q,topic:bp/storage-proto-enhancement,n,z

Addressed by: https://review.openstack.org/616634
    Share and back end capabilities improvements

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.