orchestration,hypervisor: allow custom manufacturer, product for vm metadata#9163
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9163 +/- ##
===========================================
Coverage 15.55% 15.55%
- Complexity 12010 12012 +2
===========================================
Files 5500 5500
Lines 481850 481889 +39
Branches 61843 59361 -2482
===========================================
+ Hits 74935 74967 +32
- Misses 398628 398636 +8
+ Partials 8287 8286 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Related to apache/cloudstack#9163 Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
DaanHoogland
left a comment
There was a problem hiding this comment.
clgtm, one minor design option/issue. I would prefer the check to be MS side
engine/orchestration/src/main/java/com/cloud/vm/VirtualMachineManagerImpl.java
Outdated
Show resolved
Hide resolved
|
@blueorangutan package |
|
@shwstppr a [SL] 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 [SF]: ✖️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 9795 |
yadvr
left a comment
There was a problem hiding this comment.
LGTM but we should add caveat that it could break cloud-init
|
@shwstppr is this ready for review or still need some work (as the PR is in draft) @blueorangutan package |
|
@rohityadavcloud a [SL] 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 [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 9833 |
|
@rohityadavcloud marked it ready A note about cloud-init behaviour is added in the global config descriptions and in the doc PR |
thanks @shwstppr overall looks good to me
|
|
@weizhouapache added tests |
|
@blueorangutan package |
|
@shwstppr a [SL] 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. |
thanks |
|
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 9839 |
|
@blueorangutan test |
|
@shwstppr a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-10424)
|
|
@blueorangutan test rocky8 kvm-rocky8 |
|
@weizhouapache a [SL] Trillian-Jenkins test job (rocky8 mgmt + kvm-rocky8) has been kicked to run smoke tests |
|
[SF] Trillian Build Failed (tid-10435) |
|
@blueorangutan package |
|
@shwstppr a [SL] 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 [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 10429 |
|
@blueorangutan LLtest alma8 kvm-alma8 |
|
@DaanHoogland a [LL] Trillian-Jenkins test job (alma8 mgmt + kvm-alma8) has been kicked to run smoke tests |
|
[LL]Trillian test result (tid-6962)
|
metadata Fixes apache#9142 Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
7f3c76a to
032d8f4
Compare
|
@blueorangutan package |
|
@shwstppr a [SL] 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 [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 10745 |
|
@blueorangutan test |
|
@shwstppr a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
vladimirpetrov
left a comment
There was a problem hiding this comment.
LGTM based on manual testing. Tested with Oracle Linux 8 KVM and CentOS 7 guest OS.
|
[SF] Trillian test result (tid-11136)
|
…pache#9163) Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
Description
Fixes #9142
Doc PR: apache/cloudstack-documentation#402
New global settings added to specify VM metadata wrt manufacturer and product:
vm.metadata.manufacturervm.metadata.productTypes of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?