-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Enable system VM volume migration for KVM #6341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable system VM volume migration for KVM #6341
Conversation
|
Found UI changes, kicking a new UI QA build |
PR Analysishttps://sonarcloud.io/summary/new_code?id=apachecloudstack&pullRequest=6341 PR Coverage Report
|
|
Can you merge latest main branch to your PR branch @GutoVeronezi ? |
|
@rohityadavcloud, done. |
|
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
|
Found UI changes, kicking a new UI QA build |
|
@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
UI build: ✔️ |
DaanHoogland
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clgtm
|
awful lot of travis failures |
|
re-try |
|
Found UI changes, kicking a new UI QA build |
|
@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
@GutoVeronezi PR is marked for milestone 4.17.1.0, schema changes are also in 4170to4171 upgrade path but base branch is main. Should it be changed to 4.17 instead? cc @DaanHoogland |
|
UI build: ✔️ |
eb74c40 to
fd3b829
Compare
|
@shwstppr a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-4597)
|
|
Found UI changes, kicking a new UI QA build |
|
@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
UI build: ✔️ |
|
re-kicking travis |
|
@GutoVeronezi can you please check why tests from |
shwstppr
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@GutoVeronezi this is causing failures
engine/schema/src/main/resources/META-INF/db/schema-41700to41710.sql
Outdated
Show resolved
Hide resolved
engine/schema/src/main/resources/META-INF/db/schema-41700to41710.sql
Outdated
Show resolved
Hide resolved
|
Found UI changes, kicking a new UI QA build |
|
@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
UI build: ✔️ |
|
Kudos, SonarCloud Quality Gate passed! |
|
@blueorangutan package |
|
@shwstppr a Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result: ✖️ el7 ✔️ el8 ✖️ debian ✖️ suse15. SL-JID 3932 |
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 3938 |
|
@blueorangutan test |
|
@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-4645)
|
Release 4.16.0.0 introduced a feature for migrating system VM volumes (apache#4385). However, it was enabled only for VMWare. This PR intends to enable the feature for KVM too. Co-authored-by: GutoVeronezi <daniel@scclouds.com.br>








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
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
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.