Various updates to storage docs #411
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -31,19 +31,21 @@ juju storage volume list | |||
|
|
|||
| As previously mentioned, a charm which requires storage will automatically allocate the default storage (unit filesystem) by default. It is possible to instead specify the storage to be used when the service is deployed, using constraints. | |||
|
|
|||
| The constraints can specify the type/pool and size of the storage required. | |||
| The constraints can specify the type/pool and size, and optionally a count, of the storage required. | |||
There was a problem hiding this comment.
From what I have seen, type/pool and size have reasonable defaults as well. So, they could be "optionally" specified as well :)
There was a problem hiding this comment.
will remove "optionally"
| location: /srv/data | ||
| ``` | ||
|
|
||
| Here the charm is asking for storage it is calling 'data', and it further defines a type and location. It is possible to specify as many entries as desired for storage, and all of the related keys are optional. | ||
| Here the charm is asking for storage it is calling 'data', and it further defines a type and location. It is possible to specify as many entries as desired for storage, and all but the 'type' key are optional. The 'type' attribute specifies the type of the storage: filesystem or block (i.e. block device/disk). The 'minimum-size' attribute specifies the minimum size of the store, overriding the default of 1G if the user does not specify a size. The location specifies the path at which to mount filesystem-type storage. The 'read-only' and 'shared' attributes are currently not handled. Support will be added in a future version of Juju. |
There was a problem hiding this comment.
instead of 1G, can we say either 1GiB or 1GB (I can't recall which OTTOMH) just to be 100% explicit. or does 1G mean the same as 1GB
There was a problem hiding this comment.
We define 1G to be 1GiB. I've changed instances of 1G in descriptions to 1GiB, but left as 1G in the example CLI invocations.
|
Excellent. Thanks for the updates on this! |
evilnick
added a commit
that referenced
this pull request
May 6, 2015
Various updates to storage docs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.