[Pacemaker] Setting cib-bootstrap-options parameters before DC election

[Andrew Beekhof]

> On 14 Jan 2015, at 12:19 am, AWeber - Ryan Steele <ryans at aweber.com> wrote:
> 
> Hi folks,
> 
> For testing scenarios in which I’m only spinning up nodes on my laptop (test-kitchen), I don’t really need the full 20 seconds for dc-deadtime.  However, I haven’t been successful in finding a way to set that option to something lower prior to the DC election during the initial startup of the pacemaker daemon.  Since, cibadmin, cdm, and other CLI tools of that ilk require Pacemaker to be running, I've attempted to configure a pared down cib.xml that just sets the dc-deadtime option, but haven’t had much luck (here’s the config I’m using and the script that generates & uses it).

Is it not taking effect or is the setting being erased? Other?

>  I feel like I'm not too far off from achieving my goal, since the CIB lint checks pass and subsequent versions of the CIB (after the 20s elapses and the DC is elected) preserve the dc-deadtime attribute I’ve set in my pre-seeded cib.xml, but would be most appreciative for a small nudge in the right direction.
> 
> FWIW, this is pacemaker 1.1.10 (well, 1.1.10+git20130802-1ubuntu2.1), corosync 2.3.3-1ubuntu1, and libheartbeat2 1:3.0.5-3.2, all from the official Ubuntu Trusty repository.  Thanks in advance!
> 
> -Ryan
> _______________________________________________
> 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