Enhanced IdM topology management
Information about the Identity Management (IdM) topology is now maintained at a central location in the shared tree. As a result, you can now manage the topology from any IdM server using the command line or the web UI.
Additionally, some topology management operations have been simplified, notably:
* Topology commands have been integrated into the IdM command-line interface, so that you can perform all replica operations using the native IdM command-line tools.
* You can manage replication agreements in the web UI or from the command line using a new and simplified workflow.
* The web UI includes a graph of the IdM topology, which helps visualize the current state of replica relationships.
* IdM includes safety measures that prevent you from accidentally deleting the last certificate authority (CA) master from the topology or isolating a server from the other servers.
* Support for server roles as a simpler way of determining which server in the topology hosts which services as well as installing these services onto a server.
For details, see https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Linux_Domain_Identity_Authentication_and_Policy_Guide/index.html#managing-topology
Note that the new functionality requires raising the domain level to `1`. See https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Linux_Domain_Identity_Authentication_and_Policy_Guide/index.html#domain-level
Description of problem:
As an Administrator I want to manage the IdM Server replication topology from a central location via CLI or UI, so that I can overview the configured topology and easily do changes to the replication agreements of the main or CA database.
Upstream design: http://www.freeipa.org/page/V4/Manage_replication_topology
Unlinking #5883 and #5884:
* topology graph: Add background to the canvas to improve UX
* topology graph: add buttons for zooming the canvas
They are only UX enhancements which won't be addresses in 4.4 upstream release. They don't solve any additional use cases.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-2404.html