Add support for having multiple backends per suffix (for entry distribution), including support for using distribution without using chaining.
Port old-style legacy methods to use the new style code.
0001-use-new-style-backend-mappingtree-and-get-rid-of-add.patch 0001-use-new-style-backend-mappingtree-and-get-rid-of-add.patch
0002-use-new-style-DirSrv-allocate-create-open-map-old-st.patch 0002-use-new-style-DirSrv-allocate-create-open-map-old-st.patch
0003-add-support-for-dirsrv.ldifdir-this-is-the-ldif-impo.patch 0003-add-support-for-dirsrv.ldifdir-this-is-the-ldif-impo.patch
0004-rename-distribution-function-properties-from-chain.patch 0004-rename-distribution-function-properties-from-chain.patch
0005-support-multiple-backends-per-suffix.patch 0005-support-multiple-backends-per-suffix.patch
0006-support-new-style-replica-changelog-code-in-legacy-r.patch 0006-support-new-style-replica-changelog-code-in-legacy-r.patch
Sorry of the late review and thanks Rich for fixing all these. Ack
Only in https://fedorahosted.org/389/attachment/ticket/47674/0002-use-new-style-DirSrv-allocate-create-open-map-old-st.patch, because https://fedorahosted.org/389/ticket/47671 was pushed, it is no longer necessary to hack the dirsrv.state to OFFLINE.
Rich, do you want to push these patches, or should I?
@mreynolds - I don't know - are they still applicable? Do they even apply against the current code? They are quite old and probably bit-rotted. At any rate, yes, please take over these patches.
Replying to [comment:9 rmeggins]:
Yeah I was wondering about that as well. I'll just have to check them out, thanks
These patches no longer apply, closing ticket
Metadata Update from @rmeggins: - Issue assigned to mreynolds - Issue set to the milestone: lib389 1.0.2
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/1011
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 close_status updated to: wontfix (was: Invalid)
Login to comment on this ticket.