Mailing List Archive: [crmsh] Question about latest crmsh.

[crmsh] Question about latest crmsh.

renayama19661014 at ybb

Nov 27, 2014, 8:48 PM

Post #1 of 3 (1197 views)

Hi All,

We used the latest edition of crmsh-b932826fb4f924137eab9efd13b7bddf8afde3f0 with Pacamerk1.1.12.
We sent the following CLI file.

-------------------------------------------
## Cluster Option ###
property no-quorum-policy="ignore" \
stonith-enabled="false"

### Resource Defaults ###
rsc_defaults resource-stickiness="INFINITY" \
migration-threshold="1"

primitive prmDummy1 ocf:pacemaker:Dummy \
op start interval="0s" timeout="300s" on-fail="restart" \
op monitor interval="10s" timeout="60s" on-fail="restart" \
op stop interval="0s" timeout="300s" on-fail="block"

primitive prmDummy2 ocf:heartbeat:Dummy \
op start interval="0s" timeout="300s" on-fail="restart" \
op monitor interval="10s" timeout="60s" on-fail="restart" \
op stop interval="0s" timeout="300s" on-fail="block"

### Resource Location ###
location rsc_location-1 prmDummy1 \
rule $role=master 300: #uname eq snmp1 \
rule $role=master 200: #uname eq snmp2
location rsc_location-2 prmDummy2 \
rule $role=master 300: #uname eq snmp1 \
rule $role=master 200: #uname eq snmp2
-------------------------------------------

Pacemkaer constituted a cluster definitely.

We had three questions.

Q1) When we executed the next command, the contents of the CLI file are displayed in the form that ""(double quatation) disappeared.

[root@snmp1 ~]# crm configure show
(snip)
primitive prmDummy1 ocf:pacemaker:Dummy \
op start interval=0s timeout=300s on-fail=restart \
op monitor interval=10s timeout=60s on-fail=restart \
op stop interval=0s timeout=300s on-fail=block
primitive prmDummy2 Dummy \
op start interval=0s timeout=300s on-fail=restart \
op monitor interval=10s timeout=60s on-fail=restart \
op stop interval=0s timeout=300s on-fail=block
(snip)

When we used Pacemaker1.0, results seem to be different.
Are these specifications of new crm command?

Q2) When we executed the next command, ocf:heartbeat is not displayed.

(snip)
[root@snmp1 ~]# crm configure show
(snip)
primitive prmDummy2 Dummy \
op start interval=0s timeout=300s on-fail=restart \
op monitor interval=10s timeout=60s on-fail=restart \
op stop interval=0s timeout=300s on-fail=block
(snip)

When we used Pacemaker1.0, results seem to be different.
Are these specifications of new crm command?

Q3) We used the editing feature in the next procedure, but it is not changed.
Is a procedure of our editing wrong?

----------------------------------------------
[root@snmp1 ~]# crm configure edit prmDummy1

primitive prmDummy1 ocf:pacemaker:Dummy \
op start interval=0s timeout=300s on-fail=restart \
op monitor enabled=false interval=10s timeout=60s on-fail=restart \
---> Add enabled=false.
op stop interval=0s timeout=300s on-fail=block
# vim: set filetype=pcmk:
:wq

[root@snmp1 ~]# crm configure show prmDummy1
primitive prmDummy1 ocf:pacemaker:Dummy \
op start interval=0s timeout=300s on-fail=restart \
op monitor enabled=false interval=10s timeout=60s on-fail=restart \
---> Okay! : Add enabled=false.
op stop interval=0s timeout=300s on-fail=block

[root@snmp1 ~]# crm configure edit prmDummy1

primitive prmDummy1 ocf:pacemaker:Dummy \
op start interval=0s timeout=300s on-fail=restart \
op monitor interval=10s timeout=60s on-fail=restart \
---> Delete enabled=false.
op stop interval=0s timeout=300s on-fail=block
# vim: set filetype=pcmk:
:wq

[root@snmp1 ~]# crm configure show prmDummy1
primitive prmDummy1 ocf:pacemaker:Dummy \
op start interval=0s timeout=300s on-fail=restart \
op monitor interval=10s timeout=60s on-fail=restart enabled=false \
---> why? Not Delete.
op stop interval=0s timeout=300s on-fail=block

[root@snmp1 ~]# crm configure edit prmDummy1

primitive prmDummy1 ocf:pacemaker:Dummy \
op start interval=0s timeout=300s on-fail=restart \
op monitor interval=11s timeout=60s on-fail=restart \
---> Delete enabled=false and Change interval.(10->11)
op stop interval=0s timeout=300s on-fail=block
# vim: set filetype=pcmk:
:wq

[root@snmp1 ~]# crm configure show prmDummy1
primitive prmDummy1 ocf:pacemaker:Dummy \
op start interval=0s timeout=300s on-fail=restart \
op monitor interval=11s timeout=60s on-fail=restart \
---> Okay! : Delete enabled=false.
---> why?
op stop interval=0s timeout=300s on-fail=block

----------------------------------------------

Best Regards,
Hideo Yamauchi.

_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Re: [crmsh] Question about latest crmsh. [ In reply to ]

kgronlund at suse

Nov 28, 2014, 2:06 AM

Post #2 of 3 (1167 views)

Permalink

Hi,

Answers to your questions follow inline.

renayama19661014@ybb.ne.jp writes:

> Hi All,
>
> We used the latest edition of crmsh-b932826fb4f924137eab9efd13b7bddf8afde3f0 with Pacamerk1.1.12.
> We sent the following CLI file.
>
[snip]
> We had three questions.
>
> Q1) When we executed the next command, the contents of the CLI file are displayed in the form that ""(double quatation) disappeared.
>
> [root@snmp1 ~]# crm configure show
> (snip)
> primitive prmDummy1 ocf:pacemaker:Dummy \
> Â Â Â Â op start interval=0s timeout=300s on-fail=restart \
> Â Â Â Â op monitor interval=10s timeout=60s on-fail=restart \
> Â Â Â Â op stop interval=0s timeout=300s on-fail=block
> primitive prmDummy2 Dummy \
> Â Â Â Â op start interval=0s timeout=300s on-fail=restart \
> Â Â Â Â op monitor interval=10s timeout=60s on-fail=restart \
> Â Â Â Â op stop interval=0s timeout=300s on-fail=block
> (snip)
>
> When we used Pacemaker1.0, results seem to be different.
> Are these specifications of new crm command?
>

Yes, this is the new CLI syntax for crmsh. Where possible, crmsh now
tries to avoid adding the double quotation marks.

> Q2) When we executed the next command, ocf:heartbeat is not displayed.
>
> (snip)
> [root@snmp1 ~]# crm configure show
> (snip)
> primitive prmDummy2 Dummy \
> Â Â Â Â op start interval=0s timeout=300s on-fail=restart \
> Â Â Â Â op monitor interval=10s timeout=60s on-fail=restart \
> Â Â Â Â op stop interval=0s timeout=300s on-fail=block
> (snip)
>
> When we used Pacemaker1.0, results seem to be different.
> Are these specifications of new crm command?
>

Yes, this is also a new feature in crmsh. When using agents from
ocf:heartbeat:, crmsh does not display the prefix part.

> Q3) We used the editing feature in the next procedure, but it is not changed.
> Is a procedure of our editing wrong?

Unfortunately, this is a bug in pacemaker, fixed very recently:

https://github.com/ClusterLabs/pacemaker/pull/613

With your version of crmsh, it is possible to work around this issue by
using the interactive shell to modify:

crm configure
edit
commit replace

Using the "commit replace" command circumvents the buggy CIB patching
feature and uses cibadmin to update the CIB.

Cheers,
Kristoffer

>
> ----------------------------------------------
> [root@snmp1 ~]# crm configure edit prmDummy1
>
> primitive prmDummy1 ocf:pacemaker:Dummy \
> Â Â Â Â op start interval=0s timeout=300s on-fail=restart \
> Â Â Â Â op monitor enabled=false interval=10s timeout=60s on-fail=restart \
> Â Â Â Â ---> Add enabled=false.
> Â Â Â Â op stop interval=0s timeout=300s on-fail=block
> # vim: set filetype=pcmk:
> :wq
>
> [root@snmp1 ~]# crm configure show prmDummy1
> primitive prmDummy1 ocf:pacemaker:Dummy \
> Â Â Â Â op start interval=0s timeout=300s on-fail=restart \
> Â Â Â Â op monitor enabled=false interval=10s timeout=60s on-fail=restart \
> Â Â Â Â ---> Okay! : Add enabled=false.
> Â Â Â Â op stop interval=0s timeout=300s on-fail=block
>
> [root@snmp1 ~]# crm configure edit prmDummy1
>
> primitive prmDummy1 ocf:pacemaker:Dummy \
> Â Â Â Â op start interval=0s timeout=300s on-fail=restart \
> Â Â Â Â op monitor interval=10s timeout=60s on-fail=restart \
> Â Â Â Â ---> Delete enabled=false.
> Â Â Â Â op stop interval=0s timeout=300s on-fail=block
> # vim: set filetype=pcmk:
> :wq
>
> [root@snmp1 ~]# crm configure show prmDummy1
> primitive prmDummy1 ocf:pacemaker:Dummy \
> Â Â Â Â op start interval=0s timeout=300s on-fail=restart \
> Â Â Â Â op monitor interval=10s timeout=60s on-fail=restart enabled=false \
> Â Â Â Â ---> why? Not Delete.
> Â Â Â Â op stop interval=0s timeout=300s on-fail=block
>
> [root@snmp1 ~]# crm configure edit prmDummy1
>
> primitive prmDummy1 ocf:pacemaker:Dummy \
> Â Â Â Â op start interval=0s timeout=300s on-fail=restart \
> Â Â Â Â op monitor interval=11s timeout=60s on-fail=restart \
> Â Â Â Â ---> Delete enabled=false and Change interval.(10->11)
> Â Â Â Â op stop interval=0s timeout=300s on-fail=block
> # vim: set filetype=pcmk:
> :wq
>
> [root@snmp1 ~]# crm configure show prmDummy1
> primitive prmDummy1 ocf:pacemaker:Dummy \
> Â Â Â Â op start interval=0s timeout=300s on-fail=restart \
> Â Â Â Â op monitor interval=11s timeout=60s on-fail=restart \
> Â Â Â Â ---> Okay! : Delete enabled=false.Â
> Â Â Â Â ---> why?
> Â Â Â Â op stop interval=0s timeout=300s on-fail=block
>
> ----------------------------------------------
>
> Best Regards,
> Hideo Yamauchi.
>
> _______________________________________________
> Linux-HA mailing list
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>

--
// Kristoffer GrÃ¶nlund
// kgronlund@suse.com
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Re: [crmsh] Question about latest crmsh. [ In reply to ]

renayama19661014 at ybb

Nov 28, 2014, 4:55 PM

Post #3 of 3 (1160 views)

Permalink

Hi Kristoffer,

Thank you for comments.

All right!

About "commit replace", I confirm it on Monday.

Many Thanks!
Hideo Yamauchi.

----- Original Message -----
> From: Kristoffer Grönlund <kgronlund@suse.com>
> To: renayama19661014@ybb.ne.jp; General Linux-HA mailing list <linux-ha@lists.linux-ha.org>; LINUX-HA <linux-ha@lists.linux-ha.org>
> Cc:
> Date: 2014/11/28, Fri 19:06
> Subject: Re: [Linux-HA] [crmsh] Question about latest crmsh.
>
>
> Hi,
>
> Answers to your questions follow inline.
>
> renayama19661014@ybb.ne.jp writes:
>
>> Hi All,
>>
>> We used the latest edition of
> crmsh-b932826fb4f924137eab9efd13b7bddf8afde3f0 with Pacamerk1.1.12.
>> We sent the following CLI file.
>>
> [snip]
>> We had three questions.
>>
>> Q1) When we executed the next command, the contents of the CLI file are
> displayed in the form that ""(double quatation) disappeared.
>>
>> [root@snmp1 ~]# crm configure show
>> (snip)
>> primitive prmDummy1 ocf:pacemaker:Dummy \
>> op start interval=0s timeout=300s on-fail=restart \
>> op monitor interval=10s timeout=60s on-fail=restart \
>> op stop interval=0s timeout=300s on-fail=block
>> primitive prmDummy2 Dummy \
>> op start interval=0s timeout=300s on-fail=restart \
>> op monitor interval=10s timeout=60s on-fail=restart \
>> op stop interval=0s timeout=300s on-fail=block
>> (snip)
>>
>> When we used Pacemaker1.0, results seem to be different.
>> Are these specifications of new crm command?
>>
>
> Yes, this is the new CLI syntax for crmsh. Where possible, crmsh now
> tries to avoid adding the double quotation marks.
>
>
>> Q2) When we executed the next command, ocf:heartbeat is not displayed.
>>
>> (snip)
>> [root@snmp1 ~]# crm configure show
>> (snip)
>> primitive prmDummy2 Dummy \
>> op start interval=0s timeout=300s on-fail=restart \
>> op monitor interval=10s timeout=60s on-fail=restart \
>> op stop interval=0s timeout=300s on-fail=block
>> (snip)
>>
>> When we used Pacemaker1.0, results seem to be different.
>> Are these specifications of new crm command?
>>
>
> Yes, this is also a new feature in crmsh. When using agents from
> ocf:heartbeat:, crmsh does not display the prefix part.
>
>> Q3) We used the editing feature in the next procedure, but it is not
> changed.
>> Is a procedure of our editing wrong?
>
> Unfortunately, this is a bug in pacemaker, fixed very recently:
>
> https://github.com/ClusterLabs/pacemaker/pull/613
>
> With your version of crmsh, it is possible to work around this issue by
> using the interactive shell to modify:
>
> crm configure
> edit
> commit replace
>
> Using the "commit replace" command circumvents the buggy CIB patching
> feature and uses cibadmin to update the CIB.
>
> Cheers,
> Kristoffer
>
>>
>> ----------------------------------------------
>> [root@snmp1 ~]# crm configure edit prmDummy1
>>
>> primitive prmDummy1 ocf:pacemaker:Dummy \
>> op start interval=0s timeout=300s on-fail=restart \
>> op monitor enabled=false interval=10s timeout=60s on-fail=restart
> \
>> ---> Add enabled=false.
>> op stop interval=0s timeout=300s on-fail=block
>> # vim: set filetype=pcmk:
>> :wq
>>
>> [root@snmp1 ~]# crm configure show prmDummy1
>> primitive prmDummy1 ocf:pacemaker:Dummy \
>> op start interval=0s timeout=300s on-fail=restart \
>> op monitor enabled=false interval=10s timeout=60s on-fail=restart
> \
>> ---> Okay! : Add enabled=false.
>> op stop interval=0s timeout=300s on-fail=block
>>
>> [root@snmp1 ~]# crm configure edit prmDummy1
>>
>> primitive prmDummy1 ocf:pacemaker:Dummy \
>> op start interval=0s timeout=300s on-fail=restart \
>> op monitor interval=10s timeout=60s on-fail=restart \
>> ---> Delete enabled=false.
>> op stop interval=0s timeout=300s on-fail=block
>> # vim: set filetype=pcmk:
>> :wq
>>
>> [root@snmp1 ~]# crm configure show prmDummy1
>> primitive prmDummy1 ocf:pacemaker:Dummy \
>> op start interval=0s timeout=300s on-fail=restart \
>> op monitor interval=10s timeout=60s on-fail=restart enabled=false
> \
>> ---> why? Not Delete.
>> op stop interval=0s timeout=300s on-fail=block
>>
>> [root@snmp1 ~]# crm configure edit prmDummy1
>>
>> primitive prmDummy1 ocf:pacemaker:Dummy \
>> op start interval=0s timeout=300s on-fail=restart \
>> op monitor interval=11s timeout=60s on-fail=restart \
>> ---> Delete enabled=false and Change interval.(10->11)
>> op stop interval=0s timeout=300s on-fail=block
>> # vim: set filetype=pcmk:
>> :wq
>>
>> [root@snmp1 ~]# crm configure show prmDummy1
>> primitive prmDummy1 ocf:pacemaker:Dummy \
>> op start interval=0s timeout=300s on-fail=restart \
>> op monitor interval=11s timeout=60s on-fail=restart \
>> ---> Okay! : Delete enabled=false.
>> ---> why?
>> op stop interval=0s timeout=300s on-fail=block
>>
>> ----------------------------------------------
>>
>> Best Regards,
>> Hideo Yamauchi.
>>
>> _______________________________________________
>> Linux-HA mailing list
>> Linux-HA@lists.linux-ha.org
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
>>
>
> --
> // Kristoffer Grönlund
> // kgronlund@suse.com
>
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems