Bug 1449707

Summary: Persist postgresql customisations from the perf & scaling tuning guide
Product: Red Hat Satellite Reporter: Julio Entrena Perez <jentrena>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.9CC: stbenjam
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-10 13:37:12 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:
Attachments:
Description Flags
2016 - Performance & Scale Tuning of Satellite 6.2 and Capsules none

Description Julio Entrena Perez 2017-05-10 13:21:50 UTC 
Created attachment 1277618 [details]
2016 - Performance & Scale Tuning of Satellite 6.2 and Capsules

Description of problem:
Pages 24 and 25 of the performance and scale tuning guide for Satellite 6.2 available at https://access.redhat.com/articles/2626101 suggest to customise the following PostgreSQL settings:

- /var/lib/pgsql/data/postgresql.conf
  shared_buffers
  max_connections

Currently when the installer runs, for example when upgrading to the next minor release, these customisations are wiped and replaced with the default values.

There does not seem to be any way of persisting these changes across executions of the installer in file /etc/foreman-installer/custom-hiera.yaml .

This results in minor upgrades bringing back previous issues if customers aren't vigilant and re-apply the changes after each upgrade.

We should provide a way to persist these changes in /etc/foreman-installer/custom-hiera.yaml

Version-Release number of selected component (if applicable):
foreman-installer-1.11.0.15-2.el7sat

How reproducible:
Always

Steps to Reproduce:
1. Customise the settings as per above
2. Run "satellite-installer --scenario satellite --upgrade"
3. Check for the previously applied customisations

Actual results:
Customisations are gone.

Expected results:
Customisations are there after the execution of the installer.

Additional info:
Comment 2 Stephen Benjamin 2017-05-10 13:37:12 UTC 

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