From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] storage plugins: what is plugindata()->{content}[1]
Date: Fri, 7 Feb 2025 10:19:26 +0100 [thread overview]
Message-ID: <f294c444-e845-4ab9-aa4a-9469267f71bd@proxmox.com> (raw)
In-Reply-To: <mailman.122.1738918965.293.pve-devel@lists.proxmox.com>
Am 07.02.25 um 10:02 schrieb Roland Kammerer via pve-devel:
> Hi all,
>
> rather simple question I guess, but I could not find the answer in
> https://pve.proxmox.com/wiki/Storage_Plugin_Development and linked
> documents and looks like my grep foo is lacking today, so here we go:
> I guess I know what the first hash in the 'content' array is, but what
> is the second? Actually, why is there a second one?
>
> Storage/LVMPlugin.pm:
> content => [ {images => 1, rootdir => 1}, { images => 1 }]
>
> vs.
>
> Storage/LvmThinPlugin.pm:
> content => [ {images => 1, rootdir => 1}, { images => 1, rootdir => 1}]
>
> Best, rck
Hi,
the first entry is all valid content types that the plugin supports, the
second entry is the fallback for the storage configuration, i.e. if the
storage configuration for a specific storage does not explicitly specify
a 'content' option, those will be used/allowed. See the parse_config()
method in Plugin.pm.
Best Regards,
Fiona
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-02-07 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 9:02 Roland Kammerer via pve-devel
2025-02-07 9:18 ` Fabian Grünbichler
2025-02-07 12:34 ` Roland Kammerer via pve-devel
2025-02-12 10:57 ` Fabian Grünbichler
[not found] ` <Z6X9vOv2lCsvTy3o@arm64>
2025-02-25 10:50 ` Max Carrara
2025-03-07 8:24 ` Roland Kammerer via pve-devel
[not found] ` <Z8qtOTycFZpN5bpL@arm64>
2025-03-07 12:01 ` Roland Kammerer via pve-devel
2025-03-12 11:09 ` Max Carrara
2025-02-07 9:19 ` 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=f294c444-e845-4ab9-aa4a-9469267f71bd@proxmox.com \
--to=f.ebner@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.