From 2d7a098397f0790d585fe272c0f2795a86d32274 Mon Sep 17 00:00:00 2001
From: Dietmar Maurer <dietmar@proxmox.com>
Date: Mon, 16 Feb 2015 10:31:41 +0100
Subject: [PATCH] remove crm 'move' state

---
 PVE/HA/Manager.pm |  5 -----
 README            | 11 +++--------
 2 files changed, 3 insertions(+), 13 deletions(-)

diff --git a/PVE/HA/Manager.pm b/PVE/HA/Manager.pm
index ab7d715..6c5e0ca 100644
--- a/PVE/HA/Manager.pm
+++ b/PVE/HA/Manager.pm
@@ -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
diff --git a/README b/README
index 0d73d25..20f234f 100644
--- a/README
+++ b/README
@@ -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 ===