[ClusterLabs] Configuration of Initial cib.xml

[Kostiantyn Ponomarenko]

Hi folks,

Is it possible to have a configured initial cib.xml file?

In my solution there is a script that applies configuration automatically
each boot.
But before that, another script (before starting pacemaker) does:
    # rm -rf /var/lib/pacemaker/cib/*
in order to clean up the previous config.
The clean up is made each time despite anything.
Then, if the node has a DC status it runs a shell script with crm commands
to set up cluster.

The thing is - every group boot, when all nodes are rebooted, I have those
noisy messages in the log, which say that no STONITH was configured:

2015 Aug  3 17:56:59 +03:00 daemon.err<27> pengine[37739]:    error:
unpack_resources: Resource start-up disabled since no STONITH resources
have been defined
2015 Aug  3 17:56:59 +03:00 daemon.err<27> pengine[37739]:    error:
unpack_resources: Either configure some or disable STONITH with the
stonith-enabled option
2015 Aug  3 17:56:59 +03:00 daemon.err<27> pengine[37739]:    error:
unpack_resources: NOTE: Clusters with shared data need STONITH to ensure
data integrity
2015 Aug  3 17:56:59 +03:00 daemon.err<27> pengine[37739]:    error:
unpack_resources: Resource start-up disabled since no STONITH resources
have been defined
2015 Aug  3 17:56:59 +03:00 daemon.err<27> pengine[37739]:    error:
unpack_resources: Either configure some or disable STONITH with the
stonith-enabled option
2015 Aug  3 17:56:59 +03:00 daemon.err<27> pengine[37739]:    error:
unpack_resources: NOTE: Clusters with shared data need STONITH to ensure
data integrity

The configuration scrip set-up STONITH devices, but the messages still
appear, because the configuration was recreated by Pacemaker and doesn't
have STONITH yet.
So, the idea is to get read of this kind of error messages.

As a possible option I am thinking of creating an initial cib.xml file with
configured STONITH in it, and put it in the place after cleaning up
previous config.
So just wanted to check my idea with somebody, so I am sure it won't lead
to any troubles in future ;-)

Thank you,
Kostya
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20150803/0dc01b59/attachment-0003.html>