[Pacemaker] Correct order of meta/params in crm

[Dejan Muhamedagic]

Hi,

On Sat, Mar 02, 2013 at 08:19:23AM -0500, David Coulson wrote:
> Running Pacemaker 1.1.7-6.el6-148fccfd5985c5590cc601123c6c16e966b85d14
> 
> I noticed we have inconsistent ordering of meta/params in our
> configuration - For some resources, meta comes before params, in
> some cases after. In the case below, both. I am assuming meta before
> params is the correct way to do it, but wanted to be sure before I
> clean it all up.
> 
> primitive re-wesbprod-ip ocf:heartbeat:IPaddr \
>         meta failure-timeout="60" \
>         params ip="172.31.0.65" cidr_netmask="32" nic="lo" \
>         meta failure-timeout="60" \
>         op monitor interval="30s"

You have here two sets of meta parameters. But that probably
doesn't matter. Otherwise, any order of params, op, meta is OK.
Just keep them grouped, otherwise you'll end up with multiple
sets.

Thanks,

Dejan

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