Feature Overview 

OpenStack Manila has support for "managing" and "unmanaging" shares and share snapshots, a valuable workflow for cloud administrators to take shared file systems (and their snapshots) in and out of manila's management. Managing allows manila to adopt/import a share into a configured backend storage system, and apply manila specific extra specifications on it.

Consider for instance a possibility of moving a ceph cluster across OpenStack deployments; or rebuilding an existing OpenStack deployment and registering shares back. It's not trivial for an administrator to remove a share from manila or restore it into manila when performing these day2 cluster maintenance operations. Manila also doesn't support retype operations currently. The alternative to retyping is to migrate shares (which involves an expensive data copy) or to un-manage and re-manage them with a different share type.

Goals 

• The feature is helpful to OpenStack Administrators performing a migration or maintenance of their RHOSO clouds. Having this feature allows taking things outside the OpenStack control plane, or simultaneously offline and bringing them back when maintenance is complete
• Without this feature it is not possible to bring any pre-existing CephFS resources into OpenStack

Requirements
A list of specific needs, capabilities, or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the Feature shifts. If a non MVP requirement slips, it does not shift the feature.

Done - Acceptance Criteria 

• Manage/unmanage tests should be enabled in existing cephfs and native jobs, will need to backport downstream
• Tempest tests is enough for this feature - includes downstream coverage
• downstream user docs
• support enablement

Documentation Considerations 

• add a note for using cephfs identifier for subvolume instead of export paths
• remove existing limitation 

Questions to Answer 

1. Confirm we don't need any RelDel/Prod-CI team work and Epic