We need a tool to help find and potentially correct or guide users through replication conflict management. Such a tool would:
If this is to be consumed by other projects, we may want to add a flag to help improve performance of this such that in our cn=replica we have nsds5conlfictdetected: true|false, so that applications can notify users to trigger the tool.
First, I think the CLI tool should be standalone from dsadm/dsconf, e.g. repltool.py
This tool should do things like:
Most of this functionality is already available in lib389.
Plus we may want to defer working on this on the lib389 side now...
The issue is well known and we are hoping to fix or ease the problem in the 1.3.6 time frame. That could affect the lib389 side. https://bugzilla.redhat.com/show_bug.cgi?id=1274430 https://fedorahosted.org/389/ticket/47784
I'd rather think we should design the conflict entry first, then adjust it to lib389???
I agree with Noriko's points.
I also disagree about the tool. From now, I want all our tools to end up in dsadm/dsconf. We have a "discoverability" problem with tools right now. When I was an admin I had no idea what shipped with the server. We need to be focused on getting our tools into dsadm / dsconf, and then that allows admins to discover what they need. We need to make it easier to find and use tools, not harder.
Replying to [comment:5 firstyear]:
From now, I want all our tools to end up in dsadm/dsconf.
Sounds good to me. I remember you already implemented the framework of dsadm/dsconf.
Do we also have the doc/memo how to add a new functionality to the tool frameworks with the guidance which one should be chosen? Thanks!
http://www.port389.org/docs/389ds/design/dsadm-dsconf.html
As for adding new parts, no docs yet. I should write one.
Cool! Thanks! Let's advertise the doc and make it standard...
Metadata Update from @nhosoi: - Issue assigned to firstyear - Issue set to the milestone: lib389 1.0.3
This was implemented in dsconf, closing ticket....
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mreynolds: - Issue set to the milestone: None (was: lib389 1.0.3)
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/1687
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: fixed)
Login to comment on this ticket.