Doc: Clarify how to configure CephFS vols as image/backup store#1418
Doc: Clarify how to configure CephFS vols as image/backup store#1418roosterfish wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the MicroCloud initialization documentation to clarify how to configure LXD’s storage.images_volume and storage.backups_volume when using CephFS, emphasizing per-cluster-member configuration via lxc --target.
Changes:
- Adjusts the instructions for setting
storage.images_volume/storage.backups_volumeto use--target <cluster member>. - Adjusts the “view configured values” examples to use
--target <cluster member>as well.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
8bda344 to
127d652
Compare
elijahgreenstein
left a comment
There was a problem hiding this comment.
Just a small suggestion, @roosterfish
| ``` | ||
|
|
||
| Once the storage volumes are created, set them as the values for the {ref}`configuration options <lxd:server-options-misc>` of `storage.images_volume` and `storage.backups_volume`. This example syntax uses `remote-fs` as the storage pool, along with volumes named `images` and `backup`: | ||
| Once the storage volumes are created, set them as the values for the {ref}`configuration options <lxd:server-options-misc>` of `storage.images_volume` and `storage.backups_volume`. Repeat these steps for each cluster member. |
There was a problem hiding this comment.
| Once the storage volumes are created, set them as the values for the {ref}`configuration options <lxd:server-options-misc>` of `storage.images_volume` and `storage.backups_volume`. Repeat these steps for each cluster member. | |
| Once the storage volumes are created, set them as the values for the `storage.images_volume` and `storage.backups_volume` {ref}`configuration options <lxd:server-options-misc>`. Repeat these steps for each cluster member. |
There was a problem hiding this comment.
Thanks, fixed.
I have also moved the "Repeat these steps for each cluster member" sentence based on reporters feedback in #1417 (comment).
…backup store A user might not be aware that it's crucial to set the config per cluster member. So instead of mentioning it at the bottom, use the --target key specifically. Otherwise a user would need to know that he needs to go to each cluster member to set the config key. Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
127d652 to
51a6f5d
Compare
elijahgreenstein
left a comment
There was a problem hiding this comment.
LGTM! Moving the "repeat these steps" line makes a lot of sense
Fixes #1417.
A user might not be aware that it's crucial to set the config per cluster member. So instead of mentioning it at the bottom, use the
--targetkey specifically.Otherwise a user would need to know that he needs to go to each cluster member to set the config key.