From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 7AC9C1FF16B for ; Tue, 29 Jul 2025 15:50:09 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 69E11135CE; Tue, 29 Jul 2025 15:51:32 +0200 (CEST) Message-ID: Date: Tue, 29 Jul 2025 15:50:58 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Proxmox VE development discussion , Wolfgang Bumiller References: <20250729111557.136012-1-w.bumiller@proxmox.com> <20250729111557.136012-8-w.bumiller@proxmox.com> Content-Language: en-US From: Fiona Ebner In-Reply-To: <20250729111557.136012-8-w.bumiller@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1753797048832 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.026 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [common.pm] Subject: Re: [pve-devel] [PATCH storage 07/26] common: add pve-storage-vtype standard option with new types X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Am 29.07.25 um 1:16 PM schrieb Wolfgang Bumiller: > This adds the vm-vol and ct-vol vtypes introduced in the upcoming > commits. > > Signed-off-by: Wolfgang Bumiller > --- > src/PVE/Storage/Common.pm | 17 +++++++++++++++++ > 1 file changed, 17 insertions(+) > > diff --git a/src/PVE/Storage/Common.pm b/src/PVE/Storage/Common.pm > index 222dc76..b2ebd50 100644 > --- a/src/PVE/Storage/Common.pm > +++ b/src/PVE/Storage/Common.pm > @@ -59,6 +59,23 @@ PVE::JSONSchema::register_standard_option( > }, > ); > > +=head3 pve-storage-vtype > + > +Possible vtypes a guest image can have. IMHO, this should be renamed to make it clear that it's only for guest images, not all vtypes. > + > +=cut > + > +PVE::JSONSchema::register_standard_option( > + 'pve-storage-vtype', > + { > + type => 'string', > + enum => [qw(vm-vol ct-vol images rootdir)], > + description => > + "The volume type indicates whether the volume is meant for VMs or containers." > + . " The 'images' and 'rootdir' types are for legacy support and should be avoided.", > + }, > +); > + > =pod > > =head1 FUNCTIONS _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel