openshift-docs icon indicating copy to clipboard operation
openshift-docs copied to clipboard

Updates for BZ2093247 - adding details of workload partitioning

Open rohennes opened this issue 3 years ago • 2 comments

BZ#2093247: Adding some detail that workload partitioning can only be applied at install time, cannot be disabled post-install, but can be reconfigured post-install.

Version(s): 4.9+

Issue: https://bugzilla.redhat.com/show_bug.cgi?id=2093247

Link to docs preview: http://file.emea.redhat.com/rohennes/BZ2093247/scalability_and_performance/sno-du-enabling-workload-partitioning-on-single-node-openshift.html#sno-du-enabling-workload-partitioning_sno-du-enabling-workload-partitioning-on-single-node-openshift

rohennes avatar Jul 15 '22 15:07 rohennes

The contents of /etc/crio/crio.conf.d/01-workload-partitioning is not correct, the line 59 should be: [crio.runtime.workloads.management.resources] cpushares = 0 CPUs = "0-1, 52-53"

I have tested, only using this format can lead to workloads resources(cpu) take effect.

lyman9966 avatar Aug 17 '22 08:08 lyman9966

Hi @lyman9966,

Should the original text: [crio.runtime.workloads.management] activation_annotation = "target.workload.openshift.io/management" annotation_prefix = "resources.workload.openshift.io" resources = { "cpushares" = 0, "cpuset" = "0-1,52-53" }

Be changed to this: [crio.runtime.workloads.management] activation_annotation = "target.workload.openshift.io/management" annotation_prefix = "resources.workload.openshift.io"

[crio.runtime.workloads.management.resources] cpushares = 0 CPUs = "0-1, 52-53"

Or perhaps can you send me the actual file so I can see it exactly? Thank you!

rohennes avatar Aug 17 '22 10:08 rohennes

yeah, just delete the blank line,like: [crio.runtime.workloads.management] activation_annotation = "target.workload.openshift.io/management" annotation_prefix = "resources.workload.openshift.io" [crio.runtime.workloads.management.resources] cpushares = 0 CPUs = "0-1, 52-53"

lyman9966 avatar Aug 19 '22 09:08 lyman9966

And line 37 should changed to: source: data:text/plain;charset=utf-8;base64,W2NyaW8ucnVudGltZS53b3JrbG9hZHMubWFuYWdlbWVudF0KYWN0aXZhdGlvbl9hbm5vdGF0aW9uID0gInRhcmdldC53b3JrbG9hZC5vcGVuc2hpZnQuaW8vbWFuYWdlbWVudCIKYW5ub3RhdGlvbl9wcmVmaXggPSAicmVzb3VyY2VzLndvcmtsb2FkLm9wZW5zaGlmdC5pbyIKW2NyaW8ucnVudGltZS53b3JrbG9hZHMubWFuYWdlbWVudC5yZXNvdXJjZXNdCmNwdXNoYXJlcyA9IDAKQ1BVcyA9ICIwLTEsIDUyLTUzIgo=

lyman9966 avatar Aug 19 '22 10:08 lyman9966

/lgtm

lyman9966 avatar Aug 19 '22 10:08 lyman9966

New changes are detected. LGTM label has been removed.

openshift-ci[bot] avatar Aug 19 '22 10:08 openshift-ci[bot]

@rohennes A couple of tiny nits. Otherwise LGTM

mburke5678 avatar Aug 19 '22 13:08 mburke5678

/cherrypick enterprise-4.9

mburke5678 avatar Aug 19 '22 14:08 mburke5678

@mburke5678: new pull request created: #49389

In response to this:

/cherrypick enterprise-4.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/cherrypick enterprise-4.10

mburke5678 avatar Aug 19 '22 14:08 mburke5678

/cherrypick enterprise-4.11

mburke5678 avatar Aug 19 '22 14:08 mburke5678

/cherrypick enterprise-4.12

mburke5678 avatar Aug 19 '22 14:08 mburke5678

@mburke5678: new pull request created: #49390

In response to this:

/cherrypick enterprise-4.10

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@mburke5678: new pull request created: #49391

In response to this:

/cherrypick enterprise-4.11

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@mburke5678: new pull request created: #49392

In response to this:

/cherrypick enterprise-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.