public inbox for pve-devel@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>,
	Aaron Lauterer <a.lauterer@proxmox.com>
Subject: Re: [pve-devel] [PATCH container v2 5/6] migration: only migrate volumes used by the guest
Date: Mon, 22 May 2023 17:00:21 +0200	[thread overview]
Message-ID: <8e72aa37-9d4b-3e1e-f8bc-3a9a6d14cbce@proxmox.com> (raw)
In-Reply-To: <20230512124043.888785-6-a.lauterer@proxmox.com>

Am 12.05.23 um 14:40 schrieb Aaron Lauterer:
> When scanning all configured storages for volumes belonging to the
> container, the migration could easily fail if a storage is not
> available, but enabled. That storage might not even be used by the
> container at all.
> 
> By not doing that and only looking at the disk images referenced in the
> config, we can avoid that.
> We need to add additional steps for pending volumes with checks if they
> actually exist. Changing an existing mountpoint to a new volume
> will only create the volume on the next start of the container.
> 
> The big change regarding behavior is that volumes not referenced in the
> container config will be ignored.  They are already orphans that used to
> be migrated as well, but are now left where they are.
> 
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
>  src/PVE/LXC/Migrate.pm | 47 +++++++++++++++---------------------------
>  1 file changed, 17 insertions(+), 30 deletions(-)
> 
> diff --git a/src/PVE/LXC/Migrate.pm b/src/PVE/LXC/Migrate.pm
> index ccf5157..8e11be7 100644
> --- a/src/PVE/LXC/Migrate.pm
> +++ b/src/PVE/LXC/Migrate.pm
> @@ -195,6 +195,17 @@ sub phase1 {
>  
>  	return if !$volid;
>  
> +	# check if volume exists, might be a pending new one
> +	eval {
> +	    PVE::Storage::path($self->{storecfg}, $volid);
> +	};
> +	if ($@ =~ m/^unable to parse/) {

I'd really like to avoid such manual error message matching, especially
across package boundaries. PVE::Storage::path() calls parse_volume_id(),
but that also works for storeid:1 for example, so not triggering an
error for such pending changes. PVE::Storage::path() then calls the
plugin's path(), but the plugin can use whatever error message it likes,
so matching for something specific only covers certain plugins. Can't we
just filter out the yet-to-be-created volumes by matching the NEW_DISK_RE?

> +	    $self->log('info', "volume '$volid' does not exist (pending change?)");
> +	    return;
> +	} elsif ($@) {
> +	    die $@;
> +	}
> +
>  	my ($sid, $volname) = PVE::Storage::parse_volume_id($volid);
>  
>  	# check if storage is available on source node

(...)

> +    # first all volumes referenced in snapshots
>      foreach my $snapname (keys %{$conf->{snapshots}}) {
>  	&$test_volid($conf->{snapshots}->{$snapname}->{'vmstate'}, 0, undef)
>  	    if defined($conf->{snapshots}->{$snapname}->{'vmstate'});
>  	PVE::LXC::Config->foreach_volume($conf->{snapshots}->{$snapname}, $test_mp, $snapname);
>      }
>  
> +    # then all pending volumes
> +    if (defined $conf->{pending} && %{$conf->{pending}}) {

Style nit: please use parentheses for defined

> +	PVE::LXC::Config->foreach_volume($conf->{pending}, $test_mp);
> +    }
> +
>      # finally all current volumes
>      PVE::LXC::Config->foreach_volume_full($conf, { include_unused => 1 }, $test_mp);
>  




  reply	other threads:[~2023-05-22 15:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 12:40 [pve-devel] [PATCH qemu-server, container v2 0/6] migration: don't scan all storages, fail on aliases Aaron Lauterer
2023-05-12 12:40 ` [pve-devel] [PATCH qemu-server v2 1/6] migration: only migrate disks used by the guest Aaron Lauterer
2023-05-22 11:59   ` Fiona Ebner
2023-05-24 15:00     ` Aaron Lauterer
2023-05-12 12:40 ` [pve-devel] [PATCH qemu-server v2 2/6] tests: add migration test for pending disk Aaron Lauterer
2023-05-22 14:02   ` Fiona Ebner
2023-05-12 12:40 ` [pve-devel] [PATCH qemu-server v2 3/6] migration: fail when aliased volume is detected Aaron Lauterer
2023-05-22 14:17   ` Fiona Ebner
2023-05-24 14:40     ` Aaron Lauterer
2023-05-25  8:14       ` Fiona Ebner
2023-05-25  8:15   ` Fiona Ebner
2023-05-12 12:40 ` [pve-devel] [PATCH qemu-server v2 4/6] tests: add migration alias check Aaron Lauterer
2023-05-22 14:25   ` Fiona Ebner
2023-05-24 14:41     ` Aaron Lauterer
2023-05-12 12:40 ` [pve-devel] [PATCH container v2 5/6] migration: only migrate volumes used by the guest Aaron Lauterer
2023-05-22 15:00   ` Fiona Ebner [this message]
2023-05-12 12:40 ` [pve-devel] [PATCH container v2 6/6] migration: fail when aliased volume is detected Aaron Lauterer

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=8e72aa37-9d4b-3e1e-f8bc-3a9a6d14cbce@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=a.lauterer@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