public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH storage v3 4/4] vdisk_alloc: add assertion for volume's content type
Date: Tue, 15 Apr 2025 15:50:22 +0200	[thread overview]
Message-ID: <20250415135045.255272-5-d.kral@proxmox.com> (raw)
In-Reply-To: <20250415135045.255272-1-d.kral@proxmox.com>

Require a caller of vdisk_alloc() to specify the volume's intended
content type and assert whether the specified content type may be stored
on the specified storage before allocating any volume.

The 'any' volume type is for backwards compatibility of external
callers, whose API would break if content type assertions would be
added.

The two affected pve-storage code paths of this change are the API
handler for the `pvesm alloc` endpoint, which fallbacks to 'images' or
'rootdir' depending which is supported for the storage and errors out if
neither is available, and the extract_disk_from_import_file subroutine,
which is assumed to always create a VM image for now, as its only caller
is for VM images currently.

This requires a versioned break for packages where vdisk_alloc() is
called from, which are currently qemu-server and pve-container.

Signed-off-by: Daniel Kral <d.kral@proxmox.com>
---
changes since v2:
  * make $vtype a required parameter now
  * add better documentation about the $vtype's possible values
  * do only allow $vtype to be 'images', 'rootdir', 'import' and 'any'
  * add the 'any' content type for backwards compatibility until PVE 9
  * add commit message description about 'any' content type and changes
    do existing code paths
  * add fallback logic in `pvesm alloc` for retrieving a content type

 src/PVE/API2/Storage/Content.pm    | 13 ++++++++++++-
 src/PVE/GuestImport.pm             |  3 ++-
 src/PVE/Storage.pm                 | 20 +++++++++++++++-----
 src/test/run_test_zfspoolplugin.pl | 12 ++++++++----
 4 files changed, 37 insertions(+), 11 deletions(-)

diff --git a/src/PVE/API2/Storage/Content.pm b/src/PVE/API2/Storage/Content.pm
index 64ed56d..7cfb9c1 100644
--- a/src/PVE/API2/Storage/Content.pm
+++ b/src/PVE/API2/Storage/Content.pm
@@ -217,9 +217,20 @@ __PACKAGE__->register_method ({
 	}
 
 	my $cfg = PVE::Storage::config();
+	my $scfg = PVE::Storage::storage_config($cfg, $storeid);
+
+	# FIXME Replace fallback logic with scoped volume names
+	my $vtype;
+	$vtype = 'images' if defined($scfg->{content}->{images});
+	$vtype = 'rootdir' if defined($scfg->{content}->{rootdir});
+	if (!$vtype) {
+	    raise_param_exc({
+		    storage => "'$storeid' does neither support content type 'images' nor 'rootdir'"
+	    });
+	}
 
 	my $volid = PVE::Storage::vdisk_alloc(
-	    $cfg, $storeid, $param->{vmid}, $param->{format}, $size, { name => $name });
+	    $cfg, $storeid, $param->{vmid}, $param->{format}, $vtype, $size, { name => $name });
 
 	return $volid;
     }});
diff --git a/src/PVE/GuestImport.pm b/src/PVE/GuestImport.pm
index 76ebc9d..a285043 100644
--- a/src/PVE/GuestImport.pm
+++ b/src/PVE/GuestImport.pm
@@ -69,7 +69,8 @@ sub extract_disk_from_import_file {
 
 	# create temporary 1M image that will get overwritten by the rename
 	# to reserve the filename and take care of locking
-	$target_volid = PVE::Storage::vdisk_alloc($cfg, $target_storeid, $vmid, $inner_fmt, 1024);
+	$target_volid = PVE::Storage::vdisk_alloc(
+	    $cfg, $target_storeid, $vmid, $inner_fmt, 'images', 1024);
 	$target_path = PVE::Storage::path($cfg, $target_volid);
 
 	print "renaming $source_path to $target_path\n";
diff --git a/src/PVE/Storage.pm b/src/PVE/Storage.pm
index ab4dcdd..f089777 100755
--- a/src/PVE/Storage.pm
+++ b/src/PVE/Storage.pm
@@ -1056,16 +1056,20 @@ sub unmap_volume {
     return $plugin->unmap_volume($storeid, $scfg, $volname, $snapname);
 }
 
-=head3 vdisk_alloc($cfg, $storeid, $vmid, $fmt, $size [, %opts])
+=head3 vdisk_alloc($cfg, $storeid, $vmid, $fmt, $vtype, $size [, %opts])
 
 Allocates a volume on the storage with the identifier C<$storeid> (defined in
-the storage config C<$cfg>) for the VM with the id C<$vmid> with format C<$fmt>
-and a size of C<$size> kilobytes.
+the storage config C<$cfg>) for the VM with the id C<$vmid> with format C<$fmt>,
+volume type C<$vtype> and a size of C<$size> kilobytes.
 
 The format C<$fmt> can be C<'raw'>, C<'qcow2'>, C<'subvol'> or C<'vmdk'>. If
 C<$fmt> is left undefined, it will fallback on the default format of the storage
 type of C<$storeid>.
 
+The volume type C<$vtype> can be C<'images'>, C<'rootdir'>, C<'import'>, or
+C<'any'>, where the last allows the allocation of any volume type. C<'any'> will
+be removed in PVE 9, so do not rely on this value for new code.
+
 Optionally, the following key-value pairs are available for C<%opts>:
 
 =over
@@ -1082,8 +1086,8 @@ Returns the identifier for the new volume in the format C<"$storeid:$volname">.
 
 =cut
 
-sub vdisk_alloc : prototype($$$$$;%) {
-    my ($cfg, $storeid, $vmid, $fmt, $size, $opts) = @_;
+sub vdisk_alloc : prototype($$$$$$;%) {
+    my ($cfg, $storeid, $vmid, $fmt, $vtype, $size, $opts) = @_;
 
     my $name = $opts->{name};
 
@@ -1103,6 +1107,12 @@ sub vdisk_alloc : prototype($$$$$;%) {
 
     activate_storage($cfg, $storeid);
 
+    die "no volume type specified\n" if !$vtype;
+    die "$vtype is not a valid volume type for vdisk_alloc\n"
+	if $vtype !~ m/(any|images|import|rootdir)/;
+
+    assert_content_type_available($cfg, $storeid, $vtype) if $vtype ne 'any';
+
     my $plugin = PVE::Storage::Plugin->lookup($scfg->{type});
 
     # lock shared storage
diff --git a/src/test/run_test_zfspoolplugin.pl b/src/test/run_test_zfspoolplugin.pl
index 7dd0a2b..c85ee2c 100755
--- a/src/test/run_test_zfspoolplugin.pl
+++ b/src/test/run_test_zfspoolplugin.pl
@@ -565,7 +565,8 @@ my $test13 = sub {
     print "\nrun test13 \"vdisk_alloc\"\n";
 
     eval {
-	my $tmp_volid = PVE::Storage::vdisk_alloc($cfg, $storagename, "112", "raw", 1024 * 1024);
+	my $tmp_volid = PVE::Storage::vdisk_alloc(
+	    $cfg, $storagename, "112", "raw", "images", 1024 * 1024);
 
 	if ($tmp_volid ne "$storagename:vm-112-disk-0") {
 	    die "volname:$tmp_volid don't match\n";
@@ -589,7 +590,8 @@ my $test13 = sub {
     }
 
     eval {
-	my $tmp_volid = PVE::Storage::vdisk_alloc($cfg, $storagename, "112", "raw", 2048 * 1024);
+	my $tmp_volid = PVE::Storage::vdisk_alloc(
+	    $cfg, $storagename, "112", "raw", "images", 2048 * 1024);
 
 	if ($tmp_volid ne "$storagename:vm-112-disk-1") {
 	    die "volname:$tmp_volid don't match\n";
@@ -613,7 +615,8 @@ my $test13 = sub {
     }
 
     eval {
-	my $tmp_volid = PVE::Storage::vdisk_alloc($cfg, $storagename, "113", "subvol", 1024 * 1024);
+	my $tmp_volid = PVE::Storage::vdisk_alloc(
+	    $cfg, $storagename, "113", "subvol", "images", 1024 * 1024);
 
 	if ($tmp_volid ne "$storagename:subvol-113-disk-0") {
 	    die "volname:$tmp_volid  don't match\n";
@@ -637,7 +640,8 @@ my $test13 = sub {
     }
 
     eval {
-	my $tmp_volid = PVE::Storage::vdisk_alloc($cfg, $storagename, "113", "subvol", 2048 * 1024);
+	my $tmp_volid = PVE::Storage::vdisk_alloc(
+	    $cfg, $storagename, "113", "subvol", "images", 2048 * 1024);
 
 	if ($tmp_volid ne "$storagename:subvol-113-disk-1") {
 	    die "volname:$tmp_volid  don't match\n";
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  parent reply	other threads:[~2025-04-15 13:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 13:50 [pve-devel] [PATCH storage/qemu-server/container v3 00/27] consistent assertions for volume's content types Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH storage v3 1/4] introduce helpers for content type assertions of storages and volumes Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH storage v3 2/4] tree-wide: make use of content type assertion helper Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH storage v3 3/4] vdisk_alloc: factor out optional parameters in options hash argument Daniel Kral
2025-05-05 14:51   ` Wolfgang Bumiller
2025-05-06  7:33     ` Daniel Kral
2025-04-15 13:50 ` Daniel Kral [this message]
2025-04-15 13:50 ` [pve-devel] [PATCH qemu-server v3 01/12] fix #5284: cli: importovf: assert content type support for target storage Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH qemu-server v3 02/12] api: remove unusable default storage parameter in check_storage_access Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH qemu-server v3 03/12] fix #5284: api: update-vm: assert content type support for cloudinit images Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH qemu-server v3 04/12] tree-wide: update vdisk_alloc optional arguments signature Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH qemu-server v3 05/12] tree-wide: update vdisk_alloc vtype argument signature Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH qemu-server v3 06/12] cfg2cmd: improve error message for invalid volume content type Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH qemu-server v3 07/12] api: {clone, move}_vm: use volume content type assertion helpers Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH qemu-server v3 08/12] api: {create, update}_vm: " Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH qemu-server v3 09/12] api: import{disk, ovf}: " Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH qemu-server v3 10/12] api: qmrestore: " Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH qemu-server v3 11/12] api: migrate_vm: " Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH qemu-server v3 12/12] tree-wide: add todos for breaking content type assertions Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH container v3 01/11] migration: prepare: factor out common read-only variables Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH container v3 02/11] tests: add tests for expected behavior of alloc_disk wrapper Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH container v3 03/11] alloc disk: fix content type check for ZFS storages Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH container v3 04/11] alloc_disk: factor out common arguments for call to vdisk_alloc Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH container v3 05/11] alloc_disk: simplify storage-specific logic for vdisk_alloc arguments Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH container v3 06/11] alloc_disk: update vdisk_alloc optional arguments signature Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH container v3 07/11] alloc_disk: use volume content type assertion helpers Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH container v3 08/11] api: create: " Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH container v3 09/11] migration: prepare: " Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH container v3 10/11] api: update_vm: " Daniel Kral
2025-04-15 13:50 ` [pve-devel] [PATCH container v3 11/11] mount: raw/iso: " Daniel Kral
2025-05-06  8:33 ` [pve-devel] [PATCH storage/qemu-server/container v3 00/27] consistent assertions for volume's content types Wolfgang Bumiller
2025-05-09  8:11   ` Fabian Grünbichler

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=20250415135045.255272-5-d.kral@proxmox.com \
    --to=d.kral@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal