can someone explain the practical usage of non-unique attributes?
in the ocf ra specs [1], one can read
> The meta data allows the RA to flag one or more instance parameters as
> 'unique'. This is a hint to the RM or higher level configuration tools
> that the combination of these parameters must be unique to the given
> resource type.
speaking in the v2 configuration language, i thought that this means
that one can specify multiple nvpairs with the same name to the cib.xml
file. e.g. looking at the pingd ra:
> <parameter name="pidfile" unique="0">
> <longdesc lang="en">PID file</longdesc>
> <shortdesc lang="en">PID file</shortdesc>
> <content type="string" default="$HA_RSCTMP/pingd-${OCF_RESOURCE_INSTANCE}" />
> </parameter>
-> e.g.
> <nvpair id="pidfile1" name="pidfile" value="/tmp/pid1.pid" />
> <nvpair id="pidfile2" name="pidfile" value="/tmp/pid2.pid" />
as far as i can see, the first nvpair seems to "win" though and
OCF_RESKEY_pidfile is set to "/tmp/pid1.pid".
can someone please shed a light on how to (not) use unique="0"
attributes and how they are passed to the ocf ra scripts?
thanks,
raoul
[1]
http://www.opencf.org/cgi-bin/viewcvs.cgi/specs/ra/resource-agent-api.txt?rev=HEAD
--
____________________________________________________________________
DI (FH) Raoul Bhatia M.Sc. email. [email protected]
Technischer Leiter
IPAX - Aloy Bhatia Hava OEG web. http://www.ipax.at
Barawitzkagasse 10/2/2/11 email. [email protected]
1190 Wien tel. +43 1 3670030
FN 277995t HG Wien fax. +43 1 3670030 15
____________________________________________________________________
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
