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

   ### Description
   
   The new release [Libvirt-Java 
v0.5.3](https://gitlab.com/libvirt/libvirt-java/-/tags/v0.5.3) now supports 
`virDomainMigrate3`[[1]](https://gitlab.com/libvirt/libvirt-java/),[[2]](https://gitlab.com/libvirt/libvirt-java/-/commit/e45d3fb8bccab2d3048f902f0be74308afc923df),
 a powerful and flexible _domain migrate_ command in Libvirt. This command 
allows pointing just the Root volume to be migrated, saving a lot of compute 
resources, network bandwidth, and time. 
   
   Likely, data disks hold TBs of data, while Root volumes hundreds of GBs. 
This allows saving crucial time, bandwidth, and processing.
   
   It can easily save several hours to offload a KVM machine depending on the 
amount of VMs to be migrated and data disks attached to the respective VMs.
   
   [[1] Libvirt-Java](https://gitlab.com/libvirt/libvirt-java/)
   [[2] commit that added `virtDomainMigrate3` into the 
Libvirt-Java](https://gitlab.com/libvirt/libvirt-java/-/commit/e45d3fb8bccab2d3048f902f0be74308afc923df)
   Fore reference, PR https://github.com/apache/cloudstack/pull/6472 added 
`libvirt-java v0.5.3` into CloudStack.
   
   <!--- 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: AUTOMATATION 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)
   - [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
   
   - [X] Major
   - [ ] Minor
   
   
   ### 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 
-->
   <!-- see how your change affects other areas of the code, etc. -->
   Tested migration of VM with local Root (50GB) + data-disk (100GB)
   1. As an example, this is a scenario without this PR:
   ```
   ~# virsh domjobinfo i-2-345-VM
   Job type:         Unbounded   
   Operation:        Outgoing migration
   Time elapsed:     17063        ms
   Data processed:   2.938 GiB
   Data remaining:   147.065 GiB
   Data total:       150.004 GiB
   File processed:   2.938 MiB
   File remaining:   147.065 GiB
   File total:       150.004 GiB
   ```
   **Data total 150.004  GiB**
   
   2. When testing the same migration but with the changes of the PR:
   ```
   ~# virsh domjobinfo i-2-345-VM
   Job type:         Unbounded   
   Operation:        Outgoing migration
   Time elapsed:     10300        ms
   Data processed:   952.000 MiB
   Data remaining:   49.070 GiB
   Data total:       50.000 GiB
   File processed:   952.000 MiB
   File remaining:   49.070 GiB
   File total:       50.000 GiB
   ```
   **Data total 50.000 GiB**
   
   <!-- 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