Bug 1303158

Summary: add Features feature to ldap
Product: Red Hat Enterprise Linux 7 Reporter: Matthew Harmsen <mharmsen>
Component: pki-coreAssignee: Ade Lee <alee>
Status: CLOSED UPSTREAM QA Contact: Asha Akkiangady <aakkiang>
Severity: unspecified Docs Contact:
Priority: high    
Version: 7.3CC: arubin, nkinder
Target Milestone: rcKeywords: FutureFeature
Target Release: 7.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 20:28:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matthew Harmsen 2016-01-29 17:55:54 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/pki/ticket/1634

From review point with ftweedal on original Features feature:

> I think that we should store the config in LDAP so that a change on
> one replica is effected on clones.  Obviously this is a fair bit
> more work I am OK with using CS.cfg initially but we should have
> this discussion.
> 

Agreed that this is something we should discuss.  Part of the reason this is system specific though is that people tend to update one system at a time -- in case something goes wrong.  So you can very easily see a situation where a feature is available on one system but not another.

Still, having it in LDAP would allow doing things like enabling features topology-wide for instance.
Comment 2 Matthew Harmsen 2016-04-21 15:42:47 UTC 
Per CS Bug/Ticket Triage held 04/19/2016:  RHEL 7.4

Confirmed with alee and ftweedal:

    I think 10.4/RHEL 7.4 is OK; AFAIK we won't have any features likely
    to be dynamically enabled or disabled during deployment lifecycle.
Comment 5 Matthew Harmsen 2018-04-10 20:28:22 UTC 
Per RHEL 7.5.z/7.6/8.0 Triage:

edewata: close RHEL bug, keep upstream ticket in FUTURE