Re: [Linux-HA] Antw: Question around resources constraints (pacemaker on RHE7.1)
On 25 Aug 2015, at 6:18 pm, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote: MOULLE, ALAIN alain.mou...@atos.net schrieb am 21.08.2015 um 15:27 in Nachricht df84cff8a85ab546b2d53fff12267727022...@frauvj99ex5msx.ww931.my-it-solutions.net : Hi I can't find a way to configure constraints in pacemaker so that with these resources: Res1 Res2 Res3 Res4 Res5 with current colocation constraints : Res2 with Res1 Res3 with Res2 I think pacemaker still cannot do transitive location constraints; ? can you try R2 with R1 R3 with R1 (and related) instead? No no no. This has the opposite effect, a failure of R3 could easily result in /none/ of the resources moving. Better to just change: Res4 with Res1 to: Res4 with Res3 Newer versions might do better with the existing config too. If not, attach a crm_report :) Res5 with Res4 and current order symmetrical constraints : Res2 after Res1 Res3 after Res2 Res4 after Res1 Res5 after Res4 and migration-threshold=1 on all resources . What I want it that if I have a failure for example on Res3 is that all the 5 Ressources are migrated. Is there a solution ? For example , with an HA LVM configuration and VM resources : Res1=VGA Res2=FS-img-VM1 (where are the VM1 image and .xml) (FS-img-VM1 is on VGA LV) Res3=VM1 Res4=FS-img-VM2 (where are the VM2 image and .xml) (FS-img-VM1 is on another VGA LV) Res5=VM2 So current constraints are so that VGA is activated before the FS-img is mounted and before the VM is started. But I want that if the VM1 fails, it can migrate on another node (together with all other 4 resources) but with only the constraints above, the VGA stalls the migration of the VM ... Is there any solution by constraints configuration ? Note : we can't use group resources for now, because VMs are remote-nodes. Thanks Alain Moullé ___ Linux-HA mailing list is closing down. Please subscribe to us...@clusterlabs.org instead. http://clusterlabs.org/mailman/listinfo/users ___ Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha ___ Linux-HA mailing list is closing down. Please subscribe to us...@clusterlabs.org instead. http://clusterlabs.org/mailman/listinfo/users ___ Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha ___ Linux-HA mailing list is closing down. Please subscribe to us...@clusterlabs.org instead. http://clusterlabs.org/mailman/listinfo/users ___ Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha
Re: [Linux-HA] Antw: Question around resources constraints (pacemaker on RHE7.1)
Hi Thanks, I just tried : colocation fs-img with vg colocation vm with vg but the problem remains : if the vm fails, it is not migrated despite the migration-threshold=1, as the vg remains Started locally and has no problem. In fact, I would need a parameter to force the vg to move in case of vm or fs-img failure, but I think it is not possible for now ... Alain De : linux-ha-boun...@lists.linux-ha.org [linux-ha-boun...@lists.linux-ha.org] de la part de Ulrich Windl [ulrich.wi...@rz.uni-regensburg.de] Envoyé : mardi 25 août 2015 10:18 À : General Linux-HA mailing list Objet : [Linux-HA] Antw: Question around resources constraints (pacemaker on RHE7.1) MOULLE, ALAIN alain.mou...@atos.net schrieb am 21.08.2015 um 15:27 in Nachricht df84cff8a85ab546b2d53fff12267727022...@frauvj99ex5msx.ww931.my-it-solutions.net : Hi I can't find a way to configure constraints in pacemaker so that with these resources: Res1 Res2 Res3 Res4 Res5 with current colocation constraints : Res2 with Res1 Res3 with Res2 I think pacemaker still cannot do transitive location constraints; can you try R2 with R1 R3 with R1 (and related) instead? Res4 with Res1 Res5 with Res4 and current order symmetrical constraints : Res2 after Res1 Res3 after Res2 Res4 after Res1 Res5 after Res4 and migration-threshold=1 on all resources . What I want it that if I have a failure for example on Res3 is that all the 5 Ressources are migrated. Is there a solution ? For example , with an HA LVM configuration and VM resources : Res1=VGA Res2=FS-img-VM1 (where are the VM1 image and .xml) (FS-img-VM1 is on VGA LV) Res3=VM1 Res4=FS-img-VM2 (where are the VM2 image and .xml) (FS-img-VM1 is on another VGA LV) Res5=VM2 So current constraints are so that VGA is activated before the FS-img is mounted and before the VM is started. But I want that if the VM1 fails, it can migrate on another node (together with all other 4 resources) but with only the constraints above, the VGA stalls the migration of the VM ... Is there any solution by constraints configuration ? Note : we can't use group resources for now, because VMs are remote-nodes. Thanks Alain Moullé ___ Linux-HA mailing list is closing down. Please subscribe to us...@clusterlabs.org instead. http://clusterlabs.org/mailman/listinfo/users ___ Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha ___ Linux-HA mailing list is closing down. Please subscribe to us...@clusterlabs.org instead. http://clusterlabs.org/mailman/listinfo/users ___ Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha ___ Linux-HA mailing list is closing down. Please subscribe to us...@clusterlabs.org instead. http://clusterlabs.org/mailman/listinfo/users ___ Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha
Re: [Linux-HA] Antw: Question around resources constraints (pacemaker on RHE7.1)
Hi Sorry, I must admit that the cause of the problem was due to some resources configured inside vm (remote-node) and which take much too long to stop . Now that this is fixed, a vm crash leads to migration of the vm resource and all the resources linked to the same VG. Thanks Alain De : MOULLE, ALAIN Envoyé : mardi 25 août 2015 10:50 À : Please subscribe to us...@clusterlabs.org instead Objet : RE:[Linux-HA] Antw: Question around resources constraints (pacemaker on RHE7.1) Hi Thanks, I just tried : colocation fs-img with vg colocation vm with vg but the problem remains : if the vm fails, it is not migrated despite the migration-threshold=1, as the vg remains Started locally and has no problem. In fact, I would need a parameter to force the vg to move in case of vm or fs-img failure, but I think it is not possible for now ... Alain De : linux-ha-boun...@lists.linux-ha.org [linux-ha-boun...@lists.linux-ha.org] de la part de Ulrich Windl [ulrich.wi...@rz.uni-regensburg.de] Envoyé : mardi 25 août 2015 10:18 À : General Linux-HA mailing list Objet : [Linux-HA] Antw: Question around resources constraints (pacemaker on RHE7.1) MOULLE, ALAIN alain.mou...@atos.net schrieb am 21.08.2015 um 15:27 in Nachricht df84cff8a85ab546b2d53fff12267727022...@frauvj99ex5msx.ww931.my-it-solutions.net : Hi I can't find a way to configure constraints in pacemaker so that with these resources: Res1 Res2 Res3 Res4 Res5 with current colocation constraints : Res2 with Res1 Res3 with Res2 I think pacemaker still cannot do transitive location constraints; can you try R2 with R1 R3 with R1 (and related) instead? Res4 with Res1 Res5 with Res4 and current order symmetrical constraints : Res2 after Res1 Res3 after Res2 Res4 after Res1 Res5 after Res4 and migration-threshold=1 on all resources . What I want it that if I have a failure for example on Res3 is that all the 5 Ressources are migrated. Is there a solution ? For example , with an HA LVM configuration and VM resources : Res1=VGA Res2=FS-img-VM1 (where are the VM1 image and .xml) (FS-img-VM1 is on VGA LV) Res3=VM1 Res4=FS-img-VM2 (where are the VM2 image and .xml) (FS-img-VM1 is on another VGA LV) Res5=VM2 So current constraints are so that VGA is activated before the FS-img is mounted and before the VM is started. But I want that if the VM1 fails, it can migrate on another node (together with all other 4 resources) but with only the constraints above, the VGA stalls the migration of the VM ... Is there any solution by constraints configuration ? Note : we can't use group resources for now, because VMs are remote-nodes. Thanks Alain Moullé ___ Linux-HA mailing list is closing down. Please subscribe to us...@clusterlabs.org instead. http://clusterlabs.org/mailman/listinfo/users ___ Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha ___ Linux-HA mailing list is closing down. Please subscribe to us...@clusterlabs.org instead. http://clusterlabs.org/mailman/listinfo/users ___ Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha ___ Linux-HA mailing list is closing down. Please subscribe to us...@clusterlabs.org instead. http://clusterlabs.org/mailman/listinfo/users ___ Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha
