Proxmox/pve-ha-manager
5
0
Fork 0
mirror of git://git.proxmox.com/git/pve-ha-manager.git synced 2024-12-22 17:34:22 +03:00
Code Releases Activity

remove crm 'move' state

Browse Source
This commit is contained in:
Dietmar Maurer 2015-02-16 10:31:41 +01:00
parent e4ffb2996c
commit 2d7a098397
2 changed files with 3 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
PVE/HA/Manager.pm
View File

@ -71,7 +71,6 @@ my $valid_service_states = {
request_stop => 1,
started => 1,
fence => 1,
move => 1,
migrate => 1,
error => 1,
};
@ -225,10 +224,6 @@ sub manage {
}
}
} elsif ($last_state eq 'move') {
#die "implement me";
} elsif ($last_state eq 'fence') {
# do nothing here - wait until fenced

11
README
View File

@ -72,14 +72,9 @@ Some services like Qemu Virtual Machines supports live migration.
So the LRM can migrate those services without stopping them (CRM
service state 'migrate'),
Most other service types requires the service to be stopped, and
then restarted at the other node. We use the following CRM service
states transitions: 'relocate_stop' => 'relocate_move' => 'started'
Stopped services are moved using service state 'move'. It has to be
noted that service relocation is always done using the LRM (the LRM
'owns' the service), unless a node is fenced. In that case the CRM
is allowed to 'steal' the resource and mode it to another node.
Most other service types requires the service to be stopped, and then
restarted at the other node. Stopped services are moved by the CRM
(usually by simply changing the service configuration).
=== Possible CRM Service States ===