From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Leo Nunner <l.nunner@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs] storage: more documentation for content-dirs
Date: Mon, 21 Aug 2023 11:10:22 +0200 [thread overview]
Message-ID: <93168cee-93db-410f-6641-746ac83323d2@proxmox.com> (raw)
In-Reply-To: <20230607133216.216761-1-l.nunner@proxmox.com>
Am 07.06.23 um 15:32 schrieb Leo Nunner:
> give an overview over vtypes and also document the option for
> cephfs.
>
While no big deal, sounds like it should be two patches ;)
> Signed-off-by: Leo Nunner <l.nunner@proxmox.com>
> ---
> pve-storage-cephfs.adoc | 4 ++++
> pve-storage-dir.adoc | 20 ++++++++++++++++++++
> 2 files changed, 24 insertions(+)
>
> diff --git a/pve-storage-cephfs.adoc b/pve-storage-cephfs.adoc
> index c10976b..6873660 100644
> --- a/pve-storage-cephfs.adoc
> +++ b/pve-storage-cephfs.adoc
> @@ -57,6 +57,10 @@ fuse::
> Access CephFS through FUSE, instead of the kernel client. Optional, defaults
> to `0`.
>
> +content-dirs::
> +
> +Overrides for the default directory layout. Optional.
> +
> .Configuration example for an external Ceph cluster (`/etc/pve/storage.cfg`)
> ----
> cephfs: cephfs-external
> diff --git a/pve-storage-dir.adoc b/pve-storage-dir.adoc
> index 3367394..61dddeb 100644
> --- a/pve-storage-dir.adoc
> +++ b/pve-storage-dir.adoc
> @@ -59,6 +59,26 @@ in the following format:
> Where `vtype` is one of the allowed content types for the storage, and
> `path` is a path relative to the mountpoint of the storage.
>
> +.Overrides
> +[width="100%",cols="d,m,m",options="header"]
> +|===========================================================
> +|Content type |vtype | Example
> +|VM images |`images` | images=sub/dir
> +|ISO images |`iso` | iso=sub/dir
> +|Container templates |`vztmpl` | vztmpl=sub/dir
> +|Backup files |`backup` | backup=sub/dir
> +|Snippets |`sinppet` | snippet=sub/dir
> +|===========================================================
> +
Typo: sinppet and it should be plural: snippets
Maybe instead of adding a second table here, we could also just add a
vtype column to the Directory layout table that's right above?
> +So an override for VM images would look like `images=dir/path`, an
> +override for ISO images like `iso=dir/path` etc. They can also be
> +combined in a list:
> +
> +----
> +content-dirs images=dir/path,iso=dir/path
> +----
> +
> +
> .Configuration Example (`/etc/pve/storage.cfg`)
> ----
> dir: backup
prev parent reply other threads:[~2023-08-21 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 13:32 Leo Nunner
2023-08-21 9:10 ` Fiona Ebner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=93168cee-93db-410f-6641-746ac83323d2@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=l.nunner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.