[pkg-kolab] Thoughts on syncrepl support in kolab_boostrap and kolabconf

[Mathieu Parent]

Hi,



2008/10/22 Price,Neil <NPrice at gibb.co.za>:
>
> I had a look at in the kolab upstream cvs for kolab_bootstrap and it didn't
> look they have done much in this regard. Some of the few relevant statements
> are commented out.
>
> To achieve this we need
>
> 1. create a replicator dn during setup. (this is the bit they have commented
> out).
This is not needed: manager's dn is used. This can be an interresting
enhancement.

> 2. accesslog setup on master slapd.conf.
Not needed. You can propose a patch anyway.

> 3. syncrepl setup on slave slapd.conf
This was already done in /etc/ldap/slapd.replicas

This was not working for other reasons :
1. On the master, edit /etc/default/slapd, and set
SLAPD_SERVICES="ldap://127.0.0.1:389/ ldaps:/// ldapi:///" to enable
SSL. Maybe kolab_bootstrap should automaticaly do this?
2. Install the latest kolabd snapshot that includes some fixes
specific to slave setup (missing parameters:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/dist_conf/debian.diff?r1=1.18&r2=1.19&sortby=rev,
slapcat as unprivileged user:
http://svn.debian.org/wsvn/pkg-kolab/kolabd/trunk/debian/patches/30-bootstrap.dpatch?op=diff&rev=959&sc=1)

>
> To achieve 2+3 you'd need a strategy for coping with very different
> slapd.conf on master and slaves. Different templates? Different includes?
> Use kolabconf to modify?
Those differences are handled by buildLDAPReplicas (see
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/perl-kolab/lib/Kolab/Conf.pm?rev=1.1&content-type=text/vnd.viewcvs-markup)

>
> The details of how they currently deal with templates seem to be hidden in
> Kolab.pm which I haven't had the courage to look at yet.
Take a look at Kolab/Conf.pm

>
> _______________________________________________
> pkg-kolab-devel mailing list
> pkg-kolab-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-kolab-devel
>

Thanks

Mathieu Parent