-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Extract the IO_URING configuration into the agent.properties #6253
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
Conversation
When using advanced virtualization the IO Driver is not supported. The admin will decide if want to enable/disable this configuration from agent.properties file. The default value is true
|
@blueorangutan package |
|
@nvazquez 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 3146 |
|
@blueorangutan test |
weizhouapache
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.
code lgtm
GabrielBrascher
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.
Thanks for the PR @slavkap!
Code LGTM.
Pearl1594
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.
Code LGTM
|
@blueorangutan test |
|
@Pearl1594 a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
wido
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.
Code looks good!
nvazquez
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.
LGTM - manually tested OK
|
Trillian test result (tid-3886)
|
…6253) When using advanced virtualization the IO Driver is not supported. The admin will decide if want to enable/disable this configuration from agent.properties file. The default value is true (cherry picked from commit 42a92dc) Signed-off-by: Rohit Yadav <[email protected]>
…6253) When using advanced virtualization the IO Driver is not supported. The admin will decide if want to enable/disable this configuration from agent.properties file. The default value is true (cherry picked from commit 42a92dc) Signed-off-by: Rohit Yadav <[email protected]>
…6253) When using advanced virtualization the IO Driver is not supported. The admin will decide if want to enable/disable this configuration from agent.properties file. The default value is true (cherry picked from commit 42a92dc) Signed-off-by: Rohit Yadav <[email protected]>
…6253) When using advanced virtualization the IO Driver is not supported. The admin will decide if want to enable/disable this configuration from agent.properties file. The default value is true (cherry picked from commit 42a92dc) Signed-off-by: Rohit Yadav <[email protected]>
…6253) When using advanced virtualization the IO Driver is not supported. The admin will decide if want to enable/disable this configuration from agent.properties file. The default value is true (cherry picked from commit 42a92dc) Signed-off-by: Rohit Yadav <[email protected]>
…6253) When using advanced virtualization the IO Driver is not supported. The admin will decide if want to enable/disable this configuration from agent.properties file. The default value is true (cherry picked from commit 42a92dc) Signed-off-by: Rohit Yadav <[email protected]>
|
@slavkap Nice feature, but I want to voice my concern over the default value of "true". This will out of the box break Cloudstack upgrades as well as new installations on many distributions which do not ship a io_uring capable qemu-kvm. |
|
Thanks, @NuxRo, for your comment! You're right, but the reason to set the default value to |
|
@NuxRo what would you advise as a solution? If the default value is false, administrators may be aware to update all their KVM hosts if they want to enable back IO uring, right? (in case it was supported before the upgrade) |
|
@slavkap I get it, it's a sensitive lose-lose situation. The only option we have to somewhat salvage this without hurting anyone is to default to false in the agent.properties so at least new installations work out of the box. Upgrades will still break unless the admins are aware of this change and amend their config file. On the other hand io_uring is very new and I doubt there are many users. The EL8 and EL9 user bases are probably much bigger than them. |
|
@NuxRo @GabrielBrascher @wido |
|
2cents - not all supported distros have io_uring available, having the feature enabled by default breaks the general ACS+kvm deployment. If this is a relatively new feature this should ship as (a) disabled by default and to be enabled on per-host basis via agent.properties by the admin, or (b) be enabled by default based on capabilities discovered by the host/agent and still enabled/disabled override by the agent.properties. I'm not sure if (b) is possible but that would be a good compromise to support both new, existing/upgraded env which may be using io_uring. |
|
@rohityadavcloud good. fyi, it looks io_uring will be supported since RHEL 9.1 |
|
Makes sense @weizhouapache, if (b) is not feasible then we should not enable io_uring by default and let it be overriden via agent.properties and document in release notes for 4.17 that on upgrade people using it need to update it on per-host basis. |
…6253) When using advanced virtualization the IO Driver is not supported. The admin will decide if want to enable/disable this configuration from agent.properties file. The default value is true
* Extract the IO_URING configuration into the agent.properties (apache#6253) When using advanced virtualization the IO Driver is not supported. The admin will decide if want to enable/disable this configuration from agent.properties file. The default value is true * kvm: truncate vnc password to 8 chars (apache#6244) This PR truncates the vnc password of kvm vms to 8 chars to support latest versions of libvirt. * merge fix Signed-off-by: Abhishek Kumar <[email protected]> * [KVM] Enable IOURING only when it is available on the host (apache#6399) * [KVM] Disable IOURING by default on agents * Refactor * Remove agent property for iouring * Restore property * Refactor suse check and enable on ubuntu by default * Refactor irrespective of guest OS * Improvement * Logs and new path * Refactor condition to enable iouring * Improve condition * Refactor property check * Improvement * Doc comment * Extend comment * Move method * Add log * [KVM] Fix VM migration error due to VNC password on libvirt limiting versions (apache#6404) * [KVM] Fix VM migration error due to VNC password on libvirt limiting versions * Fix passwd value * Simplify implementation Co-authored-by: slavkap <[email protected]> Co-authored-by: Wei Zhou <[email protected]> Co-authored-by: Nicolas Vazquez <[email protected]>
Description
This PR fixes #6252
When using advanced virtualization, the IO Driver is not supported. The admins will decide if they want to enable/disable this configuration from
agent.propertiesfile. It's enabled by defaultTypes of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity