[Pacemaker] multiple cib in one pacemaker installation

M Siddiqui msiddiqui at live.com.pk
Tue Jun 21 18:54:31 UTC 2011


Hi,

Separating different parts of the CIB would be good for initialization
purpose also.
For instance, resource set or a single resource can be defined in a
separate file;
the resource file can be changed dynamically or at initialization time
that should
be reloaded automatically by the pacemaker.
Its similar to cibadmin replace component command but instead of calling the
command-line, change the component.xml file and let the pacemaker reload
and re-apply again.
Would be useful for:
- adding high-level manageability options on top of the pacemaker
- preparing a custom image with a set of pre-cooked resources with
default params
- moving a node between different clusters dynamically etc.

mumtaz

On Tue, Jun 21, 2011 at 5:36 AM, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:
> Hi,
>
> On Thu, Jun 02, 2011 at 02:51:24PM +0400, ruslan usifov wrote:
>> Hello
>>
>> Is it possible have multiple cib in one cluster installation. I try to
>> describe what i want:
>>
>>
>> For example we have multiple undependable resources (as resource i mean here
>> ip address files system + service (like apache, nginx and etc)). Now as they
>> placed in one cib configuration (crm configure show) is very big and is
>> difficultly read(many text). And i think that if we separate this
>> undependable resources in multiple cib read and edit configuration  becomes
>> much more convenient (something like shadow cib, but live not sandbox).
>>
>> If this is not implemented it would be great if this be applied in future
>> versions.
>
> Right now there's no way to do this. But it sounds like a good
> idea to me. Big configurations are definitely difficult to deal
> with.
>
> One idea I had earlier, but never implemented it, has been to
> define a filter for the crm configure show command so that only
> parts of the configuration are displayed. That's not exactly the
> same as what you proposed, but tackles the same issue.
>
> I don't know how difficult it would be to implement
> configuration split natively in pacemaker. And probably it
> wouldn't get a lot of attention.
>
> Thanks,
>
> Dejan
>
>> _______________________________________________
>> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
>
> _______________________________________________
> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>




More information about the Pacemaker mailing list