On Mon, Nov 9, 2009 at 4:11 PM, Colin <colin....@gmail.com> wrote:
> On Sun, Oct 18, 2009 at 10:33 AM, Andrew Beekhof <and...@beekhof.net> wrote:
>> On Fri, Oct 16, 2009 at 10:54 AM, Raoul Bhatia [IPAX] <r.bha...@ipax.at>
>> wrote:
>>> On 10/16/2009 09:59 AM, Matthew Palmer wrote:
>>>> If this were a single-machine service, I'd completely agree with you.
>>>> Unfortunately, a cluster service like pacemaker needs to have absolutely
>>>> consistent configuration across all the nodes in the cluster, and having it
>>>> read off a file on disk would make that *amazingly* difficult and
>>>> dangerous.
>>>> I remember the fun and games I had dealing with cman (or whatever it was
>>>> that went with that) and it's "read an XML config file and update everyone"
>>>> model. I'll take "crm configure edit" over that any day, TYVM.
>>>
>>> to my knowledge, if no cib.xml file exists, pacemaker creates an empty
>>> one with epoch="0" (or similar, to my experience at least < 100 ;) )
>>>
>>> i've done the following steps numerous times:
>>> 1. stop pacemaker on all nodes
>>> 2. erase all cib.xml related files
>>> 3. drop a new cib.xml into the correct directory on one node
>>> 4. set the correct permissions
>>> 5. startup all nodes
>>> 6. witness the new configuration unfold
>>
>> Yep, if you must take this approach, then the above steps are correct :-)
>>
>> Though these days, its probably easier to skip steps 3 and 4 and load
>> the config using the crm shell.
>
> Is it correct, that the remote-{clear|tls}-port attributes are only
> honoured at startup, i.e. I need to restart corosync (or shoot down
> the cib process) in order to get the port to be opened?
For now yes.
It wouldn't be terribly difficult to implement this
>
> That would mean a stop-start cycle of the cluster on every node if I
> don't start dropping XML-files into place (which I have avoided so
> far)...
>
> Thanks, Colin
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
_______________________________________________
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
