[Csync2] announce: Csync2 2.0 rc1 in git repository

[Tim Serong]

On 12/7/2010 at 06:09 AM, Lars Ellenberg <lars.ellenberg at linbit.com> wrote: 
> Johannes Thoma from LINBIT has been integrating some floating patches, 
> and implemented even more suggestions over the last weeks and months. 
> After three years without official release, csync2 finally got a 
> major overhaul, and is now preparing for a 2.0 release. 
>  
> We migrated the version control to GIT, try 
>   git clone git://git.linbit.com/csync2.git 
> or point your browser to http://git.linbit.com/csync2.git 
>  
> For the changelog since the last release (1.34), 
> I'm not even sure what to omit from the git short log, 
> it is too much, bugfixes and improvements alike. 
>  
> The highlight is certainly the database abstraction layer. 
>  
> Feature additions since 1.34: 
> 	database abstraction layer 
> 	- now supports mysql and postgres database backends 
> 	  in addition to sqlite3/sqlite 
> 	IPv6 support 
> 	native gnutls instead of openssl 
> 	tempdir and lock-timeout config options 
> 	do-local-only config option for actions 
> 	example inotify daemon, 
> 	... anything else I forgot, please see the git log 

Sweet, well done.

> Everyone so inclined, give it a spin. 
>  
> Please give us some feedback on bugs, features, omissions, (lack of) 
> documentation or functionality, or anything else csync2 related. 

With the disclaimer that I haven't actually tried 2.0 RC1 yet... :)
There's a specific use-case that isn't well handled, that being adding
a new node to an existing cluster and propagating configuration to the
new node initially.  Here's roughly what you have to do:

0) Make sure hostname resolution works (either ensure DNS works at
   your site, or add the new node to /etc/hosts on an existing node,
   and ensure /etc/hosts is listed in csync2.cfg [caveat: assign
   hostnames to public IP, not loopback IP, or you'll be very unhappy
   later]).
1) Add the new node's hostname to csync2.cfg on an existing node.
2) Copy csync2.cfg and the shared key(s) from existing node to new
   node.
3) Run "csync2 -mr / ; csync2 -xv" on existing node to push config
   to the new node.

This turns out to be remarkably annoying to automate, because you
have to do some operations on the new node and some on an existing
node, and step 3 is arguably somewhat perilous.  It would be really
nice if there was a "csync2 --join-me-to <hostname>" or similar...

Regards,

Tim


-- 
Tim Serong <tserong at novell.com>
Senior Clustering Engineer, OPS Engineering, Novell Inc.