all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Erik Fastermann <e.fastermann@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [RFC qemu-server 2/4] remote migrate: collect preconditions as structured findings
Date: Fri, 31 Jul 2026 15:42:51 +0200	[thread overview]
Message-ID: <63311ffa-f824-4322-9360-a456e4e51401@proxmox.com> (raw)
In-Reply-To: <26a8a6f4-0870-4bfc-807e-b75275f6d743@proxmox.com>

[snip]

>> User-visible effect is minimal: successful migrations are unchanged.
>> Some precondition error messages are reworded and the "Establishing
>> API connection" info line is no longer printed.
> 
> Do we gain anything from not printing it? Such changes can also be nicer
> in separate patches to ease reviewability and discussion.
> 

I thought printing the info line would be noise in the precondition 
endpoint, which I can put in the commit message, in a separate patch.

[snip]
>> +        my $findings = [];
>> +        my $plan = validate_remote_migrate_preconditions($param, $findings);
> 
> Style nit: why pass in $findings like this? You can just return multiple
> values instead. I'd prefer a name like $migration_info rather than $plan.
> 

I didn't want to return the findings array on every possible exit point 
of the function, so I thought this would be nicer. I could add an extra 
wrapper function which does this though, so I will try that.

[snip]





  reply	other threads:[~2026-07-31 13:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 11:58 [RFC qemu-server 0/4] remote migrate: extract preconditions and add check endpoint Erik Fastermann
2026-07-21 11:58 ` [RFC qemu-server 1/4] remote migrate: drop ineffective fingerprint auto-detection Erik Fastermann
2026-07-29  9:56   ` Fiona Ebner
2026-07-29  9:59     ` Fiona Ebner
2026-07-29 10:02       ` Fiona Ebner
2026-07-29 10:07     ` Fabian Grünbichler
2026-07-29 10:17       ` Fiona Ebner
2026-07-21 11:58 ` [RFC qemu-server 2/4] remote migrate: collect preconditions as structured findings Erik Fastermann
2026-07-29  9:56   ` Fiona Ebner
2026-07-31 13:42     ` Erik Fastermann [this message]
2026-07-21 11:58 ` [RFC qemu-server 3/4] qm: remote-migrate: call API endpoint directly Erik Fastermann
2026-07-21 11:58 ` [RFC qemu-server 4/4] remote migrate: add precondition check endpoint Erik Fastermann
2026-07-29  9:56   ` Fiona Ebner
2026-07-31 13:43     ` Erik Fastermann
2026-07-29  9:56 ` [RFC qemu-server 0/4] remote migrate: extract preconditions and add " Fiona Ebner
2026-07-31 13:42   ` Erik Fastermann
2026-07-31 14:44     ` 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=63311ffa-f824-4322-9360-a456e4e51401@proxmox.com \
    --to=e.fastermann@proxmox.com \
    --cc=f.ebner@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