You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2019/07/22 15:33:52 UTC

[GitHub] [cloudstack] GabrielBrascher opened a new pull request #3508: Enable KVM storage data motion on KVM hypervisor_capabilities

GabrielBrascher opened a new pull request #3508: Enable KVM storage data motion on KVM hypervisor_capabilities
URL: https://github.com/apache/cloudstack/pull/3508
 
 
   ## Description
   <!--- Describe your changes in detail -->
   Considering that we have addressed a considerable effort on allowing KVM to perform storage data motion, this PR proposes updating the 'hypervisor_capabilities' table setting the 'storage_motion_supported' to '1' for KVM.
   
   **PRs that implemented KVM storage motion features:**
   - Non-managed storages
   #2997 KVM VM live migration with ROOT volume on file storage type
   #2983 KVM live storage migration intra cluster from NFS source and destination
   - Managed storages
   #2298 CLOUDSTACK-9620: Enhancements for managed storage
   <!-- 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: # -->
   
   ## Types of changes
   <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
   - [ ] 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)
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services