Date: Wed, 20 Feb 2019 15:35:46 +0100 From: Ludwig Krispenz lkrispen@redhat.com
On 02/20/2019 03:24 PM, Howard Chu wrote:
Mark Reynolds wrote:
On 2/20/19 5:59 AM, Howard Chu wrote:
>>> Date: Tue, 19 Feb 2019 13:50:11 +0100 >>> From: wodel youchi wodel.youchi@gmail.com >>> >>> Hi, >>> >>> is it possible to create a replication matser/master or master/slave >>> between 389DS and another LDAP server openldap for example? >>> >>> Regards. > Maybe. OpenLDAP has recently added support for replication using a retro changelog. > It has only been tested against Sun/Oracle DSEE so far
389's retro changelog should be the same as DSEE, so this would be an option. Howard, does this new replication feature in OpenLDAP work in both directions?
Not at the moment. It only allows OpenLDAP to replicate from DSEE. It probably wouldn't be difficult to write an overlay to generate a compatible changelog, for going the other direction.
390ds also impelments SyncRepl as a plugin, so this could also be an option to try, but it would still provide only the direction 389ds -->openldap. For the other direction 389ds would have to offer some "pull replication" feature, which doesn't exist.
Not necessarily. OpenLDAP can also push changes; this configuration is sometimes needed for syncrepl behind various firewall setups.
A further problem would be in synchronizing updates from several sources, 389ds uses CSNs and RUVs, openldap also has CSN, which are a similar concept, but not directly compatible. So, even if there are approaches to do it, I think we are not there.
Indeed, I don't see a straightforward way to support master/master at the moment. But for typical provider/consumer replication it could be done, with a couple remappings of operational attributes in the middle.
389-users@lists.fedoraproject.org