-
Notifications
You must be signed in to change notification settings - Fork 591
nvmeof: add rados ns ability #5866
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
8bc3c9e to
86c2c5d
Compare
nixpanic
left a comment
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, but please check the inline comment for improved usability and coding guidelines.
86c2c5d to
388fae0
Compare
67e64c0 to
bdd2622
Compare
Madhu-1
left a comment
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.
small nit
add rados ns ability to nvmeof csi driver. Signed-off-by: gadi-didi <[email protected]>
bdd2622 to
cfb02e2
Compare
Merge Queue Status✅ The pull request has been merged at cfb02e2 This pull request spent 34 minutes 9 seconds in the queue, including 33 minutes 56 seconds running CI. Required conditions to merge
|
Add RADOS namespace ability to nvmeof csi driver.
RADOS namespace support was added to nvmeof GW project.
RADOS namespace option in create volume step is added.
Is there anything that requires special attention
It is known the ceph-csi instance (deployment) is working with only 1 RADOS namespace. And can be more than 1 deployment on same Ceph cluster. Each of deployment has different rados ns.
RADOS namespace value is defined in rbd config-map, in that way, the nvmeof controller fetch the value from the rbd response,
and then calls to create nvmeof namespace later.
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!)