-
Notifications
You must be signed in to change notification settings - Fork 586
doc: clarifiy NVMe-oF design a little more #5422
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
After collecting feedback, it has been confirmed that the Ceph-CSI/RBD component can be used to create the RBD-images. The NVMe Subsystems may not have been pre-created, so Ceph-CSI should verify if the subsystem exists, and create it if needed. Note: also corrected some of the markdown-linter complaints. Signed-off-by: Niels de Vos <ndevos@ibm.com>
770f9d5 to
bffdf3f
Compare
| - NVMe-oF Gateway Group (hostname, could be a Kubernetes Service) | ||
| - NVMe subsystem name | ||
| - if given, the name for the subsystem should be used | ||
| - if not given, base the name on the owner (Kubernetes Namespace) |
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.
can we make this as mandatory in the SC so that we dont need to worry about it in other CO? or add a comment in other CO its a mandatory field
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.
I think it can be optional in a StorageClass, as we can detect the owner in Kubernetes clusters. For other platforms (Docker Swarm, Hashicorp Nomad, ..) it should be mandatory. I think it is sufficiently clear in the document?
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.
That last part that its mandatory for other CO was not mentioned, as this also need more PR for open questions, it can be addressed later
|
@Mergifyio queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at d97f3cf |
After collecting feedback, it has been confirmed that the Ceph-CSI/RBD
component can be used to create the RBD-images.
The NVMe Subsystems may not have been pre-created, so Ceph-CSI should
verify if the subsystem exists, and create it if needed.