Feature Overview (mandatory - Complete while in New status)
JIO AI project is using NetApp backend over iSCSI with multiple pools, they have large size images (~ 75 GB) to create BFV VMs and reduce the time to boot by using glance cinder optimization OR the image volume cache optimization but this image gets caches in one pool and there needs to one copy per pool to optimize the clone for bootable volume. This restriction requires customer to have 4 copies of the same image for all the pool in that backend.  Cinder already have the improvement in place to clone the volume across the pool that will remove the need to maintain copy per pool which will reduce the overall space requirement. 

Goals (mandatory - Complete while in New status)

• Backport the base framework patches for clone across pool
• Backport the bug fix in the code path for clone across pool
• Backport NetApp patches for clone across pool
• Tempest tests for this feature
• Upstream CI coverage for the tempest tests

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):

All the required patches are merged upstream and backported to RHOSO 18 downstream with proper testing.

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):

Jio AI wants have 3 cinder NetApp backends, each consisting of multiple pools (ranging from 2-4 per backend).
They want to store image in one backend pool and should be able to create volumes in that backend across it's pools without copying the image from one pool to another.

Out of Scope {}{}(Initial completion while in Refinement status):

NA

Documentation Considerations {}{}(Initial completion while in Refinement status):

Since there is no user configuration that needs to be enabled for this feature, we can only document the part about this optimization being available and can be used by customers for their use cases.

Questions to Answer {}{}(Initial completion while in Refinement status):

NA

Background and Strategic Fit (Initial completion while in Refinement status):

NA

Customer Considerations {}{}(Initial completion while in Refinement status):

NA

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

• …