From: "Daniel Kral" <d.kral@proxmox.com>
To: "Fiona Ebner" <f.ebner@proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH ha-manager v4 13/27] crm command: support JSON-style migrate command
Date: Fri, 16 Oct 2026 11:53:02 +0200 [thread overview]
Message-ID: <DM665VFXOXT6.VICV4ZEFVU49@proxmox.com> (raw)
In-Reply-To: <20261015125112.174954-14-f.ebner@proxmox.com>
On Thu Oct 15, 2026 at 2:50 PM CEST, Fiona Ebner wrote:
> To pass along opaque migration options from the resource-specific
> migration API endpoint to the resource plugin implementation, the
> options will be encoded as JSON. Instead of just adding an extra
> positional argument with those, support having the full CRM command be
> recorded as JSON in the queued commands file.
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>
> Changes in v4:
> * Encode JSON with canonical => 1.
> * Improve error messages.
>
> src/PVE/HA/Manager.pm | 57 +++++++++++++++++++++++++++++++++++++------
> 1 file changed, 49 insertions(+), 8 deletions(-)
>
> diff --git a/src/PVE/HA/Manager.pm b/src/PVE/HA/Manager.pm
> index c28d7fa..4e7fab5 100644
> --- a/src/PVE/HA/Manager.pm
> +++ b/src/PVE/HA/Manager.pm
> @@ -711,6 +711,28 @@ my sub check_resource_motion_valid {
> return 1;
> }
>
> +my sub handle_crm_motion_command {
> + my ($self, $task, $sid, $node, $options) = @_;
> +
> + my $cmd = "$task $sid $node";
> +
> + if (defined($options) && scalar(keys($options->%*))) {
> + $cmd .= ' ' . JSON::to_json($options, { canonical => 1 });
> + }
> +
> + my ($haenv, $ms, $ns, $sc, $ss) = $self->@{qw(haenv ms ns sc ss)};
nit: $ms, $ns, and $sc are unused here
> +
> + if (my $sd = $ss->{$sid}) {
> + if (check_resource_motion_valid($self, $node, $sd, "ignore crm command '$cmd'")) {
> + $self->queue_resource_motion($cmd, $task, $sid, $node, $options);
> + }
> + } else {
> + $haenv->log('err', "crm command error - no such service: $cmd");
> + }
> +
> + return;
> +}
> +
> # read new crm commands and save them into crm master status
> sub update_crm_commands {
> my ($self) = @_;
> @@ -722,16 +744,35 @@ sub update_crm_commands {
> foreach my $cmd (split(/\n/, $cmdlist)) {
> chomp $cmd;
>
> - if ($cmd =~ m/^(migrate|relocate)\s+(\S+)\s+(\S+)$/) {
> - my ($task, $sid, $node) = ($1, $2, $3);
> - if (my $sd = $ss->{$sid}) {
> - if (check_resource_motion_valid($self, $node, $sd, "ignore crm command '$cmd'")) {
> - $self->queue_resource_motion($cmd, $task, $sid, $node, {});
> - }
> - } else {
> - $haenv->log('err', "crm command error - no such service: $cmd");
> + if ($cmd =~ m/^{/) {
> + # New-style JSON-encoded command. Currently only 'migrate' is supported, allowing for
> + # additional options.
> +
> + my $command_info = eval { JSON::decode_json($cmd) };
> + if (my $err = $@) {
> + $haenv->log('err', "unable to decode JSON command: '$cmd' - $err");
> + next;
> }
>
> + my $kind = $command_info->{kind};
> + if (!defined($kind)) {
> + $haenv->log('err', "unable to handle JSON command without 'kind': '$cmd'");
> + } elsif ($kind eq 'migrate') {
> + my ($sid, $node, $options) = $command_info->@{qw(sid node options)};
> + if (!defined($sid) || !defined($node)) {
> + $haenv->log('err', "'migrate' JSON command without sid or node");
> + next;
> + }
> + handle_crm_motion_command($self, $kind, $sid, $node, $options);
nit: only noticed now, but 'kind' should probably also be 'task' here as
we call it like that everywhere else... Even though with variants
'kind' is more common, so no hard feelings here.
> + } else {
> + $haenv->log('err', "unable to handle unknown JSON command: '$cmd'");
> + }
> +
> + next;
> + }
> +
> + if ($cmd =~ m/^(migrate|relocate)\s+(\S+)\s+(\S+)$/) {
nit: should probably be an elsif here?
> + handle_crm_motion_command($self, $1, $2, $3, {});
> } elsif ($cmd =~ m/^stop\s+(\S+)\s+(\S+)$/) {
> my ($sid, $timeout) = ($1, $2);
> if (my $sd = $ss->{$sid}) {
next prev parent reply other threads:[~2026-10-16 9:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 12:50 [PATCH-SERIES many v4 00/27] migration: strict config check for intra-cluster migration Fiona Ebner
2026-10-15 12:50 ` [PATCH common v4 01/27] tools: move version_cmp() helper from qemu-server Fiona Ebner
2026-10-15 12:50 ` [PATCH common v4 02/27] rest handler: handle: respect schema's 'type-property' when resolving type Fiona Ebner
2026-10-15 12:50 ` [PATCH cluster v4 03/27] cluster: move pvecfg node version helpers from qemu-server Fiona Ebner
2026-10-15 12:50 ` [PATCH ha-manager v4 04/27] update crm commands: align logging with next state started/stopped Fiona Ebner
2026-10-15 12:50 ` [PATCH ha-manager v4 05/27] manager: factor out helper to check if requested resource motion is valid Fiona Ebner
2026-10-15 12:50 ` [PATCH ha-manager v4 06/27] next state stopped: align logging for motion command with next_state_started() Fiona Ebner
2026-10-15 12:50 ` [PATCH ha-manager v4 07/27] next state {stopped,started}: factor out helper to handle motion command Fiona Ebner
2026-10-15 12:50 ` [PATCH ha-manager v4 08/27] lrm: resource migration: support extra migration options Fiona Ebner
2026-10-15 12:50 ` [PATCH ha-manager v4 09/27] change service state: support hash as a parameter value Fiona Ebner
2026-10-15 12:50 ` [PATCH ha-manager v4 10/27] next state: handle motion command: support migration options Fiona Ebner
2026-10-15 12:50 ` [PATCH ha-manager v4 11/27] resources: add migrate_json_properties() method Fiona Ebner
2026-10-16 9:51 ` Daniel Kral
2026-10-15 12:50 ` [PATCH ha-manager v4 12/27] queue resource motion: support migration options Fiona Ebner
2026-10-15 12:50 ` [PATCH ha-manager v4 13/27] crm command: support JSON-style migrate command Fiona Ebner
2026-10-16 9:53 ` Daniel Kral [this message]
2026-10-15 12:50 ` [PATCH ha-manager v4 14/27] api: resources: migration: support additional migration options Fiona Ebner
2026-10-16 9:54 ` Daniel Kral
2026-10-15 12:50 ` [PATCH ha-manager v4 15/27] test: add test for " Fiona Ebner
2026-10-15 12:50 ` [PATCH qemu-server v4 16/27] helpers: move version_cmp() helper to pve-common Fiona Ebner
2026-10-15 12:50 ` [PATCH qemu-server v4 17/27] helpers: move pvecfg node version helpers to pve-cluster Fiona Ebner
2026-10-15 12:50 ` [PATCH qemu-server v4 18/27] api: migrate: allow forwarding certain migration properties to HA Fiona Ebner
2026-10-15 12:50 ` [PATCH qemu-server v4 19/27] fix #7053: api: migrate: pass 'with-conntrack-state' flag to HA migration Fiona Ebner
2026-10-15 12:50 ` [PATCH qemu-server v4 20/27] qm: mtunnel: reply when a command is unknown Fiona Ebner
2026-10-15 12:50 ` [PATCH qemu-server v4 21/27] qm: mtunnel: add 'conf' command to do strict configuration parsing Fiona Ebner
2026-10-15 12:50 ` [PATCH qemu-server v4 22/27] migration: intra-cluster: check config can be parsed on target node Fiona Ebner
2026-10-15 12:50 ` [PATCH container v4 23/27] api: migrate: allow forwarding certain migration properties to HA Fiona Ebner
2026-10-15 12:50 ` [PATCH container v4 24/27] pct: introduce mtunnel command Fiona Ebner
2026-10-15 12:50 ` [PATCH container v4 25/27] d/control: bump versioned build dependency for libpve-common-perl to 9.0.12 Fiona Ebner
2026-10-15 12:51 ` [PATCH container v4 26/27] migration: intra-cluster: check config can be parsed on target node Fiona Ebner
2026-10-15 12:51 ` [PATCH manager v4 27/27] ui: migrate: add checkbox to allow skipping newly enforced config check Fiona Ebner
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=DM665VFXOXT6.VICV4ZEFVU49@proxmox.com \
--to=d.kral@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox