[RFC PATCH-SERIES qemu-server 0/1] fix #7053: allow setting additional HA migration parameters

[Daniel Kral <d.kral@proxmox.com>]

Bugzilla #7053 reports that even though 'with-conntrack-state' is
checked, the VM will always migrate without conntrack state in the end.

In fact, any parameters from the migrate_vm API endpoint but the $vmid
and $node are not passed on to the HA stack at all. This was likely
caught now, because the conntrack state is the only optional parameter
visible in the web interface and set by default.



Currently, the resource motion crm command is matched from ^ to $:

    if ($cmd =~ m/^(migrate|relocate)\s+(\S+)\s+(\S+)$/) {

We could extend that crm command to something like:

    if ($cmd =~ m/^(migrate|relocate)\s+(\S+)\s+(\S+)(?:\s+(\S.*))?$/) {

but this would need the newer `ha-manager {migrate,relocate} ...`
API/CLI endpoint to append both the standard and extended version for
some period as older HA Manager versions wouldn't be able to parse the
extended version but only the standard versions. Newer HA Manager
versions would be fine though, as first the standard version would be
parsed and afterwards the extended version would overwrite the request
from the standard version.

The downside from this though is that the migration parameters are not
the same for VMs and CTs (and possible future resource types) and would
therefore expose quite a lot of resource-specific data structures to the
more generic HA Manager code.

Additionally, both the node with the active HA Manager as well as the
node's LRM where the to-be-moved HA resource is on need to have the
newer pve-ha-manager version to correctly relay the migration
parameters.



As the migrate_vm API request is proxied to the node where the HA
resource is assigned to, this RFC patch series puts the responsibility
to handle the additional migration parameters at the caller's side,
where these are saved while the request is relayed through the HA stack
until the LRM on the node calls migrate_vm again.

The implementation is not fully fleshed out (e.g. cleaning up the
migration params file on a crashed/stopped VM or rejected migration
requests, etc.), but I wanted to get more feedback whether this solution
has any merit and if not decide on another possible solution.

If it does have merit, this could be generalized for both qemu-server
and pve-container if it useful for containers as well.


qemu-server:

Daniel Kral (1):
  fix #7053: api: migrate: save and restore migration params for HA
    managed VMs

 src/PVE/API2/Qemu.pm | 54 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 54 insertions(+)


Summary over all repositories:
  1 files changed, 54 insertions(+), 0 deletions(-)

-- 
Generated by murpp 0.9.0