| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
¿@wido @weizhouapache @ravening @GabrielBrascher , can you guys look at this please? |
Sorry, something went wrong.
|
In this PR: #4341 The functionality was added that the rootDiskSize can be configured in an Offering. When we scale the VM we should also scale the rootdisk's size if that is bigger in the new offering. This PR does not seem to do that. We probably want that added as well. I really like this PR though. Very much welcome! |
Sorry, something went wrong.
|
@wido We already have the API resizeVolume, which is designed to scale the root disk as well as data disks, and it works with VMs in stopped or running states. This API scaleVirtualMachine was first designed to scale computing resources (memory, cpuNumber and cpuSpeed). I think we should not mix these two concepts here. |
Sorry, something went wrong.
After reading the code and comments from @GabrielBrascher I understand this code only works with custom service offerings, correct? If so, please disregard my comments. Otherwise, with PR #4341 merged we now have the option to make the root disk size a condition of the service offering. Thus when changing the offering one needs to make sure that the root disk is also resized according to the new offering. |
Sorry, something went wrong.
|
Can anyone review this? |
Sorry, something went wrong.
As every variable declared in interfaces are already final, this moving will be needed to mock tests in nexts commits
The values are according to service offering or global configs
Improve libvirt def
|
@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian. SL-JID 838 |
Sorry, something went wrong.
|
@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
Sorry, something went wrong.
|
Trillian test result (tid-1601)
|
Sorry, something went wrong.
There was a problem hiding this comment.
@GutoVeronezi overall it looks good. I've raised a few points to change in regards to the Source code header to meet the Apache license for Apache's projects.
Sorry, something went wrong.
| @@ -0,0 +1,43 @@ | |||
| /* | |||
| * Copyright 2021 The Apache Software Foundation. | |||
There was a problem hiding this comment.
Please check the Copyright
Sorry, something went wrong.
| @@ -0,0 +1,246 @@ | |||
| /* | |||
| * Copyright 2021 The Apache Software Foundation. | |||
There was a problem hiding this comment.
Please check the Copyright
Sorry, something went wrong.
| @@ -0,0 +1,105 @@ | |||
| /* | |||
| * Copyright 2021 The Apache Software Foundation. | |||
There was a problem hiding this comment.
Please check the Copyright
Sorry, something went wrong.
| @@ -0,0 +1,45 @@ | |||
| /* | |||
| * Copyright 2021 The Apache Software Foundation. | |||
There was a problem hiding this comment.
@GutoVeronezi I think that these source code headers need to be updated removing Copyright as we discussed in another PR (sorry but I forgot which one xD)
Sorry, something went wrong.
|
Manual tests LGTM. |
Sorry, something went wrong.
|
@GabrielBrascher done, thanks. |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for the PR, @GutoVeronezi.
LGTM, based on manual tests and code review.
Sorry, something went wrong.
|
@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 952 |
Sorry, something went wrong.
|
@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
Sorry, something went wrong.
|
Trillian test result (tid-1736)
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
ACS has an API to scale VMs scaleVirtualMachine, however dynamic scale of VMs is limited to XenServer and VMWare.
This PR intends suport live scale for VMs on KVM.
When we are using a custom service offerings, KVM's XML only receives the boot memory, but with this changes it will receive the max values defined in the service offerings. If it is a unconstrainced service offering, max values will be the vm.serviceoffering.cpu.cores.max and vm.serviceoffering.ram.size.max values . If they are 0, max values will be host or last host capacities.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
How Has This Been Tested?
I created unit tests for the code that is being introduced here. Moreover, it has been tested locally in a test lab. I created multiples VMs with multiples definitions and tested API with they: