tbordaz / 389-ds-base

Forked from 389-ds-base 7 years ago
Clone

bf6e486 Ticket - 51189 integrate changelog in main database - update CLI

Authored and Committed by tbordaz 3 years ago
    Ticket - 51189 integrate changelog in main database - update CLI
    
    Bug description:
        PHASE 2 of backend redesign:
        http://www.port389.org/docs/389ds/design/integrate-changelog-database-and-backend-database.html
        With https://pagure.io/389-ds-base/issue/49562, the changelog uses the main database.
        Changelog configuration was managed with a global config entry (cn=changelog5,cn=config)
        Now it is managed via a per backend config entry (cn=changelog,cn=<backend_entry>).
        Some config parameters are now in the backend specific changelog entry
    	nsslapd-changelogmaxage
    	nsslapd-changelogmaxentries
    	nsslapd-changelogtrim-interval
        Some config paramters are simply abandonned (see design):
    	nsslapd-changelogdir
    	nsslapd-changelogcompactdb-interval
    
    Fix description:
        This fix (PR) is to be applied on top of 49562
        It suppressed the ablity to create/delete changelog as the changelog entry
        is now created/suppressed when a backend becomes a replica or not.
    
        subcommands to set/get changelog attributes requires a suffix (aka backend).
    	dsconf <inst> replication set-changelog --suffix <suffix>  --trim-interval <val>
    	dsconf <inst> replication set-changelog --suffix <suffix>  --max-age <val>
    	dsconf <inst> replication set-changelog --suffix <suffix>  --max-entries <val>
    	dsconf <inst> replication get-changelog --suffix <suffix>
    
        This patch removes the ability to restore a changelog (restore-changelog)
        It implements a new 'class Changelog' to set/get the configuration attribute
        of a per backend changelog
    
    https://pagure.io/389-ds-base/issue/51189
    
    Reviewed by: Simon Pichugin, Mark Reynolds (Big thanks)
    
        
file modified
+61 -1