-
Notifications
You must be signed in to change notification settings - Fork 121
Performance profile render command integration #324
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -61,7 +61,8 @@ spec: | |
| - machineConfigLabels: | ||
| machineconfiguration.openshift.io/role: worker-cnf | ||
| operand: | ||
| debug: false | ||
| tunedConfig: | ||
| reapply_sysctl: null | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You tell me :) This is the value the test is seeing, I only updated the expected value for it to pass as PAO does not care about this part.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I might tell you, but I have no idea about the test you're talking about. :) I guess it is
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is the expected value of Tuned when PerfProfile is processed by the render stage. If you check couple of lines above this, we mostly care about the generated tuned profile. The rest is just what NTO structures serialize to by default. |
||
| priority: 20 | ||
| profile: openshift-node-performance-manual | ||
| status: {} | ||
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.
Should we make the make target more specific as in
cluster-node-tuning-operator/Makefile
Line 202 in 1316041
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.
I was wondering if we can have more tests that are e2e in nature, but do not require a running cluster.. but the name is not important obviously.
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.
if we are planing to add a render lane in openshift/release then it should correspond to the make target
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.
@MarSik we currently have https://github.com/openshift/cluster-node-tuning-operator/blob/master/hack/run-render-command-functests.sh under this repo. If this target comes to replace the invocation of this script like we did in PAO then we can remove the script (although the script contains some additional decorations)