Description of problem: Various default values ([1], [2], [3]) limit Satellite6 usage to various maximal number of content hosts. A user has to manually tune the system when wanting more content hosts. As many Satellite deployments are supposed to hit either of the limit, the tuning is required for most deployments. It can be written down in manuals (see bz1159281) or even better done automatically by installer to: - simplify the manual steps during installation - prevent (resolving) customer issues when not following that recommendations Therefore I suggest having an option reflecting deployment size (in # of content hosts) that will update the settings. Alternativelly, the installer can set the parameters everytime to some safely high values (i.e. for 10k content hosts or so). [1] https://bugzilla.redhat.com/show_bug.cgi?id=1159281#c0 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1159281#c4 [3] https://bugzilla.redhat.com/show_bug.cgi?id=1159281#c12 Version-Release number of selected component (if applicable): katello-installer-2.3.5-1.el7sat.noarch How reproducible: 100% Steps to Reproduce: 1. Run katello-installer in either way. Actual results: parameters mentioned in bz1159281#c0, bz1159281#c4 and bz1159281#c12 have default values. Expected results: Have possibility to fine tune the values for larger deployments automatically. Additional info:
Per 6.3 planning, moving out non acked bugs to the backlog
Created redmine issue http://projects.theforeman.org/issues/16950 from this bug
Might it make sense to have the installer query the database to determine a rough size on an upgrade? That will help sites that grew beyond their estimates.
For those following this bug, there is a partial solution noted in the 6.5 Quick Tuning Guide: https://access.redhat.com/solutions/4224211 See "2.2 Quick Tuning Guide" additional work will be done to build this directly into the installer.
Upstream bug assigned to ekohlvan
This issue has been successfully verified in 6.7 Snap10, now user can change the deployment size as per their requirement using satellite-installer. # satellite-installer --help --tuning INSTALLATION_SIZE Tune for an installation size. Choices: default, medium, large, extra-large, extra-extra-large (default: "default") # satellite-installer --tuning medium --disable-system-checks Installing Done [100%] [................................................................................................................................] Success! # grep tuning /etc/foreman-installer/scenarios.d/satellite.yaml tuning: medium :tuning: medium
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:1454