With the merge of the two DS instances we can potentially significantly simplify the replication management procedures used to deal with the replication agreements between the servers. Right now the main instance replication agreements and CS replication agreements are independent. It is useful in very advanced configurations when the deployment uses different replication topology for CS and identity data. To simplify replication management i suggest the following scheme.
There is no way to get back.
The whole feature is similar to the managed entries approach and can be explained in the documentation in the similar terms.
We may be enabled to do this effort when #4302 is implemented. Moving to respective milestone.
with the implementation of the topology plugin #4302, this is feature is available. The current design of the topology plugins configures the topology (segments) of a replicated suffix either directly - or by a reference to another managed suffix. So initially a replication configuration can be setup by referencing an existing one.
The initialization of the databases has still to be triggered, there is no automatism planned yet.
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1199516 (Red Hat Enterprise Linux 7)
Postponed, see freeipa-devel for reasoning.
today I did a quick test of what is possible with the current version of the topology plugin and the current replica-install process.
For 6. we need to decide what type of repl agmts we want to use for dogtag database, if it should be different we could add the type and other data to the topology suffix entry and derive defaults from there
for 4/5. I think we do not need this information in the cn=config topo plugin config, the presence of a topology suffix in the shared tree should be enough
In 4.3 CA and Domain agreements are centrally managed using new managed topology feature.
But they are not managed "together" which is the subject of this ticket. This ticket is out of scope of 4.3 release. Moving to 4.4 backlog for future triage, but it's probable that it is out of scope of 4.4 as well.
I think this ticket is now obsolete since we moved agreement management into the topology plugin.
I propose to close it.
triage result: With topology graph in Web UI, topology structure is clear. Therefore this improvement is no longer needed.
Feedback about the topology graph is welcome.
Metadata Update from @dpal:
- Issue assigned to lkrispen
- Issue set to the milestone: 0.0 NEEDS_TRIAGE
to comment on this ticket.