50732c9 Issue 49657 - Fix cascading replication scenario in lib389 API

Authored and Committed by spichugi 5 years ago
    Issue 49657 - Fix cascading replication scenario in lib389 API
    
    Bug description: We should be able to create cascading replication topology
    with existing lib389 API. Fix existing topology in topologies.py
    and add the functionality to replica.py API accordingly.
    
    Fix description: Add the code to join_hub function.
    Get agreement name from the last three port numbers.
    When we call _create_service_group on read-only instance
    do not try to create it.
    Generate the replica credentials when adding the service account
    and store them in ReplicationManager object.
    Fix a few small issues in replica.py.
    In topologies.py, divide the instance and replica creation.
    Refactor topology_m1h1c1 according to the changes.
    During the finalizer, check if instance exists before the removal.
    
    https://pagure.io/389-ds-base/issue/49657
    
    Reviewed by: mreynolds (Thanks!)
    
        
file modified
+113 -67
file modified
+83 -105