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

   ### Description
   
   Release 4.16.0.0 introduced a feature for migrating system VM volumes 
(#4385). However, it was enabled only for VMWare.
   
   This PR intends to enable the feature for KVM too.
   
   ### 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)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Feature/Enhancement Scale
   
   - [ ] Major
   - [ x] Minor
   
   ### How Has This Been Tested?
   
   It was tested in a local lab.
   
   (I tested the process for each system VM type)
   
   To test the SSVM and CPVM, I enabled a zone to create them. When they were 
created, I disabled the zone. I accessed the system VMs and created files to 
validate later. I stopped them and migrated the volumes. I checked the 
references in database and storage and then I started the system VMs. After 
that, I accessed them again and verified the files. The migration performed 
successfully, the data was kept and the system VMs were working fine.
   
   To test the VR, I created a network. I accessed the VR and created a file to 
validate later. I stopped the VR and migrated the volume. I checked the 
reference in database and storage and then I started the VR. After that, I 
accessed it again and verified the file. The migration performed successfully, 
the data was kept and the VR was working fine.


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