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
cephcluster: tune devices according to the deviceType #944
cephcluster: tune devices according to the deviceType #944
Conversation
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.
Can you please add to the commit message and the PR description explanations what problem this PR is trying to solve?
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 I get it right, the deviceType can be set in the storageDeviceSet in the storage cluster yaml input. If this is set, this can override the otherwise potentially wrongly detected device type. I.e. it has to be set explicitly by the admin or whoever is crafting the input (GUI..). This PR is taking this specified device type and propagates corresponding OSD tuning settings to rook, in addition to (and overriding) the settings of PR #864 that enabled tuning settings based on known storage class types for backend disks. To be honest the code is getting more and more confusing. I suggest rebasing these changes on top of the refactoring of the tuning code in #946 which will make the resulting code more obvious and this change even shorter.
I further suggest to add this new code to the throttleStorageDevices()
function (called checkTuneStorageDevices
after the refactor), instead of directly to the ensureCephCluster()
function.
80e2194
to
b0e721c
Compare
Done the changes on top of the refactor code. I need suggestion to make it little better. |
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 rebasing!
See inline request/suggestions to make this even better / more minimal.
Thanks!
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.
oh, and if you would update the commit message a bit explaining that this is not about auto-detected hdd types, but about hdd types that explicitly configured by the admin (or gui?) in the deviceset section in the storagecluster yaml.
b2b2ad1
to
f7b9fa4
Compare
f7b9fa4
to
6c7e711
Compare
/test ci/prow/ocs-operator-ci |
@crombus: The specified target(s) for
Use In response to this:
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. |
tune devices according to the deviceType added by the admin in storagecluster.yaml and modify the testcase Signed-off-by: crombus <pkundra@redhat.com>
check for that deviceType is considered as priority Signed-off-by: crombus <pkundra@redhat.com>
6c7e711
to
ada7e14
Compare
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
Thanks for the updates!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: iamniting, obnoxxx The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Please review the full test history for this PR and help us cut down flakes. |
Now the bot has retriggered the ci runs, but before, ocs-operator-ci was failing in a strange way (already the second time on this PR): First, it is failing in
but before that, there is a strange PASS:
Is this expected? 🤔 |
now ocs-operator-ci has passed - strange flake... |
@crombus: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
/retest Please review the full test history for this PR and help us cut down flakes. |
Signed-off-by: crombus pkundra@redhat.com