blob: c7ef3e0e12cdd94883a654e993275c624e349142 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
Current cluster status:
* Node List:
* Node xen-a: standby (with active resources)
* Online: [ xen-b ]
* Full List of Resources:
* xen-a-fencing (stonith:external/ipmi): Started xen-b
* xen-b-fencing (stonith:external/ipmi): Started xen-a
* db (ocf:heartbeat:Xen): Started xen-a
* dbreplica (ocf:heartbeat:Xen): Started xen-b
* core-101 (ocf:heartbeat:Xen): Started xen-a
* core-200 (ocf:heartbeat:Xen): Started xen-a
* sysadmin (ocf:heartbeat:Xen): Started xen-b
* edge (ocf:heartbeat:Xen): Started xen-a
* base (ocf:heartbeat:Xen): Started xen-a
* Email_Alerting (ocf:heartbeat:MailTo): Started xen-b
Transition Summary:
* Restart xen-a-fencing ( xen-b ) due to resource definition change
* Stop xen-b-fencing ( xen-a ) due to node availability
* Migrate db ( xen-a -> xen-b )
* Migrate core-101 ( xen-a -> xen-b )
* Migrate core-200 ( xen-a -> xen-b )
* Migrate edge ( xen-a -> xen-b )
* Migrate base ( xen-a -> xen-b )
Executing Cluster Transition:
* Resource action: xen-a-fencing stop on xen-b
* Resource action: xen-a-fencing start on xen-b
* Resource action: xen-a-fencing monitor=60000 on xen-b
* Resource action: xen-b-fencing stop on xen-a
* Resource action: db migrate_to on xen-a
* Resource action: core-101 migrate_to on xen-a
* Resource action: edge migrate_to on xen-a
* Resource action: db migrate_from on xen-b
* Resource action: db stop on xen-a
* Resource action: core-101 migrate_from on xen-b
* Resource action: core-101 stop on xen-a
* Resource action: core-200 migrate_to on xen-a
* Resource action: edge migrate_from on xen-b
* Resource action: edge stop on xen-a
* Resource action: base migrate_to on xen-a
* Pseudo action: db_start_0
* Pseudo action: core-101_start_0
* Resource action: core-200 migrate_from on xen-b
* Resource action: core-200 stop on xen-a
* Pseudo action: edge_start_0
* Resource action: base migrate_from on xen-b
* Resource action: base stop on xen-a
* Resource action: db monitor=10000 on xen-b
* Resource action: core-101 monitor=10000 on xen-b
* Pseudo action: core-200_start_0
* Resource action: edge monitor=10000 on xen-b
* Pseudo action: base_start_0
* Resource action: core-200 monitor=10000 on xen-b
* Resource action: base monitor=10000 on xen-b
Revised Cluster Status:
* Node List:
* Node xen-a: standby
* Online: [ xen-b ]
* Full List of Resources:
* xen-a-fencing (stonith:external/ipmi): Started xen-b
* xen-b-fencing (stonith:external/ipmi): Stopped
* db (ocf:heartbeat:Xen): Started xen-b
* dbreplica (ocf:heartbeat:Xen): Started xen-b
* core-101 (ocf:heartbeat:Xen): Started xen-b
* core-200 (ocf:heartbeat:Xen): Started xen-b
* sysadmin (ocf:heartbeat:Xen): Started xen-b
* edge (ocf:heartbeat:Xen): Started xen-b
* base (ocf:heartbeat:Xen): Started xen-b
* Email_Alerting (ocf:heartbeat:MailTo): Started xen-b
|
