Doc: Additional examples for cluster storage pools using remote drivers#13819
Doc: Additional examples for cluster storage pools using remote drivers#13819tomponline merged 1 commit intocanonical:mainfrom
Conversation
|
Heads up @ru-fu - the "Documentation" label was applied to this issue. |
589cb65 to
866f471
Compare
| Storage pool my-remote-pool created | ||
| ``` | ||
|
|
||
| Create a second storage pool `my-remote-pool2` using the Dell PowerFlex driver in SDC mode using the pool `sp1` in protection domain `pd1`: |
There was a problem hiding this comment.
| Create a second storage pool `my-remote-pool2` using the Dell PowerFlex driver in SDC mode using the pool `sp1` in protection domain `pd1`: | |
| The following commands create a second storage pool `my-remote-pool2` using the Dell PowerFlex driver in SDC mode using the pool `sp1` in protection domain `pd1`: |
There was a problem hiding this comment.
We could also be consistent with the examples in the other section and change all three examples to use "Create/Set up a pool ..." instead of "These commands create/set up ...".
There was a problem hiding this comment.
You mean not using the {terminal} block? I was thinking the same but decided against as it shows very cleanly how to to run the three --target commands one after another and then finally the actual pool creation command without too much text in between.
Or should we just indent the commands (still grouped together) like in the other examples and prevent using the {terminal}?
There was a problem hiding this comment.
No sorry, I was referring to the wording only.
In the other examples section, we have instructions like "Create a directory pool" or "Use the existing directory", while here we are using "The following series of commands sets up" and "The following commands create".
So there's a bit of an inconsistency, but I don't see a problem with that.
There was a problem hiding this comment.
Ah ok I see. Added a PR to address the consistent naming #13827
This provides additional examples when to define (non-)member specific config keys and how to create cluster storage pools backed by remote storage drivers. Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
866f471 to
ae60464
Compare
A follow up on #13819 that addresses #13819 (comment).
This provides additional examples when to define (non-)member specific config keys and
how to create cluster storage pools backed by remote storage drivers.