Due to the changes made by SUSE and Red Hat, there are customers who are needing to move from OpenLDAP to 389-ds.
I think it's not possible to do a 1:1 migration but we can do as much as possible. I think an example of what we could achieve is:
I think we can't achieve a perfect migration but anything that helps makes this easier would be welcome.
We could draw inspiration from FreeIPA's ldap migration tool.
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue tagged with: openldap
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4 backlog
Requires https://pagure.io/389-ds-base/pull-request/50934
Metadata Update from @firstyear: - Issue marked as depending on: #50933 - Issue marked as depending on: #50945
Metadata Update from @firstyear: - Issue marked as depending on: #137
Metadata Update from @firstyear: - Issue marked as depending on: #137 - Issue marked as depending on: #50947
Metadata Update from @tbordaz: - Issue marked as depending on: #50925
https://pagure.io/389-ds-base/pull-request/51163
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3600
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue unmarked as depending on: #137 - Issue unmarked as depending on: #50925 - Issue unmarked as depending on: #50933 - Issue unmarked as depending on: #50945 - Issue unmarked as depending on: #50947 - Issue unmarked as depending on: #51171 - Issue unmarked as depending on: #51235
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.