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
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