rbd: use volumeattributesclass feature implement rbd volume qos#6160
rbd: use volumeattributesclass feature implement rbd volume qos#6160YiteGu wants to merge 11 commits intoceph:develfrom
Conversation
b78efe5 to
36c1c2f
Compare
c1e4f0a to
dffa21e
Compare
nixpanic
left a comment
There was a problem hiding this comment.
This is a user visible change. Put a note in PendingReleaseNotes.md for this too. Maybe add a note in the main README.md for support of this as well, update other documentation?
|
This pull request now has conflicts with the target branch. Could you please resolve conflicts and force push the corrected changes? 🙏 |
cb885ba to
a8df95a
Compare
|
This pull request now has conflicts with the target branch. Could you please resolve conflicts and force push the corrected changes? 🙏 |
43fa44e to
1a4ade8
Compare
f7b6685 to
e786b28
Compare
nixpanic
left a comment
There was a problem hiding this comment.
Two minor things that caught the eye of Claude Code, and look like good recommendations to me.
|
/test ci/centos/mini-e2e/k8s-1.34 |
e786b28 to
650a107
Compare
nixpanic
left a comment
There was a problem hiding this comment.
Another round of review (now completed by me, not Claude).
These are the only changes I would like to see, everything else looks good to me. Thanks!
b2d68cb to
a79ce62
Compare
19d57ab to
b6400da
Compare
I checked the StorageClass's secret and found no problems. |
Are there any other investigation approaches? |
|
In Lines 136 to 146 in 9af58c4 |
b6400da to
f838c0b
Compare
|
/test ci/centos/mini-e2e/k8s-1.34/rbd |
f838c0b to
c059c35
Compare
|
@YiteGu , I've updated the commit e2e: add e2e test for rbd volume volumeattributesclass to include the new parameters. With these changes it should all be good 🤞 |
|
/test ci/centos/mini-e2e/k8s-1.34/rbd |
|
/test ci/centos/mini-e2e/k8s-1.33/rbd |
Nice, I've already returned home from the company, and I'll continue working tomorrow. |
|
@nixpanic @iPraveenParihar e2e test successful, I will execu a final push, remove the diagnostic log I had added. |
c059c35 to
137bf95
Compare
1. Create a VolumeAttributesClass with a QoS parameter. Create a PVC with a VolumeAttributesClassName parameter. Verify the QoS results of the RBD image. 2. Modify the VolumeAttributesClassName of the PVC and verify the change in the QoS of the RBD image. 3. Create a VolumeAttributesClass that supports capacity-based QoS and verify the QoS results of the RBD image. Create a cloned volume of the PVC and verify the QoS results of the cloned volume. Signed-off-by: Yite Gu <guyite@bytedance.com> Co-authored-by: Niels de Vos <ndevos@ibm.com>
The addition of a new op caused the tryAcquire function to become too complex and fail CI checks. The tryAcquire function implementation was refactored, and the conflictMatrix design was introduced, which greatly reduced the complexity. Signed-off-by: Yite Gu <guyite@bytedance.com>
storageclass is no longer used as the qos parameters carrier for RBD volumes; these parameters are now defined in volumeattribetesclass. Signed-off-by: Yite Gu <guyite@bytedance.com>
Signed-off-by: Yite Gu <guyite@bytedance.com>
Signed-off-by: Yite Gu <guyite@bytedance.com>
Signed-off-by: Yite Gu <guyite@bytedance.com>
Signed-off-by: Yite Gu <guyite@bytedance.com>
Signed-off-by: Yite Gu <guyite@bytedance.com>
Signed-off-by: Yite Gu <guyite@bytedance.com>
137bf95 to
ff95af7
Compare
|
/test ci/centos/mini-e2e/k8s-1.34/rbd |
|
/test ci/centos/mini-e2e/k8s-1.33/rbd |
Describe what this PR does
volumeAttributesClassNamewhen defining the PVC. For example:volumeAttributesClassNameparameter of an existing PVC.ref: https://kubernetes.io/docs/concepts/storage/volume-attributes-classes/
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!)