Hi, thanks for the response. Please see inline replies. Note, this is part of an automated test. It normal works, but will usually file 1 in 20 tries for me. The point is that it¹s intermittent.
Gene On 4/8/14, 3:38 PM, "Chris Feist" <cfe...@redhat.com> wrote: >On 03/24/2014 08:55 PM, Naoya Anzai wrote: >> Hi all, >> >> I'm using pcs 0.9.115 on fedora 20. > >Which version of the pcs rpm are you using? (rpm -q pcs) [~]# rpm -q pcs pcs-0.9.90-2.el6.centos.2.noarch > >This issues has been recently been fixed, but there may not yet be a >fedora build. Interesting. Here is what yum says [~]# yum info pcs Installed Packages Name : pcs Arch : noarch Version : 0.9.90 Release : 2.el6.centos.2 Size : 463 k Repo : installed >From repo : CentOS-6.5-updates-x86_64 Summary : Pacemaker Configuration System URL : http://github.com/feist/pcs License : GPLv2 Description : pcs is a corosync and pacemaker configuration tool. It permits users to : easily view, modify and created pacemaker based clusters. > >Thanks, >Chris > >> >> --- >> [root@saturn ~]# pcs --version >> 0.9.115 >> [root@saturn ~]# cat /etc/redhat-release >> Fedora release 20 (Heisenbug) >> --- >> >> I want to add locational rule property "boolean-op" using pcs, >> but this pcs seems it does not be implemented... >> >> --- >> [root@saturn ~]# pcs -f pgsql_cfg constraint location vip-backup rule >>score="-INFINITY" pgsql-status ne "HS:sync" and pgsql-status ne "PRI" >> [root@saturn ~]# pcs -f pgsql_cfg constraint location --full >> Location Constraints: >> Resource: vip-backup >> Constraint: location-vip-backup >> Rule: score=-INFINITY (id:location-vip-backup-rule) >> Expression: pgsql-status ne HS:sync >>(id:location-vip-backup-rule-expr) >> [root@saturn ~]# cat pgsql_cfg|grep -e location-vip-backup-rule -A2 -B1 >> <rsc_location id="location-vip-backup" rsc="vip-backup"> >> <rule id="location-vip-backup-rule" score="-INFINITY"> >> <expression attribute="pgsql-status" >>id="location-vip-backup-rule-expr" operation="ne" value="HS:sync"/> >> </rule> >> </rsc_location> >> --- >> >> If this feature is implemented, can anybody teach me how to use? >> >> Incidentally, >> By editing the xml file directly, it can read and load correctly. >> --- >> #After edit pgsql_cfg >> [root@saturn ~]# pcs -f pgsql_cfg constraint location --full >> Location Constraints: >> Resource: vip-backup >> Constraint: location-vip-backup >> Rule: score=-INFINITY boolean-op=and >>(id:location-vip-backup-rule) >> Expression: pgsql-status ne HS:sync >>(id:location-vip-backup-rule-expr) >> Expression: pgsql-status ne PRI >>(id:location-vip-backup-rule-expr-1) >> --- >> >> Regards, >> >> Naoya >> >> --- >> Naoya Anzai >> Engineering Department >> NEC Soft, Ltd. >> E-Mail: anzai-na...@mxu.nes.nec.co.jp >> --- >> >> >> _______________________________________________ >> 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 _______________________________________________ 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
