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
add new property TuneFastDeviceClass #864
add new property TuneFastDeviceClass #864
Conversation
e1277e4
to
76d77ba
Compare
@jarrpa I ran |
@iamniting: changing LGTM is restricted to collaborators 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. |
I think we should make these changes in two commits first one for the move part and second one for add part. |
@jarrpa the ci test is failing at govet. need help there. |
@crombus since the implementation of |
Test failures are valid. Please rebase and resolve. Always run |
the PR is dependent on #912. rook 1.5.1. I'll rebase it. |
Not strictly required for a 4.7 feature, afaict, but would be good to have before feature freeze... |
/test ocs-operator-ci |
/test ocs-operator-bundle-e2e-aws |
1 similar comment
/test ocs-operator-bundle-e2e-aws |
move throttleStorageDevices func in cephcluster.go and add managed-premium as fastdeviceclass. modify test file according to the changes. Signed-off-by: crombus <pkundra@redhat.com>
add case for fasttune device Signed-off-by: crombus <pkundra@redhat.com>
Signed-off-by: crombus <pkundra@redhat.com>
/retest |
/test ocs-operator-ci |
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.
To my taste, the main commit (add new property TuneFastDeviceClass) does a bit too much. I would have recommended to split the refactoring (moving of function from reconcile.go
to cephcluster.go
, etc) into separat commits. But not blocking because of this.
The whole terminology with Tune[Fast|Slow]DeviceClass
is rather confusing or non-obvious, but I guess it is what it is.
For now the patch might be enough, but conceptually, I think we need the list of device types to tune for slow or fast types not to be just storage class names and hard code selection of provisioners in the throttle function but instead we should have the devices types be pairs of provisioner and storage class name.
Since this can be done in a follow-up cleanup PR, approving this one for now.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kesavanvt, 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. |
@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. |
A new property TuneFastDeviceClass was added to the Storage Cluster spec in PR red-hat-storage#864. This commit adds the generated changes for that. Signed-off-by: Raghavendra Talur <raghavendra.talur@gmail.com>
A new property TuneFastDeviceClass was added to the Storage Cluster spec in PR red-hat-storage#864. This commit adds the generated changes for that. Signed-off-by: Raghavendra Talur <raghavendra.talur@gmail.com>
A new property TuneFastDeviceClass was added to the Storage Cluster spec in PR red-hat-storage#864. This commit adds the generated changes for that. Signed-off-by: Raghavendra Talur <raghavendra.talur@gmail.com>
/cherry-pick release-4.6 |
@crombus: #864 failed to apply on top of branch "release-4.6":
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. |
@crombus https://bugzilla.redhat.com/show_bug.cgi?id=1909793 still doesn't have all the acks. Pls do not merge it into 4.6 yet. |
@agarwal-mudit this feature is already in 4.7. |
Ok, then lets not backport it to 4.6 |
Signed-off-by: crombus pkundra@redhat.com