Project

General

Profile

Actions

Feature #27775

closed

Add support for pre-defined tuning profiles for Foreman & Katello installations

Added by Mike McCune about 5 years ago. Updated almost 5 years ago.


Description

We need to be able to offer an easy route for users to tune Foreman & Katello with pre-defined custom-heira settings to reduce the number of steps and errors required to change common configurations needed when Foreman is used in medium to large scale environments.

Downstream has some example templates defined here for:

  • Medium 32G
  • Large 64G
  • Ex-Large 128G
  • 2Ex-Large 256G

[[https://github.com/RedHatSatellite/satellite-support/tree/master/tuning-profiles]]

Through discussion with Ewoud he is proposing we add the ability to deliver similar pre-defined custom-heira templates but be able to include them in the top level /etc/foreman-installer/custom-heira.yaml file via a one line parameter:

tuning::size: large

This would allow us to control the tuning templates and deliver new versions with users not having to change individual settings and preserve changes as upgrades are delivered.

This relies on some changes outlined here to be able to implement:

To automatically provide the scenario info, we need to modify the
heira_configurer right here:

[[https://github.com/theforeman/kafo/blob/8b5c184fc278df90bc55a367982be1c1275f6639/lib/kafo/hiera_configurer.rb#L75-L83]]

The above relies on an updated version of kafo and then requiring installer heirarchy modification outlined here:

https://github.com/theforeman/foreman-installer/blob/1f281337039e3e7d3c31d49935b23e7c0e2dad84/config/foreman-hiera.yaml#L15

The example needs to gain a line or 2 describing it:

[[https://github.com/theforeman/foreman-installer/blob/develop/config/custom-hiera.yaml]]

Lastly, we will need to deliver the pre-defined tuning templates in an RPM as well as properly document this because upgrading users who've modified custom-hiera.yaml will not get the new example.

Actions

Also available in: Atom PDF