-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OSDOCS-930 - Include section on the OpenStack Manila CSI Driver #22199
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
The preview will be available shortly at: |
139530e
to
e80aba9
Compare
@duanwei33 PTAL? |
ec53882
to
f2c78a6
Compare
@bobfuru Sorry for the delay, I think there is still some update for this feature, I list some items not align with our test:
I can provide env with manila operator if you needed. |
Hi Bob, |
43674a2
to
ea21b50
Compare
Hi Wei, Thanks for the feedback. See my inline comments below...
That makes sense. Because I didn't have CSI Manila Operator in OLM, I was mostly guessing. :)
I added a section for instructions about installing ManilaDriver (or whatever name it will be called). So the Operator doesn't deploy the driver? I thought that's one of the features of CSI Operators? I'm not sure what the steps are to do this, so please fill in/comment on them as you have more details.
Fixed.
Because we have console instructions, I'm inclined to keep those here, along with CLI.
Fixed!
This came from a BZ enhancement for local storage Operator install, so I thought it would also be useful context here. If you think it's incorrect, please let me know and I'll remove.
Yes, that would be most helpful, thanks!
As of now, our Docs freeze date is June 8, but I know GA is now July 9, so we will probably have additional time for this doc to be finished with QE review. Or is June 8 even possible for you? |
Perfect, thank you, @duanwei33 !! I did what I could for now based on the info I have (and no test env). Appreciate you looking now and again next week!! |
@jeana-redhat PTAL for clarity, typos, links, etc. Thanks! |
ea21b50
to
99466b4
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.
Some suggestions, mostly ISG or minimalism related. Anything I asked as a question is something I'm uncertain about just because I'm still getting up to speed - if the question is irrelevant feel free to just ignore rather than explaining so you don't get caught up in that.
storage/container_storage_interface/persistent-storage-csi-manila.adoc
Outdated
Show resolved
Hide resolved
storage/container_storage_interface/persistent-storage-csi-manila.adoc
Outdated
Show resolved
Hide resolved
modules/persistent-storage-csi-manila-dynamic-provisioning.adoc
Outdated
Show resolved
Hide resolved
modules/persistent-storage-csi-manila-dynamic-provisioning.adoc
Outdated
Show resolved
Hide resolved
modules/persistent-storage-csi-manila-dynamic-provisioning.adoc
Outdated
Show resolved
Hide resolved
modules/persistent-storage-csi-manila-dynamic-provisioning.adoc
Outdated
Show resolved
Hide resolved
modules/persistent-storage-csi-manila-dynamic-provisioning.adoc
Outdated
Show resolved
Hide resolved
@jeana-redhat, I don't usually drive-by comment, but this is impressive peer review work and I wanted to say so! |
05c06ba
to
a613756
Compare
storage/container_storage_interface/persistent-storage-csi-manila.adoc
Outdated
Show resolved
Hide resolved
ab01b7b
to
46fe558
Compare
Done. |
46fe558
to
114caa6
Compare
114caa6
to
a024f09
Compare
modules/persistent-storage-csi-manila-dynamic-provisioning.adoc
Outdated
Show resolved
Hide resolved
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've posted remarks on a few nits or small issues, but this looks good and is very close to merge IMO.
But I think manila-csi should be included in the section dedicated to dynamic provisioning as well [1].
It could appear in the "Available dynamic provisioning plug-ins" table right after OpenStack cinder. The provisioner plug-in name is "manila.csi.openstack.org". Notes could just be a link back to the manila-csi docs that you are currently writing. There should be a "RHOSP Manila CSI object definition" section that says the Manila CSI storage classes are automatically created when the Operator and Driver are installed as covered in [link](to this section you are writing now).
a3a9b02
to
58d48a4
Compare
Great idea! I've added CSI Manila to the plug-ins table and added a section for the object definition. As you said, this is redundant but conforms to how we've laid out the rest of the page. Preview of this addition here: https://osdocs-930-manila--ocpdocs.netlify.app/openshift-enterprise/latest/storage/dynamic-provisioning.html#available-plug-ins_dynamic-provisioning |
58d48a4
to
91d64af
Compare
91d64af
to
57961f1
Compare
LGTM, Bob. Thanks for your work on this one! |
/cherrypick enterprise-4.5 |
@bobfuru: new pull request created: #23391 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
xrefs aren't allowed in modules: $ grep -A1 'You must not include xrefs' modules/mod-docs-ocp-conventions.adoc You must not include xrefs in modules or create an xref to a module. You can only use xrefs to link from one assembly to another. And we can't move this module out into an assembly directory, because it is consumed from two places: $ git --no-pager grep dynamic-provisioning-available-plugins post_installation_configuration/storage-configuration.adoc:include::modules/dynamic-provisioning-available-plugins.adoc[leveloffset=+3] storage/dynamic-provisioning.adoc:include::modules/dynamic-provisioning-available-plugins.adoc[leveloffset=+1] We could: a. Trim down post_installation_configuration to just xref the storage assembly, instead of duping so much of it's content via modules. b. Drop the module and instead inline (some of) it with copy/paste in both assemblies. c. Remove the xref. With this commit, I'm going with (c), removing the xref which was added in 57961f1 ([STOR] Include section on the OpenStack Manila CSI Driver, 2020-05-12, openshift#22199).
xrefs aren't allowed in modules: $ grep -A1 'You must not include xrefs' modules/mod-docs-ocp-conventions.adoc You must not include xrefs in modules or create an xref to a module. You can only use xrefs to link from one assembly to another. And we can't move this module out into an assembly directory, because it is consumed from two places: $ git --no-pager grep dynamic-provisioning-available-plugins post_installation_configuration/storage-configuration.adoc:include::modules/dynamic-provisioning-available-plugins.adoc[leveloffset=+3] storage/dynamic-provisioning.adoc:include::modules/dynamic-provisioning-available-plugins.adoc[leveloffset=+1] We could: a. Trim down post_installation_configuration to just xref the storage assembly, instead of duping so much of it's content via modules. b. Drop the module and instead inline (some of) it with copy/paste in both assemblies. c. Remove the xref. With this commit, I'm going with (c), removing the xref which was added in 57961f1 ([STOR] Include section on the OpenStack Manila CSI Driver, 2020-05-12, openshift#22199).
xrefs aren't allowed in modules: $ grep -A1 'You must not include xrefs' modules/mod-docs-ocp-conventions.adoc You must not include xrefs in modules or create an xref to a module. You can only use xrefs to link from one assembly to another. And we can't move this module out into an assembly directory, because it is consumed from two places: $ git --no-pager grep dynamic-provisioning-available-plugins post_installation_configuration/storage-configuration.adoc:include::modules/dynamic-provisioning-available-plugins.adoc[leveloffset=+3] storage/dynamic-provisioning.adoc:include::modules/dynamic-provisioning-available-plugins.adoc[leveloffset=+1] We could: a. Trim down post_installation_configuration to just xref the storage assembly, instead of duping so much of it's content via modules. b. Drop the module and instead inline (some of) it with copy/paste in both assemblies. c. Remove the xref. With this commit, I'm going with (c), removing the xref which was added in 57961f1 ([STOR] Include section on the OpenStack Manila CSI Driver, 2020-05-12, openshift#22199).
Work being tracked in OSDOCS-930 and OSDOCS-1117.
Storage -> Using CSI -> Using CSI OpenStack Manila
Preview link: https://osdocs-930-manila--ocpdocs.netlify.app/openshift-enterprise/latest/storage/container_storage_interface/persistent-storage-csi-manila.html