Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Wed, Nov 24, 2010 at 08:38:41AM -0500, Vadym Chepkov wrote: >> primitive res-Wmysql3-IP ocf:heartbeat:IPaddr2 \ >> meta target-role="started" \ >> operations $id="res-Wmysql3-IP-operations" \ >> op monitor interval="10s" timeout="20s" \ >> params ip ip="10.99.212.247" > > Doesn't look right, seems crm missed it fixed >> colocation col-Ip-Drbd +inf: ms-Drbd-R0 res-Wmysql3-IP > > This one is wrong, by the way, should be > > colocation col-Ip-Drbd inf: ms-Drbd-R0:Master res-Wmysql3-IP:Started This seems to fix the problem. > >> order ord-Ip-Drbd +inf: res-Wmysql3-IP ms-Drbd-R0 > > Same with this one: > order ord-Ip-Drbd inf: res-Wmysql3-IP ms-Drbd-R0:Master This doesn't work: crm flags it as a syntax error. > By the way, I would simplify the config. > > group mysql res-Wmysql3-IP res-Wmysql3-Fs res-Mysql > colocation col-mysql inf: mysql ms-Drbd-R0:Master > order ord-mysql inf: ms-Drbd-R0:promote mysql:start > > This is all you need for this case But in this case, you have res-Wmysql3-Fs only in the group; does this guarantee that res-Wmysql3-Fs gets, as it were, inserted into the order rule? I know that the resources in the group are started in the order given, and colocation is implied. In that case, wouldn't it be just as simple -- and perhaps more logical -- to have this: group mysql res-Wmysql3-IP res-Wmysql3-Fs res-Mysql colocation col-Drbd-Fs inf: res-Wmysql3-Fs ms-Drbd-R0:Master order ord-Drbd-Fs inf: ms-Drbd-R0:promote res-Wmysql3-Fs:start Anyway, thanks for solving the real problem. -- Owen