[OPENDJ-6864] Replication domains should be named using their base-dn property Created: 16/Dec/19  Updated: 28/Jul/20

Status: Dev backlog
Project: OpenDJ
Component/s: config, ease of use, replication, tech-debt
Affects Version/s: 7.0.0
Fix Version/s: None

Type: Task Priority: Major
Reporter: Matthew Swift Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None

Epic Link: Miscellaneous 2020.Winter

 Description   

Using dsconfig to configure a replication domain I was surprised to be asked twice for the base DN:

>>>> Replication Domain management menu
What would you like to do?
    1)  Create a new Replication Domain
    2)  View and edit an existing Replication Domain
    3)  Delete an existing Replication Domain
    4)  List existing Replication Domains
    a)  show advanced components and properties
    q)  quit
    b)  back
Enter choice [b]: 1
>>>> There is only one Replication Synchronization Provider: "Multimaster
Synchronization". Are you sure that this is the correct one? (yes / no) [yes]: 
>>>> Enter a name for the Replication Domain that you want to create: dc=example,dc=com
>>>> Configuring the "base-dn" property
    Specifies the base DN of the replicated data.
    Syntax:  DN
Enter a value for the "base-dn" property: dc=example,dc=com

We should name replication domains using the base-dn property in a similar fashion to what we do already for backends and indexes.



 Comments   
Comment by Ludovic Poitou [ 16/Dec/19 ]

Backends are not named using the base-dn, but using a backend-id which is a string.

Therefore I agree with you, we should name replication domains with an identifier which is a string and not a string built from the base-dn.

How about using cn as there is no other attribute in the replication domains than the base-dn?

Comment by Matthew Swift [ 16/Dec/19 ]

Ludovic Poitou - what???

A backend has multiple base DNs, so it cannot be named using its base DN. It must have a single directory which is determined by its backend ID, which is case-insensitive IIRC.

Replication domains only have a single DN which is unique among other domains. There's no point in confusing the user with an additional unneeded method of naming.

Comment by Ludovic Poitou [ 16/Dec/19 ]

Just saying that backends do not use a DN as the RDN... And I think we should avoid these nested DN names

Generated at Fri Oct 23 08:33:53 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.