-
Notifications
You must be signed in to change notification settings - Fork 37
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
support volume expansion #16
Comments
No strong feeling from me. But welcome contributions. |
I wonder if storing this information in etcd will affect the impact of the k8s cluster, if it is used in the actual production environment. etcd is generally the best memory in 8G, Too big or too small can easily cause performance degradation.I feel that my question is a bit redundant, but I still want to hear more professional opinions. |
If I want to contribute the code of expand volume, what should I do? |
You can follow the guide in below link to setup gerrit and push code. |
|
Try |
nice |
How often submitted code is generally evaluated |
I've left comment to your PR yesterday. |
thank you . i got it |
For a major feature, there's often non-trivial feed backs and change request to the original commit. |
I think mine is a secondary feature, haha. |
root@localhost:~/go/src/spdk-csi# git status Changes not staged for commit: I added functionality for volume expansion and performed unit tests. This indicate that the test passed? |
iSCSI: nvmf: |
Not sure of your question. Do you add volume expansion specific unit test? The test itself should verify the function. |
Yes, Can the above output prove that the function is feasible. i think it's ok, |
Honestly, it's hard for me to read the above output. |
{"jsonrpc":"2.0","id":9,"method":"bdev_lvol_resize","params":{"name":"adb8bfad-29ad-41da-b134-37c28bd8f6e9","size":1069547520}} Sorry, I didn't think carefully. The above may be the key information. |
This looks right. Of course, you should make sure the original size is not the same as resized. |
Do I have to add the e2e_test test case before submitting the code? |
Yes. |
OK |
I have a question to ask you, after the success of the volume extension, how to verify the success of it. I want to get the persistent volume size, but I can't find an interface in the framework to get the persistent volume resources. Is there any other way? |
What should I do if the submitted code conflicts? |
Fix the conflict and push again? |
The pulled code is the latest. When I submitted it for the first time, I found that the changed Id was the same. I deleted it and submitted it again. Although the submission was successful, the status on the web side showed a merge conflict. |
Is it because the change of the person who committed the code before me has not yet passed? |
You patch is not based on latest tip (95a1911). Pull and rebase again. |
Yes, thank you, it's resolved now. |
@lijhnihaoa , thanks for the patch. Will you change issue title to something like "support volume expansion" to match current scope. |
Is the feature of volume expansion available? I need it, even though give me some suggestion are welcome. |
https://review.spdk.io/gerrit/c/spdk/spdk-csi/+/17748 |
Hi,@lijhnihaoa are you still working on this? |
I don't have time recently, I have to take care of my newborn child and work.
发自我的小米
在 2023年10月24日 11:26,Xin Yang ***@***.***>写道:<br type="attributi
***@***.***<https://github.com/lijhnihaoa> are you still working on this?
―
Reply to this email directly, view it on GitHub<#16 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALYZYKHH4BQL35NXQFLZC2DYA4YPFAVCNFSM6AAAAAAQXW4HICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZWGQ2TONBSG4>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I would like to ask what you think about the high availability of CSI. For example, if SPDK and CSI-Node are restarted at the same time, how can they be restored to the state before the restart.
The text was updated successfully, but these errors were encountered: