[Pacemaker] [PATCH] Allow the user to insert a startup configuration

Andrew Beekhof andrew at beekhof.net
Tue Dec 15 13:48:53 UTC 2009


On Tue, Dec 15, 2009 at 1:01 PM, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:
> Hi,
>
> On Tue, Dec 15, 2009 at 12:38:47PM +0100, Andrew Beekhof wrote:
>> On Tue, Dec 15, 2009 at 11:47 AM, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:
>> > Hi,
>> >
>> > On Tue, Dec 15, 2009 at 11:37:48AM +0100, Andrew Beekhof wrote:
>> >> Anyone else interested in this feature being added?
>> >
>> > The configuration is not explicitely given to the cluster, but
>> > placed in a file. What happens on next startup? Who removes the
>> > file so that the cluster doesn't load it again? If the answer to
>> > the last question is "the admin", I'm against the feature.
>>
>> As I understand it, the intention is that the cluster always loads it.
>> I personally would have no use for such a feature[1], but it seems to
>> be a recurring theme so I'm reluctantly considering it.
>>
>> [1] It really only has an effect if the entire cluster is down anyway.
>
> Consider this: The static init cib is stored, the user starts the
> cluster and waits anxiously for the configuration to load, it's
> loaded yeah!, but there's a problem with resource x, let's see
> where's the issue, reading a few thousand lines of log, aha!,
> there it is, fixed, works!, great, everybody happy, everybody
> forgets about the static init cib; then next month there's a new
> release, put resource in not managed mode, stop cluster, upgrade,
> start cluster, load static init cib. That is bound to happen.
> What's wrong with cibadmin -C? Or crm configure load replace? One
> can even load from an url.

I'm not disagreeing, I'm just saying that this is how the feature is
intended to work (and trying to gauge the interest in it).




More information about the Pacemaker mailing list