No subject


Sun Apr 3 06:52:37 UTC 2011


trying to remove and should be read in reverse.

>
>> > =A0 =A0 =A0<rsc_order id=3D"order-set" kind=3D"Mandatory">
>> > =A0 =A0 =A0 =A0<resource_ref id=3D"dummy0" action=3D"promote"/>
>> > =A0 =A0 =A0 =A0<resource_ref id=3D"dummy1" action=3D"promote"/>
>> > =A0 =A0 =A0 =A0<ordering_set id=3D"order-set-1" internal-ordering=3D"O=
ptional">
>> > =A0 =A0 =A0 =A0 =A0<resource_ref id=3D"dummy2"/>
>> > =A0 =A0 =A0 =A0 =A0<resource_ref id=3D"dummy3"/>
>> > =A0 =A0 =A0 =A0</ordering_set>
>> > =A0 =A0 =A0</rsc_order>
>> >
>> > For instance, that way we won't have single resource sets which
>> > look silly.
>>
>> Thats for the shell to deal with. =A0Sorry.
>> If you want to omit the delimiters for a single set, or the first one,
>> or the last one, or the one in the middle - go for it.
>> But that's got nothing to do with the XML.
>
> OK. Though I wish I could understand why is that impossible to
> code in such a way in XML. I mean, semantically it is the same
> thing, right? It's just that the latter version has a bit less
> scaffolding.

Its a lot of extra work to reduce a minimal amount of XML scaffolding
that the vast majority of people will never see (since they use the
shell) and introduces unnecessary confusion as to which syntax is
"correct".

>
>> >> Also, the changes wont be in a release until 1.1.7 and it will take a
>> >> while to enter common usage.
>> >> So I think you have time.
>> >
>> > OK.
>> >
>> >> > I'm going to try to do something today and tomorrow, but next
>> >> > week I'll be away. So, if you're in a hurry, go ahead with the
>> >> > changes.
>> >> >
>> >> > Just two more notes regarding the language:
>> >> >
>> >> > There's "colocation_set/internal-colocation" and
>> >> > "ordering_set/internal-ordering". They sound different. Should
>> >> > the order stuff be "order_set/internal-order"? I'm not partial
>> >> > to any and furthermore not a native speaker, so I'll leave that
>> >> > to you and others who are more intimate with english.
>> >>
>> >> As an engineer my grasp on english can be tenuous at times, but
>> >> "internal-order" feels wrong.
>> >
>> > How about internal-score for both? I mean, we already know what
>> > kind of constraint it is.
>>
>> Score does not make sense for ordering constraints.
>> Since we're already removing it from the non-set version, it doesn't
>> make sense to add it back here.
>
> Ah, forgot that again. OK, then internal-score and internal-kind?
> Or just "score" and "kind"? The thing is, for instance in the
> rsc_colocation element, there's the "score" attribute specifying
> the same kind of thing as the "internal-colocation" attribute in
> the colocation_set element. That sounds confusing to me.

I added the internal- prefix to fix it in people's minds that it
applied to the members of the set and not between the sets themselves.

>
> And how about "collocation" instead of "colocation"? At least my
> dictionaries prefer the former spelling.

Apparently either form is correct:
   http://en.wikipedia.org/wiki/Colocation

So I guess we should use colocation to be consistent with the constraint na=
me.

>
> Cheers,
>
> Dejan
>
>> >> > Are we going to name the new stuff differently in shell? Such as
>> >> > collocation_set and order(ing)_set? Though I don't like these in
>> >> > particular, because they are going to be the only ones with '_'
>> >> > in its names,
>> >>
>> >> I was using '-', but then I noticed all the other tag names used '_'.
>> >> Then I remembered deciding at one point to use '_' for tag names
>> >> (partly because changing them is hard) and '-' for attributes.
>> >>
>> >> Having said that, the tokens used by the shell are not required to
>> >> match those in the xml.
>> >> Though it may require more work when translating between xml and shel=
l syntax.
>> >
>> > Yes, I know that, and I was actually asking about the names in
>> > the shell because I cannot think of anything better than
>> > order_set or collocation_set.
>> >
>> >> Remember to check the validate-with field though - to see which
>> >> version of the syntax the cluster is currently using.
>> >
>> > Right.
>> >
>> > Thanks,
>> >
>> > Dejan
>> >
>> >> > but there seems to be no way around it. Any better
>> >> > suggestions?
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Dejan
>> >> >
>> >> > _______________________________________________
>> >> > 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_Scratc=
h.pdf
>> >> > Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?produ=
ct=3DPacemaker
>> >> >
>> >>
>> >> _______________________________________________
>> >> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=
=3DPacemaker
>> >
>> > _______________________________________________
>> > 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.p=
df
>> > Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=
=3DPacemaker
>> >
>>
>> _______________________________________________
>> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=3D=
Pacemaker
>
> _______________________________________________
> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=3DP=
acemaker
>



More information about the Pacemaker mailing list