Hi all,
I've got two group of resources, say A and B. Suppose this is the situation:

group A:

colocation B_ON_B_ms-r1 inf: ( B_ip ) ( B_iscsitarget-lun ) ( 
B_iscsitarget-export ) B_ms-r1:Master
order B_AFTER_B_ms-r1 inf: B_ms-r1:promote ( B_iscsitarget-export:start 
) ( B_iscsitarget-lun:start ) ( B_ip:start )

group B:

colocation A_ON_A_ms-r0 inf: ( A_ip ) ( A_fs ) ( A_db-fs ) ( A_iscsi-db 
) A_ms-r0:Master
order A_AFTER_A_ms-r0 inf: A_ms-r0:promote ( A_iscsi-db:start ) ( 
A_db-fs:start ) ( A_fs:start ) ( A_ip:start )

The point is that both resources can reside on different nodes, but A 
depends on B, so I want that if B switch, then A must be stopped, then B 
must be started and after that A is restarted.
I've declared this order constraint, but it doesn't do what I'm expecting:

order A_after_B inf: ( B_iscsitarget-export:start ) ( 
B_iscsitarget-lun:start ) ( B_ip:start ) ( A_iscsi-db:start ) ( 
A_db-fs:start ) ( A_fs:start ) ( A_ip:start )

What am I missing?

Thanks a lot!

-- 
Raoul Scarazzini
Mia Mamma Usa Linux: Niente รจ impossibile da capire, se lo spieghi bene!
[email protected]

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to