Created attachment 1277617 [details] 2016 - Performance & Scale Tuning of Satellite 6.2 and Capsules Description of problem: Page 17 of the performance and scale tuning guide for Satellite 6.2 available at https://access.redhat.com/articles/2626101 suggests to customise the following settings in the following files: - File /etc/httpd/conf.d/05-foreman-ssl.conf PassengerMaxPoolSize PassengerMaxRequestQueueSize PassengerStatThrottleRate PassengerMaxRequests - File /etc/httpd/conf.d/25-puppet.conf PassengerMinInstances PassengerStartTimeout PassengerMaxPreloaderIdleTime PassengerMaxRequests PassengerPreStart 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:
This is a breakdown of how each item can be set, and which items can be set globally and which can be set per vhost. To begin with, the one value that cannot be set at all currently for the puppet vhost: PassengerMaxPreloaderIdleTime For puppet vhost: PassengerMinInstances: can be set with --puppet-passenger-min-instances PassengerPreStart: can be set with --puppet-passenger-pre-start Globally, that is, it affects both Foreman and Puppet vhosts, the following are set by default in hiera and can be customized: PassengerMaxPoolSize: set to 12 by default PassengerMaxRequestQueueSize: set to 250 by default PassengerStatThrottleRate: set to 120 by default PassengerMaxRequests: set to 10000 by default The following have to be set by the user using a custom hiera config: PassengerStartTimeout Given PassengerMaxPreloaderIdleTime has no current way to set it, I would ask what effect it has on the tuning. Further, I would recommend splitting that out to its own BZ and consider the rest of whats laid out here to be done and part of this BZ.
This is resolved and able to be set in custom-heira.yaml in 6.3 and later