io-hog working configuration #488
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
config.yaml small nits small nits
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: tsebastiani The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| stressng: | ||
| plugin: quay.io/arcalot/arcaflow-plugin-stressng:0.3.1 | ||
| step: workload | ||
| input: |
There was a problem hiding this comment.
We need to update with the recent changes similar to https://github.com/redhat-chaos/krkn/blob/main/scenarios/arcaflow/cpu-hog/sub-workflow.yaml#L69.
There was a problem hiding this comment.
Hey Ravi, seems to me that the structure is already exactly the same as the other two arcaflow scenarios (including the recent changes):
This is the diff between io-hog and cpu-hog.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It works instantiating a privileged container mounting the hostPath (seems to be the only solution to r/w on the node filesystem). It works on Vanilla OCP (4.14.0-0.nightly-2023-09-07-211548) needs to be tested on prow.