[Pacemaker] getting started

[Frank DiMeo]

I've been working with pacemaker/openais for a few weeks now and have several "getting started" questions, so I'll put them all into one email:

1) Is there a way to start pacemaker and specify an xml file as the startup configuration?  Right now, I start openais/pacemaker, wait for DC election, then run cibadmin to load the file.  That's fine for now, but I want to automate this eventually.

2) Is there any way to shorten the time for DC election?  I was hoping to be able to specify a cluster-delay shorter than 60s by loading an xml file at startup, and thereby shorten this election time.

3) I can't seem to specify either an rsc_defaults or op_defaults section in an xml file.  When I try to specify rsc_defaults for instance, syslog shows:

ov 18 08:57:57 ubuntu_1 cibadmin: [27658]: info: Invoked: cibadmin --replace --xml-file 2rcordered_1_sticky.xml 
Nov 18 08:57:57 ubuntu_1 cib: [27081]: ERROR: Extra element rsc_defaults in interleave 
Nov 18 08:57:57 ubuntu_1 cib: [27081]: ERROR: Element configuration failed to validate content 
Nov 18 08:57:57 ubuntu_1 cib: [27081]: ERROR: Element cib failed to validate content 
Nov 18 08:57:57 ubuntu_1 cib: [27081]: WARN: cib_perform_op: Updated CIB does not validate against pacemaker-1.0 schema/dtd
Nov 18 08:57:57 ubuntu_1 cib: [27081]: WARN: cib_diff_notify: Update (client: cibadmin, call:2): 0.7.3 -> 3.29.1 (Update does not conform to the configured schema/DTD)
Nov 18 08:57:57 ubuntu_1 cib: [27081]: WARN: cib_process_request: Operation complete: op cib_replace for section 'all'

I don't see what I'm doing wrong.  The offending xml file (2rcordered_1_sticky.xml) is enclosed.

4) I'm trying to specify two collocated resources that don't have any startup dependency.  When I use the syntax:

    <constraints>
      <rsc_colocation id="coloc-1" score="INFINITY">
	<resource_set id="collocated-set-1" sequential="false">
	  <resource_ref id="eyes"/>
	  <resource_ref id="clock"/>
	</resource_set>
      </rsc_colocation>
    </constraints>

Both resources start up, but not on the same node.  According to the documentation (as I read it), this syntax should cause collocation of the two resources, but not control the ordering.


Thanks very much in advance for you comments,
-Frank
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2rcordered_1_sticky.xml
Type: text/xml
Size: 1618 bytes
Desc: 2rcordered_1_sticky.xml
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20091118/792eb6c0/attachment-0003.xml>