public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Hannes Laimer <h.laimer@proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 qemu-server] api: qemu: make resize_vm async close #2315
Date: Tue, 12 Jan 2021 12:24:41 +0100	[thread overview]
Message-ID: <43ffecfe-494e-4b3a-dbfe-39fa880c1bf2@proxmox.com> (raw)
In-Reply-To: <20210112110754.168177-1-h.laimer@proxmox.com>

On 12.01.21 12:07, Hannes Laimer wrote:
> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
> ---
> Resize is now done in a task.
> 
> v1 -> v2: pass code that should be executed correctly to fork_worker

yeah that looked weird in the v1, did not checked it and assumed
you tested the version you actually send at least once (please try do so
in the future).

Anyway, all other points I replied to v1 still apply to v2.

> 
>  PVE/API2/Qemu.pm | 9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm
> index e8de4ea..0c5d50c 100644
> --- a/PVE/API2/Qemu.pm
> +++ b/PVE/API2/Qemu.pm
> @@ -3730,7 +3730,7 @@ __PACKAGE__->register_method({
>  	    },
>  	},
>      },
> -    returns => { type => 'null'},
> +    returns => { type => 'string'},
>      code => sub {
>          my ($param) = @_;
>  
> @@ -3816,9 +3816,10 @@ __PACKAGE__->register_method({
>  
>  	    PVE::QemuConfig->write_config($vmid, $conf);
>  	};
> -
> -        PVE::QemuConfig->lock_config($vmid, $updatefn);
> -        return;
> +	my $worker = sub {
> +	    PVE::QemuConfig->lock_config($vmid, $updatefn);
> +	};
> +	return $rpcenv->fork_worker('qmresize', $vmid, $authuser, $worker);
>      }});
>  
>  __PACKAGE__->register_method({
> 





      parent reply	other threads:[~2021-01-12 11:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 11:07 Hannes Laimer
2021-01-12 11:17 ` Oguz Bektas
2021-01-12 11:24 ` Thomas Lamprecht [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=43ffecfe-494e-4b3a-dbfe-39fa880c1bf2@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=h.laimer@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