On 2014-11-27T10:10:47, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote:
Hi!
I had thought ordrring of clones would work, but it looks like it does not in
current SLES11 SP3 (1.1.11-3ca8c3b):
I have rules like:
order ord_DLM_O2CB inf: cln_DLM cln_O2CB
order ord_DLM_cLVMd inf: cln_DLM cln_cLVMd
colocation col_O2CB_DLM inf: cln_O2CB cln_DLM
colocation col_cLVMd_DLM inf: cln_cLVMd cln_DLM
I thought the instances on one node would start DLM first, then in parallel
(optimally) O2CB and cLVMd.
Correct.
When adding a new node to the cluster, all three instances were started at
the same time:
Nov 25 12:37:18 h05 pengine[15681]: notice: LogActions: Start prm_cLVMd:2
(h10)
Nov 25 12:37:18 h05 pengine[15681]: notice: LogActions: Start
prm_LVM_CFS_VMs:2(h10)
Nov 25 12:37:18 h05 pengine[15681]: notice: LogActions: Start prm_O2CB:2
(h10)
Nov 25 12:37:18 h05 pengine[15681]: notice: LogActions: Start
prm_CFS_VMs_fs:2 (h10)
This is the PE *scheduling* the resources to be started. It's not the
actual ordering. It's just telling you that the resources will be
started during this transition.
You need to check either the transition graph (crm configure simulate),
or look at the actual sequence of commands the LRM executes.
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284
(AG Nürnberg)
Experience is the name everyone gives to their mistakes. -- Oscar Wilde
___
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/