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
Prioritize hypervisor.uri configuration #8254
Conversation
@blueorangutan package |
@weizhouapache 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. |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #8254 +/- ##
============================================
+ Coverage 21.64% 29.14% +7.50%
- Complexity 21530 31049 +9519
============================================
Files 5052 5193 +141
Lines 343910 366293 +22383
Branches 49538 53556 +4018
============================================
+ Hits 74431 106773 +32342
+ Misses 258607 244881 -13726
- Partials 10872 14639 +3767
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 7807 |
@blueorangutan test |
@DaanHoogland a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
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
[SF] Trillian test result (tid-8384)
|
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
@DaanHoogland @weizhouapache do we need third-party testing for this one? |
in principle I'd say we always do, but I'm sensitive to arguments why we wouldn't. I think we can only decide on this based on the code and available automatic tests though, never relying on the author. I would appreciate it if you didn't trust my PRs in that respect either. |
Yes @GutoVeronezi |
I can put it on my tasks for the next week. |
cool, thanks @GutoVeronezi |
Hello guys I did some basic tests with the feature:
|
Merging this one based on the approvals and tests results. |
Co-authored-by: Henrique Sato <henrique.sato@scclouds.com.br>
Description
The KVM Agent has the
hypervisor.uri
configuration to define the connection with Libvirt; however, this property is ignored and a hardcoded value is used in many parts of the code.This PR intends to prioritize the
hypervisor.uri
property in Libvirt connections and use the hypervisor default URI only when this configuration is not defined.Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
I followed the same steps from
How did you try to break this feature...
and verified that the host was only using the URI defined in thehypervisor.uri
property.How did you try to break this feature and the system with this change?
hypervisor.uri
property to a host's agent.properties,hypervisor.uri=qemu:///session
for example;hypervisor.uri
property is defined, the agent is still using the hypervisor default URI in many connections;