-
Couldn't load subscription status.
- Fork 580
rbd: support set qos max limit for rbdVol #5501
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
Conversation
42f1a7d to
b5d86ed
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.
@YiteGu as we are adding lot of changes to it in think we need to do the basic E2E testing, can you please update e2e test for nbd driver to test IOPS and make sure everything works
Get |
b5d86ed to
8f08fd8
Compare
rbdVol already support qos base on capacity, in reality, performance doesn't always scale linearly with capacity. To address this, we've added max configurations to allow users to set a maximum QoS limit for a volume. Once the maximum limit is reached, further capacity increases will no longer improve performance. These configurations as below: - maxIops - maxReadIops - maxWriteIops - maxBps - maxReadBps - maxWriteBps Signed-off-by: Yite Gu <[email protected]>
8f08fd8 to
92ac16f
Compare
|
/test ci/centos/mini-e2e/k8s-1.31 |
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!
|
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at f0a905f |
rbdVol already support qos base on capacity, in reality, performance doesn't always scale linearly with capacity. To address this, we've added max configurations to allow users to set a maximum QoS limit for a volume. Once the maximum limit is reached, further capacity increases will no longer improve performance. These configurations as below:
Describe what this PR does
Provide some context for the reviewer
Is there anything that requires special attention
Do you have any questions?
Is the change backward compatible?
Are there concerns around backward compatibility?
Provide any external context for the change, if any.
For example:
Related issues
Mention any github issues relevant to this PR. Adding below line
will help to auto close the issue once the PR is merged.
Fixes: #issue_number
Future concerns
List items that are not part of the PR and do not impact it's
functionality, but are work items that can be taken up subsequently.
Checklist:
guidelines in the developer
guide.
Request
notes
updated with breaking and/or notable changes for the next major release.
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>: retest the<job-name>after unrelatedfailure (please report the failure too!)