rajiv-jain-netapp opened a new pull request, #14243:
URL: https://github.com/apache/cloudstack/pull/14243

   Enable the managed-storage template cache flow for the ONTAP primary storage 
plugin so that VM root volumes are cloned from a template copy kept on the 
pool's FlexVolume instead of being copied from secondary storage for every 
deployment.
   
   - Advertise CAN_CREATE_VOLUME_FROM_VOLUME from the datastore driver.
   - Create the template cache on primary: an iSCSI LUN (identity tracked on 
template_spool_ref) or a qcow2 file for NFS, populated by the KVM host.
   - Clone new volumes from the cached template: LUN clone for iSCSI and ONTAP 
file clone (FileCloneRequest) for NFS, growing the clone when the disk offering 
is larger than the template.
   - Clean up the cached LUN/file when the template is removed from the pool; a 
missing file is treated as already deleted.
   - Move protocol-specific create/clone/resize logic into UnifiedSANStrategy 
and UnifiedNASStrategy, and add a StorageStrategy helper to poll an optional 
async job.
   - Add unit tests for the driver and the NAS/SAN strategies.
   
   ### Description
   
   This PR...
   <!--- Describe your changes in DETAIL - And how has behaviour functionally 
changed. -->
   
   <!-- For new features, provide link to FS, dev ML discussion etc. -->
   <!-- In case of bug fix, the expected and actual behaviours, steps to 
reproduce. -->
   
   <!-- When "Fixes: #<id>" is specified, the issue/PR will automatically be 
closed when this PR gets merged -->
   <!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" -->
   <!-- Fixes: # -->
   
   <!--- 
******************************************************************************* 
-->
   <!--- NOTE: AUTOMATION USES THE DESCRIPTIONS TO SET LABELS AND PRODUCE 
DOCUMENTATION. -->
   <!--- PLEASE PUT AN 'X' in only **ONE** box -->
   <!--- 
******************************************************************************* 
-->
   
   ### Types of changes
   
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   - [ ] Build/CI
   - [ ] Test (unit or integration test code)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Feature/Enhancement Scale
   
   - [ ] Major
   - [ ] Minor
   
   #### Bug Severity
   
   - [ ] BLOCKER
   - [ ] Critical
   - [ ] Major
   - [ ] Minor
   - [ ] Trivial
   
   ### Screenshots (if appropriate):
   
   ### How Has This Been Tested?
   
   <!-- Please describe in detail how you tested your changes. -->
   <!-- Include details of your testing environment, and the tests you ran to 
-->
   
   #### How did you try to break this feature and the system with this change?
   
   <!-- see how your change affects other areas of the code, etc. -->
   
   <!-- Please read the 
[CONTRIBUTING](https://github.com/apache/cloudstack/blob/main/CONTRIBUTING.md) 
document -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to