all lists on 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 qemu-server] api: qemu: make resize_vm async close #2315
Date: Tue, 12 Jan 2021 12:20:39 +0100	[thread overview]
Message-ID: <caa3d328-b0d1-3d2e-2fbf-8625a43ac920@proxmox.com> (raw)
In-Reply-To: <20210112094436.136048-1-h.laimer@proxmox.com>

On 12.01.21 10:44, Hannes Laimer wrote:
> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
> ---
> Resizing is now done asynchronous in a task.

seems like an API change, doesn't it? Maybe (did not checked) we could
add an "async" boolean param and make the return type a optional string, can
you please check if that would work and stay compatible as long as async is not
passed as true.

Then there are again a few cosmetic, but still important, issues:
* even if it's rather obvious the cost adding something like:
  "resize can easily hang for a longer time depending on underlying storage
  and load" is almost zero (takes <10 seconds of one person) and can only
  help to avoid people going to the b
* place the "fix #2315:" first
  https://pve.proxmox.com/wiki/Developer_Documentation#Commits_and_Commit_Messages
* replace the "qemu:" with "disk:", as we're in the qemu-server repository
  the "qemu" doesn't adds much informational value here (like it would in the,
  e.g., pve-manager one).

thanks!

> 
>  PVE/API2/Qemu.pm | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm
> index e8de4ea..379f34a 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) = @_;
>  
> @@ -3817,8 +3817,7 @@ __PACKAGE__->register_method({
>  	    PVE::QemuConfig->write_config($vmid, $conf);
>  	};
>  
> -        PVE::QemuConfig->lock_config($vmid, $updatefn);
> -        return;
> +	return $rpcenv->fork_worker('qmresize', $vmid, $authuser, PVE::QemuConfig->lock_config($vmid, $updatefn));
>      }});
>  
>  __PACKAGE__->register_method({
> 






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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12  9:44 Hannes Laimer
2021-01-12 11:20 ` 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=caa3d328-b0d1-3d2e-2fbf-8625a43ac920@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 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