Feature Overview (mandatory - Complete while in New status)

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 (mandatory - Complete while in New status)

• 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

<---- to be filled out ---->

Requirements (mandatory -_ Complete while in Refinement status):
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 (mandatory - Complete while in Refinement status):
Acceptance Criteria articulates and defines the value proposition - what is required to meet the goal and intent of this Feature. The Acceptance Criteria provides a detailed definition of scope and the expected outcomes - from a users point of view
…
<your text here>

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):
Include use case diagrams, main success scenarios, alternative flow scenarios.
<your text here>

Out of Scope __(Initial completion while in Refinement status):
High-level list of items or persona’s that are out of scope.
<your text here>

Documentation Considerations __(Initial completion while in Refinement status):
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation..
<your text here>

Questions to Answer __(Initial completion while in Refinement status):
Include a list of refinement / architectural questions that may need to be answered before coding can begin.
<your text here>

Background and Strategic Fit (Initial completion while in Refinement status):
Provide any additional context is needed to frame the feature.
<your text here>

Customer Considerations __(Initial completion while in Refinement status):
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
<your text here>

Team Sign Off (Completion while in Planning status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

• …