[Pacemaker] Question about new migration

Kazunori INOUE kazunori.inoue3 at gmail.com
Wed Jan 15 03:12:04 EST 2014


Hi David,

With new migration logic, when VM was migrated by 'node standby',
start was performed in migrate_target. (migrate_from was not performed.)

Is this the designed behavior?


# crm_mon -rf1
Stack: corosync
Current DC: bl460g1n6 (3232261592) - partition with quorum
Version: 1.1.11-0.27.b48276b.git.el6-b48276b
2 Nodes configured
3 Resources configured

Online: [ bl460g1n6 bl460g1n7 ]

Full list of resources:

prmVM2  (ocf::heartbeat:VirtualDomain): Started bl460g1n6
 Clone Set: clnPing [prmPing]
     Started: [ bl460g1n6 bl460g1n7 ]

Node Attributes:
* Node bl460g1n6:
    + default_ping_set                  : 100
* Node bl460g1n7:
    + default_ping_set                  : 100

# crm node standby bl460g1n6
# egrep "do_lrm_rsc_op:|process_lrm_event:" ha-log | grep prmVM2
Jan 15 15:39:22 bl460g1n6 crmd[30795]:     info: do_lrm_rsc_op:
Performing key=11:5:0:be72ea63-75a9-4de4-a591-e716f960743b
op=prmVM2_migrate_to_0
Jan 15 15:39:28 bl460g1n6 crmd[30795]:   notice: process_lrm_event:
LRM operation prmVM2_migrate_to_0 (call=16, rc=0, cib-update=66,
confirmed=true) ok
Jan 15 15:39:30 bl460g1n6 crmd[30795]:     info: do_lrm_rsc_op:
Performing key=7:6:0:be72ea63-75a9-4de4-a591-e716f960743b
op=prmVM2_stop_0
Jan 15 15:39:30 bl460g1n6 crmd[30795]:   notice: process_lrm_event:
LRM operation prmVM2_stop_0 (call=19, rc=0, cib-update=68,
confirmed=true) ok

Jan 15 15:39:30 bl460g1n7 crmd[29923]:     info: do_lrm_rsc_op:
Performing key=8:6:0:be72ea63-75a9-4de4-a591-e716f960743b
op=prmVM2_start_0
Jan 15 15:39:30 bl460g1n7 crmd[29923]:   notice: process_lrm_event:
LRM operation prmVM2_start_0 (call=13, rc=0, cib-update=17,
confirmed=true) ok


Best Regards,
Kazunori INOUE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pcmk-Wed-15-Jan-2014.tar.bz2
Type: application/x-bzip2
Size: 187208 bytes
Desc: not available
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140115/1ef4a50d/attachment-0002.bz2>


More information about the Pacemaker mailing list