stress: add field to set the oom score

[YangKeao]

Signed-off-by: YangKeao yangkeao@chunibyo.icu

What problem does this PR solve?

#3069, but still need to modify the document after this PR merged.

What's changed and how it works?

Add a new field to represent the oom_score_adj value of the mem stress process. The chaos-daemon will use choom to execute the process and set the oom_score_adj. If this value is set to -1000, the oom killer will always kill the target container.

Related changes

• Need to update chaos-mesh/website
• Need to update Dashboard UI

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• FingerLeader
• cwen0

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[codecov]

Codecov Report

Merging #3070 (41ad5c6) into master (98931bb) will decrease coverage by 0.22%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #3070      +/-   ##
==========================================
- Coverage   38.20%   37.97%   -0.23%     
==========================================
  Files         105      105              
  Lines        9098     9108      +10     
==========================================
- Hits         3476     3459      -17     
- Misses       5315     5340      +25     
- Partials      307      309       +2     

Impacted Files	Coverage Δ
pkg/bpm/bpm.go	55.00% <0.00%> (-0.77%)	⬇️
pkg/bpm/build_linux.go	32.65% <0.00%> (-2.91%)	⬇️
pkg/chaosdaemon/stress_server_linux.go	0.00% <0.00%> (ø)
.../workflow/controllers/workflow_entry_reconciler.go	46.03% <0.00%> (-9.00%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 98931bb...41ad5c6. Read the comment docs.

[FingerLeader]

Why use int64 here? I found that everything else uses int except for proto.

[YangKeao]

Because the size of int depends on the implementation but is not part of the go language, the gRPC only allows using int32 or int64.

But anyway, I should use int32 here. I have submitted a commit to turn it into int32.

[FingerLeader]

LGTM!

[cwen0]

@YangKeao Can you fix CI first?

[YangKeao]

@YangKeao Can you fix CI first?

Fixed.

[cwen0]

LGTM @YangKeao Remember to create an issue to trace the implementation of this feature on chaos dashboard.

[cwen0]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: a9accf2

[ti-chi-bot]

@YangKeao: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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 ti-community-infra/tichi repository.