slavkap opened a new pull request, #14203:
URL: https://github.com/apache/cloudstack/pull/14203

   ### Description
   
   Volume pool/path info is now sent to the agent whenever a VM has a StorPool 
volume, not just when the VM looks Stopped, since nasbackup.sh re-checks the 
VM's actual liveness itself right before acting and needs the StorPool path to 
clone a backup source disk if it finds the VM already stopped.
   
   - StorPoolStorageAdaptor.createPhysicalDisk() now creates and attaches a 
StorPool volume (previously a no-op returning null), used when restoring a 
backup provisions a new volume.
   - nasbackup.sh clones the live StorPool volume into a point-in-time volume 
before reading from it for a cold backup, and cleans it up afterwards (with an 
EXIT trap as a safety net).
   - Backup size is now reported via an explicit BACKUP_SIZE_TOTAL=<bytes> 
marker on stdout instead of being inferred from output position/shape, which 
broke down once StorPool added a third code shape; take-backup errors are now 
always returned as a BackupAnswer rather than letting an uncaught exception 
surface as a plain Answer.
   - Restore reports back the volume path StorPool actually assigned 
(BackupAnswer.restoredVolumePath) instead of the path CloudStack guessed, since 
StorPool controls the device path itself.
   - Backup file identifiers are normalized to the qcow2 basename so StorPool's 
full device path matches what nasbackup.sh expects.
   
   ### 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)
   - [X] 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
   
   - [X] Major
   - [ ] Minor
   
   
   ### How Has This Been Tested?
   Manual testing and smoke tests with StorPool as a primary storage, KVM 
hypervisors


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