Lib389 'replica' should support enableReplication like it was before the enhancement https://pagure.io/389-ds-base/issue/49516.
EnableReplication is a low level interface that is useful to write specific tests. It could be used for higher level interface like create_first_master.
In addition 'dsctl' should provide a way to call enableReplication
1.4
Call to enableReplication is now failing to enable replication on a master
enableReplication fails
enableReplication fails and 'dsctl' should call it on 'enable-repl'
I agree with the proposal. :) A couple of thoughts: - I think we can add method enable_replication(instance, role, replicaid, properties) to ReplicationManager class. We will use it in other methods like create_firt_master(), join_master(), etc. properties will contain replica attributes we want to use instead of the default ones. If the caller explicitly specifies nsDS5ReplicaBindDN or nsDS5ReplicaBindDNGroup, we don't create the default user/group (so the user must create it by himself). - dsconf probably would be better for the replica configuration. As I see our CLI tools, dsclt is for controlling existing instance not for configuring.
enable_replication(instance, role, replicaid, properties)
ReplicationManager
create_firt_master(), join_master()
properties
dsconf
dsclt
Metadata Update from @spichugi: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.0
dsconf now fully supports replication, fyi...
https://access.redhat.com/documentation/en-us/red_hat_directory_server/11/html/administration_guide/single-master_replication#setting_up_single-master_replication_using_the_command_line
Metadata Update from @vashirov: - Issue priority set to: minor - Issue set to the milestone: 1.4.4 (was: 1.4.0)
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/2843
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 - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.