all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Daniel Kral <d.kral@proxmox.com>
Subject: Re: [pve-devel] [PATCH container v2 02/11] tests: add tests for expected behavior of alloc_disk wrapper
Date: Thu, 20 Feb 2025 11:21:50 +0100	[thread overview]
Message-ID: <3da5f7f5-0da4-4679-9950-c95294526be9@proxmox.com> (raw)
In-Reply-To: <20250211160825.254167-23-d.kral@proxmox.com>

Am 11.02.25 um 17:08 schrieb Daniel Kral:
> Adds test cases for the alloc_disk wrapper subroutine to ensure that:
> 
> - zero-sized volumes are allocated as subvols on path-based storages
> - non-zero-sized volumes are allocated as raw on path-based storages
> - volumes are allocated as raw on btrfs storages without quotas
> - volumes are allocated as subvols on btrfs storages with quotas
> - volumes are allocated as subvols on zfs storages
> - volumes cannot be allocated on storages that do not support rootdir
> 
> These test cases should allow to catch regressions in following changes
> to the alloc_disk wrapper.

Always nice to have such tests up-front :)

> diff --git a/src/test/run_alloc_disk_tests.pl b/src/test/run_alloc_disk_tests.pl
> new file mode 100755
> index 0000000..b13f5a2
> --- /dev/null
> +++ b/src/test/run_alloc_disk_tests.pl
> @@ -0,0 +1,149 @@
> +#!/usr/bin/env perl
> +
> +use strict;
> +use warnings;
> +
> +use lib qw(..);
> +
> +use PVE::Tools;
> +
> +use Test::More;
> +use Test::MockModule;
> +
> +use PVE::LXC;
> +
> +my $test_vmid = 100;
> +my $test_root_uid = 100000;
> +my $test_root_gid = 100000;
> +
> +my $storage_config = {
> +    ids => {
> +	local => {
> +	    content => {
> +		rootdir => 1,
> +	    },
> +	    path => "/var/lib/vz",
> +	    type => "dir",
> +	    shared => 0,
> +	},
> +	norootdirs => {

Similar to the qemu-server patch: I'd add some other content to the
hash, just so it's slightly more realistic.

> +	    path => '/var/lib/vz',
> +	    type => 'dir',> +	},
> +	btrfsstore => {
> +	    content => {
> +		rootdir => 1,
> +	    },
> +	    path => '/butter/bread',
> +	    type => 'btrfs',
> +	},
> +	btrfsquotas => {
> +	    content => {
> +		rootdir => 1,
> +	    },
> +	    path => '/butter/bread',
> +	    type => 'btrfs',
> +	    quotas => 1,
> +	},
> +	zfspool0 => {
> +	    type => 'zfspool',
> +	    content => {
> +		rootdir => 1,
> +	    },
> +	    pool => 'rpool0',
> +	    mountpoint => '/zfspool0',
> +	},
> +    },
> +};
> +
> +my $storage_module = Test::MockModule->new("PVE::Storage");
> +$storage_module->redefine(
> +    vdisk_alloc => sub {
> +	my ($storecfg, $storage, $vmid, $fmt, $name, $size_kb) = @_;
> +
> +	$fmt //= '';
> +	my $prefix = ($fmt eq 'subvol') ? 'subvol' : 'vm';
> +
> +	return "$storage:$prefix-$vmid-disk-0";

Nit: To have the tests be slightly more complete, you could have
additional global variables for size and format, similar to how you keep
track of $format_disk_called. But not too important.

> +    },
> +);
> +
> +my $format_disk_called = 0;
> +
> +my $lxc_module = Test::MockModule->new("PVE::LXC");
> +$lxc_module->redefine(
> +    format_disk => sub {
> +	$format_disk_called = 1;
> +    },
> +);
> +
> +my $tests = [
> +    {
> +	description => 'allocate zero-sized volume on path-based storage',
> +	storage => 'local',
> +	size_kb => 0,
> +	result => ["local:subvol-$test_vmid-disk-0", 1],
> +    },
> +    {
> +	description => 'allocate non-zero-sized volume on path-based storage',
> +	should_format_disk => 1,
> +	storage => 'local',
> +	size_kb => 1024 * 1024,
> +	result => ["local:vm-$test_vmid-disk-0", 0],
> +    },
> +    {
> +	description => 'allocate volume on btrfs with quotas disabled',
> +	should_format_disk => 1,
> +	storage => 'btrfsstore',
> +	size_kb => 1024 * 1024,
> +	result => ["btrfsstore:vm-$test_vmid-disk-0", 0],
> +    },
> +    {
> +	description => 'allocate volume on btrfs with quotas enabled',
> +	storage => 'btrfsquotas',
> +	size_kb => 1024 * 1024,
> +	result => ["btrfsquotas:subvol-$test_vmid-disk-0", 1],
> +    },
> +    {
> +	description => 'allocate volume on zfspool',
> +	storage => 'zfspool0',
> +	size_kb => 1024 * 1024,
> +	result => ["zfspool0:subvol-$test_vmid-disk-0", 1],
> +    },
> +    {
> +	description => 'allocate volume on storage without rootdir content type support',
> +	should_fail => 1,
> +	storage => 'norootdirs',
> +	size_kb => 1024 * 1024,
> +    },
> +];
> +
> +# multiply by 2 because of format_disk test
> +plan(tests => 2 * scalar($tests->@*));
> +
> +for my $case ($tests->@*) {
> +    my $should_format_disk = exists($case->{should_format_disk}) ? $case->{should_format_disk} : 0;
> +    $format_disk_called = 0;
> +
> +    my @result = eval {

I'd prefer to be explicit: my ($volid, $needs_chown) = eval {

> +	PVE::LXC::alloc_disk(
> +	    $storage_config,
> +	    $test_vmid,
> +	    $case->{storage},
> +	    $case->{size_kb},
> +	    $test_root_uid,
> +	    $test_root_gid
> +	)
> +    };
> +

Style nit: I'd avoid the blank line here to make it less likely for
future code to sneak in

> +    if ($@) {

Style nit: if (my $err = $@) { and then use $err. Because what if
somebody changes the $should_fail assignment to a function call in the
future or adds another line in between, then you might suddenly have a
different $@ in the check below.

> +	my $should_fail = exists($case->{should_fail}) ? $case->{should_fail} : 0;
> +	is(defined($@), $should_fail, "should fail: $case->{description}") || diag explain $@;

I'd just write 1 instead of defined($@), because we are already in the
failure branch. Note that defined($@) would otherwise return 'undef', so
comparing against 0 wouldn't work either. And note this requires
$should_fail to be exactly 1 and not some other true value.

So I'd prefer using something like:

if ($should_fail) {
    pass(...)
} else {
    diag ...
    fail(...)
}

> +    } else {
> +	is_deeply(\@result, $case->{result}, $case->{description});
> +    }
> +
> +    is($format_disk_called, $should_format_disk, "should format_disk: $case->{description}");
> +}
> +
> +done_testing();



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


  reply	other threads:[~2025-02-20 10:22 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11 16:07 [pve-devel] [PATCH container/qemu-server/storage v2 00/31] consistent assertions for volume's content types Daniel Kral
2025-02-11 16:07 ` [pve-devel] [PATCH pve-storage v2 1/5] api: {upload, download}_url: factor out common parameter hash accesses Daniel Kral
2025-02-19 15:39   ` [pve-devel] applied: " Fiona Ebner
2025-02-11 16:07 ` [pve-devel] [PATCH pve-storage v2 2/5] introduce helpers for content type assertions of storages and volumes Daniel Kral
2025-02-19 14:54   ` Fiona Ebner
2025-02-20  9:14     ` Daniel Kral
2025-02-20  9:36       ` Fiona Ebner
2025-02-20 12:53         ` Daniel Kral
2025-02-20 12:58           ` Fiona Ebner
2025-02-11 16:07 ` [pve-devel] [PATCH pve-storage v2 3/5] tree-wide: make use of content type assertion helper Daniel Kral
2025-02-19 15:16   ` Fiona Ebner
2025-02-20  9:31     ` Daniel Kral
2025-02-11 16:07 ` [pve-devel] [PATCH pve-storage v2 4/5] vdisk_alloc: factor out optional parameters in options hash argument Daniel Kral
2025-02-20  8:49   ` Fiona Ebner
2025-02-20  9:34     ` Daniel Kral
2025-02-11 16:07 ` [pve-devel] [PATCH pve-storage v2 5/5] vdisk_alloc: add optional assertion for volume's content type Daniel Kral
2025-02-20  9:03   ` Fiona Ebner
2025-02-20 10:40     ` Fabian Grünbichler
2025-02-20 10:48       ` Fiona Ebner
2025-02-20 12:33         ` Daniel Kral
2025-02-20 13:09           ` Fiona Ebner
2025-02-11 16:08 ` [pve-devel] [PATCH qemu-server v2 01/15] test: cfg2cmd: expect error for invalid volume's storage " Daniel Kral
2025-02-19 15:45   ` Fiona Ebner
2025-02-11 16:08 ` [pve-devel] [PATCH qemu-server v2 02/15] fix #5284: api: move-disk: assert content type support for target storage Daniel Kral
2025-02-20 14:04   ` Fiona Ebner
2025-02-11 16:08 ` [pve-devel] [PATCH qemu-server v2 03/15] fix #5284: api: clone_vm: " Daniel Kral
2025-02-20 14:04   ` Fiona Ebner
2025-02-11 16:08 ` [pve-devel] [PATCH qemu-server v2 04/15] api: remove unused size variable in check_storage_access Daniel Kral
2025-02-20 14:04   ` Fiona Ebner
2025-02-11 16:08 ` [pve-devel] [PATCH qemu-server v2 05/15] api: remove unusable default storage parameter " Daniel Kral
2025-02-20 14:09   ` Fiona Ebner
2025-02-21  8:27     ` Daniel Kral
2025-02-21  9:15       ` Fiona Ebner
2025-02-20 14:15   ` Fiona Ebner
2025-02-11 16:08 ` [pve-devel] [PATCH qemu-server v2 06/15] fix #5284: api: update-vm: assert content type support for cloudinit images Daniel Kral
2025-02-20 14:23   ` Fiona Ebner
2025-02-21  8:30     ` Daniel Kral
2025-02-21  9:42       ` Fiona Ebner
2025-02-11 16:08 ` [pve-devel] [PATCH qemu-server v2 07/15] fix #5284: cli: importovf: assert content type support for target storage Daniel Kral
2025-02-20 14:29   ` Fiona Ebner
2025-02-11 16:08 ` [pve-devel] [PATCH qemu-server v2 08/15] tree-wide: update vdisk_alloc optional arguments signature Daniel Kral
2025-02-20 14:36   ` Fiona Ebner
2025-02-11 16:08 ` [pve-devel] [PATCH qemu-server v2 09/15] cfg2cmd: improve error message for invalid volume content type Daniel Kral
2025-02-11 16:08 ` [pve-devel] [PATCH qemu-server v2 10/15] api: {clone, move}_vm: use volume content type assertion helpers Daniel Kral
2025-02-11 16:08 ` [pve-devel] [PATCH qemu-server v2 11/15] api: {create, update}_vm: " Daniel Kral
2025-02-11 16:08 ` [pve-devel] [PATCH qemu-server v2 12/15] api: import{disk, ovf}: " Daniel Kral
2025-02-11 16:08 ` [pve-devel] [PATCH qemu-server v2 13/15] api: qmrestore: " Daniel Kral
2025-02-11 16:08 ` [pve-devel] [PATCH qemu-server v2 14/15] api: migrate_vm: " Daniel Kral
2025-02-20 14:46   ` Fiona Ebner
2025-02-20 17:50     ` Daniel Kral
2025-02-21  9:45       ` Fiona Ebner
2025-02-11 16:08 ` [pve-devel] [PATCH qemu-server v2 15/15] tree-wide: add todos for breaking content type assertions Daniel Kral
2025-02-20 14:47   ` Fiona Ebner
2025-02-11 16:08 ` [pve-devel] [PATCH container v2 01/11] migration: prepare: factor out common read-only variables Daniel Kral
2025-02-20  9:20   ` Fiona Ebner
2025-02-11 16:08 ` [pve-devel] [PATCH container v2 02/11] tests: add tests for expected behavior of alloc_disk wrapper Daniel Kral
2025-02-20 10:21   ` Fiona Ebner [this message]
2025-02-11 16:08 ` [pve-devel] [PATCH container v2 03/11] alloc_disk: fail fast if storage does not support content type rootdir Daniel Kral
2025-02-20 12:15   ` Fiona Ebner
2025-02-20 17:52     ` Daniel Kral
2025-04-15 12:27     ` Daniel Kral
2025-04-15 13:31       ` Wolfgang Bumiller
2025-04-15 14:19         ` Fabian Grünbichler
2025-04-16  8:19           ` Wolfgang Bumiller
2025-02-11 16:08 ` [pve-devel] [PATCH container v2 04/11] alloc_disk: factor out common arguments for call to vdisk_alloc Daniel Kral
2025-02-20 13:11   ` Fiona Ebner
2025-02-11 16:08 ` [pve-devel] [PATCH container v2 05/11] alloc_disk: simplify storage-specific logic for vdisk_alloc arguments Daniel Kral
2025-02-20 13:22   ` Fiona Ebner
2025-02-11 16:08 ` [pve-devel] [PATCH container v2 06/11] alloc_disk: update vdisk_alloc optional arguments signature Daniel Kral
2025-02-20 13:24   ` Fiona Ebner
2025-02-11 16:08 ` [pve-devel] [PATCH container v2 07/11] alloc_disk: use volume content type assertion helpers Daniel Kral
2025-02-11 16:08 ` [pve-devel] [PATCH container v2 08/11] api: create: " Daniel Kral
2025-02-11 16:08 ` [pve-devel] [PATCH container v2 09/11] migration: prepare: " Daniel Kral
2025-02-11 16:08 ` [pve-devel] [PATCH container v2 10/11] api: update_vm: " Daniel Kral
2025-02-11 16:08 ` [pve-devel] [PATCH container v2 11/11] mount: raw/iso: " Daniel Kral
2025-02-20 13:29   ` Fiona Ebner
2025-02-21  8:38     ` Daniel Kral
2025-02-21  9:50 ` [pve-devel] [PATCH container/qemu-server/storage v2 00/31] consistent assertions for volume's content types Fiona Ebner
2025-02-28  8:46 ` [pve-devel] partially-applied: " Fiona Ebner
2025-04-15 13:58 ` [pve-devel] superseded: " Daniel Kral

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=3da5f7f5-0da4-4679-9950-c95294526be9@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal