[Kolab-devel] Question about the working of kolab's distributed concept

[radoeka]

Hi,

A question about the working of the kolab configuration and the
data propagation to slaves servers.  Is there a description about this
in cvs of wiki?

I think that it works in the following (I make assumptions here and there
and would be nice if wrong assumptions are corrected):
- admin adds a user via the web interface (which may be located
  on the master server or on a slave system).  The user data is submitted
  by the admin, as a result of this, the data is added to the master ldap
  server.
- The master ldap server replicates the data to the slaves. Among the
  slaves there is the kolab daemon (kolabd) listening to the replicated ldap
  data.  Kolabd creates on the appropriate slave the cyrus email account.
- In case of deletion: admin deletes user via webinterface.  The master
  ldap server is told to remove the cyrus email account (hmm but how?).
  kolabd removes the cyrus email account, sets a kolabDeleteFlag (in
  the master ldap server).  As soon as this flag is  seen on the master,
  the corresponding record(s) is removed from master ldap server.  The
  master replicates this deletion and the data will be removed
  from the slaves as well.

Is this indeed the basic principle on which kolab's distributed concept is
build?

--
Richard