The name is misleading, because the HA resource migration is not executed, but only queues the HA resource to change into the state 'migrate' or 'relocate', which is then picked up by the respective LRM to execute.
The term 'resource motion' also generalizes the different actions implied by the 'migrate' and 'relocate' command and state. Signed-off-by: Daniel Kral <[email protected]> --- src/PVE/HA/Manager.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/PVE/HA/Manager.pm b/src/PVE/HA/Manager.pm index fc0e7fc2..fd71ec44 100644 --- a/src/PVE/HA/Manager.pm +++ b/src/PVE/HA/Manager.pm @@ -408,7 +408,7 @@ sub read_lrm_status { return ($results, $modes); } -sub execute_migration { +sub queue_resource_motion { my ($self, $cmd, $task, $sid, $target) = @_; my ($haenv, $ss) = $self->@{qw(haenv ss)}; @@ -477,7 +477,7 @@ sub update_crm_commands { "ignore crm command - service already on target node: $cmd", ); } else { - $self->execute_migration($cmd, $task, $sid, $node); + $self->queue_resource_motion($cmd, $task, $sid, $node); } } } else { -- 2.47.3
