Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On Thu, Jul 19, 2012 at 6:09 PM, Andreas Kurz andr...@hastexo.com wrote: On 07/19/2012 02:57 PM, Rasto Levrinc wrote: On Thu, Jul 19, 2012 at 2:38 PM, Andreas Kurz andr...@hastexo.com wrote: I don't think it is supported in crm or any other configuration tool syntax for above example in xml looks like: Well, LCMC supports this, btw last time I checked this feature is still not enabled in constrains rng in 1.1.7 by default, so you have to wait at least for 1.1.8, or enable it yourself. It also doesn't work if combined with colocation. cool Rasto :-) ... does LCMC also already support the new multiple stonith-device configuration syntax ... fencing-topology ...? No it doesn't, but it doesn't remove it either. :) It's also something that could use being visualized in a graph, but I am not sure when I'll get around to do this. Rasto -- Dipl.-Ing. Rastislav Levrinc rasto.levr...@gmail.com Linux Cluster Management Console http://lcmc.sf.net/ ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On Jul 19, 2012, at 5:47 AM, Vadym Chepkov wrote: Hi, When Pacemaker 1.1.7 was announced, a new feature was mentioned: The ability to specify that A starts after ( B or C or D ) I wasn't able to find an example how to express it crm shell in neither man crm nor in Pacemaker Explained. In fact, http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-ordering.html doesn't have new attribute listed either. Is it supported in crm ? crm configure help order ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On Jul 19, 2012, at 6:55 AM, Phillip Frost wrote: On Jul 19, 2012, at 5:47 AM, Vadym Chepkov wrote: Hi, When Pacemaker 1.1.7 was announced, a new feature was mentioned: The ability to specify that A starts after ( B or C or D ) I wasn't able to find an example how to express it crm shell in neither man crm nor in Pacemaker Explained. In fact, http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-ordering.html doesn't have new attribute listed either. Is it supported in crm ? crm configure help order Not there either. pacemaker-1.1.7-6.el6.x86_64 This constraint expresses the order of actions on two resources or more resources. If there are more than two resources, then the constraint is called a resource set. Ordered resource sets have an extra attribute to allow for sets of resources whose actions may run in parallel. The shell syntax for such sets is to put resources in parentheses. Usage: ... order id score-type: rsc[:action] rsc[:action] ... [symmetrical=bool] score-type :: advisory | mandatory | score ... Example: ... order c_apache_1 mandatory: apache:start ip_1 order o1 inf: A ( B C ) ... Vadym signature.asc Description: Message signed with OpenPGP using GPGMail ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On Jul 19, 2012, at 7:44 AM, Vadym Chepkov wrote: Not there either. Maybe I'm not understanding your question. Isn't this what you are seeking? Ordered resource sets have an extra attribute to allow for sets of resources whose actions may run in parallel. The shell syntax for such sets is to put resources in parentheses. Example: order o1 inf: A ( B C ) Other examples are: # A, then B, C, D, then E order o2 inf: A B C D E # A, then B and C and D in parallel, then E order o2 inf: A ( B C D ) E If none of that is it, but you can find documentation of what you want in XML, you could try inserting the desired XML into your configuration, then running crm configure show to find the corresponding CRM syntax. ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On 07/19/2012 11:47 AM, Vadym Chepkov wrote: Hi, When Pacemaker 1.1.7 was announced, a new feature was mentioned: The ability to specify that A starts after ( B or C or D ) I wasn't able to find an example how to express it crm shell in neither man crm nor in Pacemaker Explained. In fact, http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-ordering.html doesn't have new attribute listed either. Is it supported in crm ? I don't think it is supported in crm or any other configuration tool syntax for above example in xml looks like: rsc_order id=order-1 resource_set id=req-1 sequential=false require-all=false resource_ref id=B/ resource_ref id=C/ resource_ref id=D/ /resource_set resource_set id=req-2 resource_ref id=A/ /resource_set /rsc_order ... can be found in the pengine regression tests directory in Pacemaker source ... Regards, Andreas -- Need help with Pacemaker? http://www.hastexo.com/now Thanks, Vadym ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org signature.asc Description: OpenPGP digital signature ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On Thu, Jul 19, 2012 at 2:38 PM, Andreas Kurz andr...@hastexo.com wrote: On 07/19/2012 11:47 AM, Vadym Chepkov wrote: Hi, When Pacemaker 1.1.7 was announced, a new feature was mentioned: The ability to specify that A starts after ( B or C or D ) I wasn't able to find an example how to express it crm shell in neither man crm nor in Pacemaker Explained. In fact, http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-ordering.html doesn't have new attribute listed either. Is it supported in crm ? I don't think it is supported in crm or any other configuration tool syntax for above example in xml looks like: Well, LCMC supports this, btw last time I checked this feature is still not enabled in constrains rng in 1.1.7 by default, so you have to wait at least for 1.1.8, or enable it yourself. It also doesn't work if combined with colocation. Rasto rsc_order id=order-1 resource_set id=req-1 sequential=false require-all=false resource_ref id=B/ resource_ref id=C/ resource_ref id=D/ /resource_set resource_set id=req-2 resource_ref id=A/ /resource_set /rsc_order ... can be found in the pengine regression tests directory in Pacemaker source ... -- Dipl.-Ing. Rastislav Levrinc rasto.levr...@gmail.com Linux Cluster Management Console http://lcmc.sf.net/ ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On Jul 19, 2012, at 8:57 AM, Rasto Levrinc wrote: On Thu, Jul 19, 2012 at 2:38 PM, Andreas Kurz andr...@hastexo.com wrote: On 07/19/2012 11:47 AM, Vadym Chepkov wrote: Hi, When Pacemaker 1.1.7 was announced, a new feature was mentioned: The ability to specify that A starts after ( B or C or D ) I wasn't able to find an example how to express it crm shell in neither man crm nor in Pacemaker Explained. In fact, http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-ordering.html doesn't have new attribute listed either. Is it supported in crm ? I don't think it is supported in crm or any other configuration tool syntax for above example in xml looks like: Well, LCMC supports this, btw last time I checked this feature is still not enabled in constrains rng in 1.1.7 by default, so you have to wait at least for 1.1.8, or enable it yourself. It also doesn't work if combined with colocation. Oh, so in other words it's not supported by 1.1.7 ? Why was it in release-notes then? Rasto rsc_order id=order-1 resource_set id=req-1 sequential=false require-all=false resource_ref id=B/ resource_ref id=C/ resource_ref id=D/ /resource_set resource_set id=req-2 resource_ref id=A/ /resource_set /rsc_order ... can be found in the pengine regression tests directory in Pacemaker source ... -- Dipl.-Ing. Rastislav Levrinc rasto.levr...@gmail.com Linux Cluster Management Console http://lcmc.sf.net/ ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On Jul 19, 2012, at 8:16 AM, Phillip Frost wrote: On Jul 19, 2012, at 7:44 AM, Vadym Chepkov wrote: Not there either. Maybe I'm not understanding your question. Isn't this what you are seeking? Ordered resource sets have an extra attribute to allow for sets of resources whose actions may run in parallel. The shell syntax for such sets is to put resources in parentheses. Example: order o1 inf: A ( B C ) Other examples are: # A, then B, C, D, then E order o2 inf: A B C D E # A, then B and C and D in parallel, then E order o2 inf: A ( B C D ) E which translates to A (B and C and D) E compare to A (B or C or D ) E If none of that is it, but you can find documentation of what you want in XML, you could try inserting the desired XML into your configuration, then running crm configure show to find the corresponding CRM syntax. Andreas beat me to it. ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On Jul 19, 2012, at 8:57 AM, Rasto Levrinc wrote: On Thu, Jul 19, 2012 at 2:38 PM, Andreas Kurz andr...@hastexo.com wrote: On 07/19/2012 11:47 AM, Vadym Chepkov wrote: Hi, When Pacemaker 1.1.7 was announced, a new feature was mentioned: The ability to specify that A starts after ( B or C or D ) I wasn't able to find an example how to express it crm shell in neither man crm nor in Pacemaker Explained. In fact, http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-ordering.html doesn't have new attribute listed either. Is it supported in crm ? I don't think it is supported in crm or any other configuration tool syntax for above example in xml looks like: Well, LCMC supports this, btw last time I checked this feature is still not enabled in constrains rng in 1.1.7 by default, so you have to wait at least for 1.1.8, or enable it yourself. It also doesn't work if combined with colocation I presume it doesn't work if score is INFINITY ? Otherwise it would be strange. Rasto rsc_order id=order-1 resource_set id=req-1 sequential=false require-all=false resource_ref id=B/ resource_ref id=C/ resource_ref id=D/ /resource_set resource_set id=req-2 resource_ref id=A/ /resource_set /rsc_order ... can be found in the pengine regression tests directory in Pacemaker source ... -- Dipl.-Ing. Rastislav Levrinc rasto.levr...@gmail.com Linux Cluster Management Console http://lcmc.sf.net/ ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On 2012-07-19T09:41:55, Vadym Chepkov vchep...@gmail.com wrote: Oh, so in other words it's not supported by 1.1.7 ? Why was it in release-notes then? Pacemaker supports it, but not yet the shell/hawk. Regards, Lars -- Architect Storage/HA SUSE LINUX Products 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 ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On Thu, Jul 19, 2012 at 4:13 PM, Lars Marowsky-Bree l...@suse.com wrote: On 2012-07-19T09:41:55, Vadym Chepkov vchep...@gmail.com wrote: Oh, so in other words it's not supported by 1.1.7 ? Why was it in release-notes then? Pacemaker supports it, but not yet the shell/hawk. ... nor cibadmin :) Rasto Regards, Lars -- Architect Storage/HA SUSE LINUX Products 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 ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org -- Dipl.-Ing. Rastislav Levrinc rasto.levr...@gmail.com Linux Cluster Management Console http://lcmc.sf.net/ ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On Thu, Jul 19, 2012 at 3:46 PM, Vadym Chepkov vchep...@gmail.com wrote: On Jul 19, 2012, at 8:57 AM, Rasto Levrinc wrote: On Thu, Jul 19, 2012 at 2:38 PM, Andreas Kurz andr...@hastexo.com wrote: On 07/19/2012 11:47 AM, Vadym Chepkov wrote: Hi, When Pacemaker 1.1.7 was announced, a new feature was mentioned: The ability to specify that A starts after ( B or C or D ) I wasn't able to find an example how to express it crm shell in neither man crm nor in Pacemaker Explained. In fact, http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-ordering.html doesn't have new attribute listed either. Is it supported in crm ? I don't think it is supported in crm or any other configuration tool syntax for above example in xml looks like: Well, LCMC supports this, btw last time I checked this feature is still not enabled in constrains rng in 1.1.7 by default, so you have to wait at least for 1.1.8, or enable it yourself. It also doesn't work if combined with colocation I presume it doesn't work if score is INFINITY ? Otherwise it would be strange. It doesn't work with any score. It's not strange just a missing feature. Rasto Rasto rsc_order id=order-1 resource_set id=req-1 sequential=false require-all=false resource_ref id=B/ resource_ref id=C/ resource_ref id=D/ /resource_set resource_set id=req-2 resource_ref id=A/ /resource_set /rsc_order ... can be found in the pengine regression tests directory in Pacemaker source ... -- Dipl.-Ing. Rastislav Levrinc rasto.levr...@gmail.com Linux Cluster Management Console http://lcmc.sf.net/ ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org -- Dipl.-Ing. Rastislav Levrinc rasto.levr...@gmail.com Linux Cluster Management Console http://lcmc.sf.net/ ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On 07/19/2012 02:57 PM, Rasto Levrinc wrote: On Thu, Jul 19, 2012 at 2:38 PM, Andreas Kurz andr...@hastexo.com wrote: On 07/19/2012 11:47 AM, Vadym Chepkov wrote: Hi, When Pacemaker 1.1.7 was announced, a new feature was mentioned: The ability to specify that A starts after ( B or C or D ) I wasn't able to find an example how to express it crm shell in neither man crm nor in Pacemaker Explained. In fact, http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-ordering.html doesn't have new attribute listed either. Is it supported in crm ? I don't think it is supported in crm or any other configuration tool syntax for above example in xml looks like: Well, LCMC supports this, btw last time I checked this feature is still not enabled in constrains rng in 1.1.7 by default, so you have to wait at least for 1.1.8, or enable it yourself. It also doesn't work if combined with colocation. cool Rasto :-) ... does LCMC also already support the new multiple stonith-device configuration syntax ... fencing-topology ...? Cheers, Andreas Rasto rsc_order id=order-1 resource_set id=req-1 sequential=false require-all=false resource_ref id=B/ resource_ref id=C/ resource_ref id=D/ /resource_set resource_set id=req-2 resource_ref id=A/ /resource_set /rsc_order ... can be found in the pengine regression tests directory in Pacemaker source ... -- Need help with Pacemaker? http://www.hastexo.com/now signature.asc Description: OpenPGP digital signature ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On Thu, Jul 19, 2012 at 10:57 PM, Rasto Levrinc rasto.levr...@gmail.com wrote: On Thu, Jul 19, 2012 at 2:38 PM, Andreas Kurz andr...@hastexo.com wrote: On 07/19/2012 11:47 AM, Vadym Chepkov wrote: Hi, When Pacemaker 1.1.7 was announced, a new feature was mentioned: The ability to specify that A starts after ( B or C or D ) I wasn't able to find an example how to express it crm shell in neither man crm nor in Pacemaker Explained. In fact, http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-ordering.html doesn't have new attribute listed either. Is it supported in crm ? I don't think it is supported in crm or any other configuration tool syntax for above example in xml looks like: Well, LCMC supports this, btw last time I checked this feature is still not enabled in constrains rng in 1.1.7 by default, so you have to wait at least for 1.1.8, or enable it yourself. It also doesn't work if combined with colocation. I've just now promoted it to 1.2. Thanks for the reminder. Rasto rsc_order id=order-1 resource_set id=req-1 sequential=false require-all=false resource_ref id=B/ resource_ref id=C/ resource_ref id=D/ /resource_set resource_set id=req-2 resource_ref id=A/ /resource_set /rsc_order ... can be found in the pengine regression tests directory in Pacemaker source ... -- Dipl.-Ing. Rastislav Levrinc rasto.levr...@gmail.com Linux Cluster Management Console http://lcmc.sf.net/ ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On Thu, Jul 19, 2012 at 11:41 PM, Vadym Chepkov vchep...@gmail.com wrote: On Jul 19, 2012, at 8:57 AM, Rasto Levrinc wrote: On Thu, Jul 19, 2012 at 2:38 PM, Andreas Kurz andr...@hastexo.com wrote: On 07/19/2012 11:47 AM, Vadym Chepkov wrote: Hi, When Pacemaker 1.1.7 was announced, a new feature was mentioned: The ability to specify that A starts after ( B or C or D ) I wasn't able to find an example how to express it crm shell in neither man crm nor in Pacemaker Explained. In fact, http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-ordering.html doesn't have new attribute listed either. Is it supported in crm ? I don't think it is supported in crm or any other configuration tool syntax for above example in xml looks like: Well, LCMC supports this, btw last time I checked this feature is still not enabled in constrains rng in 1.1.7 by default, so you have to wait at least for 1.1.8, or enable it yourself. It also doesn't work if combined with colocation. Oh, so in other words it's not supported by 1.1.7 ? Why was it in release-notes then? It is supported, you just need to enable the experimental schema. Its where we trial the syntax for new features until we're 100% happy with it. See http://theclusterguy.clusterlabs.org/post/441442543/new-pacemaker-release-series ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] Pacemaker 1.1.7 order constraint syntax
On Fri, Jul 20, 2012 at 12:27 AM, Rasto Levrinc rasto.levr...@gmail.com wrote: On Thu, Jul 19, 2012 at 4:13 PM, Lars Marowsky-Bree l...@suse.com wrote: On 2012-07-19T09:41:55, Vadym Chepkov vchep...@gmail.com wrote: Oh, so in other words it's not supported by 1.1.7 ? Why was it in release-notes then? Pacemaker supports it, but not yet the shell/hawk. ... nor cibadmin :) cibadmin supports it, as long as you enabled the experimental schema. cibadmin is stupid, it has no understanding of what you're trying to put into the cib ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
