[Pacemaker] [Problem][crmsh]The designation of the 'ordered' attribute becomes the error.
renayama19661014 at ybb.ne.jp
renayama19661014 at ybb.ne.jp
Mon Mar 18 22:09:13 EDT 2013
Hi Dejan,
> > changeset: 789:916d1b15edc3
> > user: Dejan Muhamedagic <dejan at hello-penguin.com>
> > date: Thu Aug 16 17:01:24 2012 +0200
> > summary: Medium: cibconfig: drop attributes set to default on cib import
I confirmed that I was set definitely without becoming xml if you made the modifications that you taught.
* When I set true with cib.xml file.(sequential=true)
(snip)
<constraints>
<rsc_order id="test-order">
<resource_set sequential="true" id="test-order-resource_set">
<resource_ref id="Dummy01"/>
<resource_ref id="Dummy02"/>
</resource_set>
</rsc_order>
</constraints>
(snip)
[root at rh64-heartbeat1 ~]# crm
crm(live)# configure
crm(live)configure# show
(snip)
group testGroup01 Dummy01 Dummy02
order test-order : _rsc_set_ Dummy01 Dummy02
(snip)
Many Thanks!
Hideo Yamauchi.
--- On Mon, 2013/3/11, renayama19661014 at ybb.ne.jp <renayama19661014 at ybb.ne.jp> wrote:
> Hi Dejan,
>
> Thank you for comment.
>
> > sequential=true is the default. In that case it's not possible to
> > have an unequivocal representation for the same construct and, in
> > this particular case, the conversion XML->CLI->XML yields a
> > different XML. There's a later commit which helps here, I think
> > that it should be possible to backport it to 1.0:
> >
> > changeset: 789:916d1b15edc3
> > user: Dejan Muhamedagic <dejan at hello-penguin.com>
> > date: Thu Aug 16 17:01:24 2012 +0200
> > summary: Medium: cibconfig: drop attributes set to default on cib import
>
> I apply the backporting that you taught and confirm movement.
> I talk with you again if I have a problem.
>
> > > Is there a right method to appoint an attribute of "resource_set" with crm shell?
> > > Possibly is not "resource_set" usable with crm shell of Pacemaker1.0.13?
> >
> > Should work. It's just that using it with two resources, well,
> > it's sort of unusual use case.
>
> All right!
>
> Many Thanks!
> Hideo Yamauchi.
>
> --- On Fri, 2013/3/8, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:
>
> > Hi Hideo-san,
> >
> > On Thu, Mar 07, 2013 at 10:18:09AM +0900, renayama19661014 at ybb.ne.jp wrote:
> > > Hi Dejan,
> > >
> > > The problem was settled with your patch.
> > >
> > > However, I have a question.
> > > I want to use "resource_set" which Mr. Andrew proposed, but do not understand a method to use with crm shell.
> > >
> > > I read two next cib.xml and confirmed it with crm shell.
> > >
> > > Case 1) sequential="false".
> > > (snip)
> > > <constraints>
> > > <rsc_order id="test-order">
> > > <resource_set sequential="false" id="test-order-resource_set">
> > > <resource_ref id="vip-master"/>
> > > <resource_ref id="vip-rep"/>
> > > </resource_set>
> > > </rsc_order>
> > > </constraints>
> > > (snip)
> > > * When I confirm it with crm shell ...
> > > (snip)
> > > group master-group vip-master vip-rep
> > > order test-order : _rsc_set_ ( vip-master vip-rep )
> > > (snip)
> >
> > Yes. All size two resource sets get the _rsc_set_ keyword,
> > otherwise it's not possible to distinguish them from "normal"
> > constraints. Resource sets are supposed to help cases when it is
> > necessary to express relation between three or more resources.
> > Perhaps this case should be an exception.
> >
> > > Case 2) sequential="true"
> > > (snip)
> > > <constraints>
> > > <rsc_order id="test-order">
> > > <resource_set sequential="true" id="test-order-resource_set">
> > > <resource_ref id="vip-master"/>
> > > <resource_ref id="vip-rep"/>
> > > </resource_set>
> > > </rsc_order>
> > > </constraints>
> > > (snip)
> > > * When I confirm it with crm shell ...
> > > (snip)
> > > group master-group vip-master vip-rep
> > > xml <rsc_order id="test-order"> \
> > > <resource_set id="test-order-resource_set" sequential="true"> \
> > > <resource_ref id="vip-master"/> \
> > > <resource_ref id="vip-rep"/> \
> > > </resource_set> \
> > > </rsc_order>
> > > (snip)
> > >
> > > Does the designation of "sequential=true" have to describe it in xml?
> >
> > sequential=true is the default. In that case it's not possible to
> > have an unequivocal representation for the same construct and, in
> > this particular case, the conversion XML->CLI->XML yields a
> > different XML. There's a later commit which helps here, I think
> > that it should be possible to backport it to 1.0:
> >
> > changeset: 789:916d1b15edc3
> > user: Dejan Muhamedagic <dejan at hello-penguin.com>
> > date: Thu Aug 16 17:01:24 2012 +0200
> > summary: Medium: cibconfig: drop attributes set to default on cib import
> >
> > > Is there a right method to appoint an attribute of "resource_set" with crm shell?
> > > Possibly is not "resource_set" usable with crm shell of Pacemaker1.0.13?
> >
> > Should work. It's just that using it with two resources, well,
> > it's sort of unusual use case.
> >
> > Cheers,
> >
> > Dejan
> >
> > > Best Regards,
> > > Hideo Yamauchi.
> > >
> > > --- On Thu, 2013/3/7, renayama19661014 at ybb.ne.jp <renayama19661014 at ybb.ne.jp> wrote:
> > >
> > > > Hi Dejan,
> > > > Hi Andrew,
> > > >
> > > > Thank you for comment.
> > > > I confirm the movement of the patch and report it.
> > > >
> > > > Best Regards,
> > > > Hideo Yamauchi.
> > > >
> > > > --- On Wed, 2013/3/6, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:
> > > >
> > > > > Hi Hideo-san,
> > > > >
> > > > > On Wed, Mar 06, 2013 at 10:37:44AM +0900, renayama19661014 at ybb.ne.jp wrote:
> > > > > > Hi Dejan,
> > > > > > Hi Andrew,
> > > > > >
> > > > > > As for the crm shell, the check of the meta attribute was revised with the next patch.
> > > > > >
> > > > > > * http://hg.savannah.gnu.org/hgweb/crmsh/rev/d1174f42f4b3
> > > > > >
> > > > > > This patch was backported in Pacemaker1.0.13.
> > > > > >
> > > > > > * https://github.com/ClusterLabs/pacemaker-1.0/commit/fa1a99ab36e0ed015f1bcbbb28f7db962a9d1abc#shell/modules/cibconfig.py
> > > > > >
> > > > > > However, the ordered,colocated attribute of the group resource is treated as an error when I use crm Shell which adopted this patch.
> > > > > >
> > > > > > --------------------------------------
> > > > > > (snip)
> > > > > > ### Group Configuration ###
> > > > > > group master-group \
> > > > > > vip-master \
> > > > > > vip-rep \
> > > > > > meta \
> > > > > > ordered="false"
> > > > > > (snip)
> > > > > >
> > > > > > [root at rh63-heartbeat1 ~]# crm configure load update test2339.crm
> > > > > > INFO: building help index
> > > > > > crm_verify[20028]: 2013/03/06_17:57:18 WARN: unpack_nodes: Blind faith: not fencing unseen nodes
> > > > > > WARNING: vip-master: specified timeout 60s for start is smaller than the advised 90
> > > > > > WARNING: vip-master: specified timeout 60s for stop is smaller than the advised 100
> > > > > > WARNING: vip-rep: specified timeout 60s for start is smaller than the advised 90
> > > > > > WARNING: vip-rep: specified timeout 60s for stop is smaller than the advised 100
> > > > > > ERROR: master-group: attribute ordered does not exist -----> WHY?
> > > > > > Do you still want to commit? y
> > > > > > --------------------------------------
> > > > > >
> > > > > > If it chooses `yes` by a confirmation message, it is reflected, but it is a problem that error message is displayed.
> > > > > > * The error occurs in the same way when I appoint colocated attribute.
> > > > > > And....I noticed that there was not explanation of ordered,colocated of the group resource in online help of Pacemaker.
> > > > > >
> > > > > > I think that the designation of the ordered,colocated attribute should not become the error in group resource.
> > > > > > In addition, I think that ordered,colocated should be added to online help.
> > > > >
> > > > > These attributes are not listed in crmsh. Does the attached patch
> > > > > help?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Dejan
> > > > > >
> > > > > > Best Regards,
> > > > > > Hideo Yamauchi.
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Pacemaker mailing list: Pacemaker at 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 at 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 at 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 at 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 at 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
>
More information about the Pacemaker
mailing list