Bug 1472585

Summary: expose common settings for custom-hiera.yaml
Product: Red Hat Satellite Reporter: sbadhwar
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.10CC: bbuckingham, cduryee, jhutar, mmccune, psuriset, sbadhwar
Target Milestone: Unspecified   
Target Release: Unused   
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: 2017-08-04 14:11:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description sbadhwar 2017-07-19 04:30:47 UTC 
Description of problem:
The performance brief for Red Hat Satellite mentions several tuning which cannot be persisted across the upgrades of Satellite. On drilling down the issue, it appears that, the puppet modules that ship with the satellite-installer does not have the specific settings exposed through them.

Some of the settings that are missing support include:
1). QPID max-connections under /etc/qpid/qpidd.conf
2). max_connections under /var/lib/pgsql/data/postgresql.conf
3). PassengerMaxPoolSize under /etc/httpd/conf.d/passenger.conf

Can we expose these settings through the puppet modules that ship with the satellite-installer

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Brad Buckingham 2017-08-04 14:11:35 UTC 

*** This bug has been marked as a duplicate of bug 1443138 ***