[ClusterLabs] Antw: Re: SLES 11 SP4 & csync2

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Tue Aug 25 04:28:50 EDT 2015


>>> Jorge Fábregas <jorge.fabregas at gmail.com> schrieb am 22.08.2015 um 19:07
in
Nachricht <55D8AC56.4020106 at gmail.com>:
> On 08/22/2015 01:38 AM, Andrei Borzenkov wrote:
>> Wrong question :) Of course you can do everything manually. The real 
>> question should be - will SUSE support installation done manually. If 
>> you do not care about support - sure, you do not need it.
> 
> That's a good point (SUSE support).  Ok, I played with the yast cluster
> module (for initial cluster configuration) and noticed that, apart from
> creating the corosync.conf file, it created:
> 
> - /etc/syconfig/pacemaker
> - /etc/sysconfig/corosync
> 
> ...so I must remind myself that this is not just Linux with
> pacemaker/corosync & friends.  It's all that *on SUSE* so, "when in
> Rome, do as Romands do" :)
> 
> I'll set it up then, in order not to break the warranty.  The HAE guide
> also mentions about placing a call to csync2 in ~/.bash_logout which is
> nice (so you don't forget).

I wouldn't do that; neither recommend. I would sync when I'm ready. If
multiple people log in and out as root, you may have trouble...

> 
> 
>> No, they manipulate CIB so this should be OK. But in real life there are 
>> always more files that should be kept in sync between cluster nodes, 
>> having tool to automate it is good.
> 
> Got it.  Thanks Andrei!
> 
> All the best,
> Jorge
> 
> _______________________________________________
> Users mailing list: Users at clusterlabs.org 
> http://clusterlabs.org/mailman/listinfo/users 
> 
> Project Home: http://www.clusterlabs.org 
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf 
> Bugs: http://bugs.clusterlabs.org 







More information about the Users mailing list