Heketi on OpenShift#5364
Heketi on OpenShift#5364gaurav-nelson merged 1 commit intoopenshift:masterfrom gaurav-nelson:heketiOnOCP
Conversation
There was a problem hiding this comment.
Didn't see /usr/share/heketi/toplogy-sample.json, may because I just have heketi-client RPM package installed. Should hint customer here.
There was a problem hiding this comment.
Thanks @wkshi I have updated the docs to include more details around this one by adding following note:
Depending upon your method of installation this file may not exist. If its missing, manually create the *_toplogy-sample.json_* file, as shown in the following example.
There was a problem hiding this comment.
# heketi-cli topology load --json=topology.json
Error: Unable to open config file
The topology.json does existing, may some steps missing.
There was a problem hiding this comment.
There is a extra "," here. Remove it then "heketi-cli topology load --json=toplogy-sample.json" could works.
There was a problem hiding this comment.
I removed the extra "," from line 179, in the latest commit and also fixed it in the gluster dynamic example.
|
@openshift/team-documentation PTAL |
There was a problem hiding this comment.
Assumes you have familiarity ??
|
[rev_history] |
|
Thanks @mburke5678 I have added rev history as well. Are you done with peer review? |
There was a problem hiding this comment.
Does EmptyDir need mark up? i looked quickly at the docs and there doesn't seem to be consistent usage. Some EmptyDir, some EmptyDir and some with no mark up.
There was a problem hiding this comment.
Kubernetes uses emptyDir maybe we should use the same markup. I'll check this in our docs and submit a new PR with the changes.
There was a problem hiding this comment.
Thanks @mburke5678 addressed this in #6084
There was a problem hiding this comment.
Run the heketi-cli command to load the topology of your environment (??)
There was a problem hiding this comment.
I think I will just go with Run the following command to load the topology of your environment:
There was a problem hiding this comment.
Where the last storageclass is talking about a storage class object, should this be two words?
Or, "...skip the following storage class creation steps..."
Or StorageClass like in the "Dynamic Provisioning and Creating Storage Classes" chapter?
There does not seem to be a consistent way that we are using this term.
There was a problem hiding this comment.
I think we should use StorageClass when we talk about specific object and use storage class in general.
|
@gaurav-nelson A few more nits and an open question on how we present the term storage class. LGTM |
For https://bugzilla.redhat.com/show_bug.cgi?id=1436101