If the following variable is set to no, only certain steps of SAP notes will be executed or checked as per setting of variable sap_hana_preconfigure_<sap_note_number>_<step>. If this variable is undefined or set to yes, all installation and configuration steps of applicable SAP notes will be executed.

If you have set sap_hana_preconfigure_config_all (see above) to no, you can limit the scope of the role to only execute the installation or the configuration steps. For this purpose, set one of the following variables, or both, to yes. The default for both is no.

For defining one or more configuration steps of SAP notes to be executed or checked only, set variable sap_hana_preconfigure_config_all to no, sap_hana_preconfigure_configuration to yes, and one or more of the following variables to yes:

If the following variable is set to yes, the role will only check if the configuration of the managed node(s) is according to the applicable SAP notes. Default is no.

If the role is run in assert mode (see above) and the following variable is set to yes, assertion errors will not cause the role to fail. This can be useful for creating reports. Default is no, meaning that the role will fail for any assertion error which is discovered. This variable has no meaning if the role is not run in assert mode.

If the following variable is set to yes, if the role is configured with variable sap_hana_preconfigure_assert being set to yes, the role will check all configuration steps no matter of the setting of the tuned and grub variables. Default is no, meaning that only those configuration steps are checked which are enabled by the tuned and grub variables. Example: If variable sap_hana_preconfigure_modify_grub_cmdline_linux is set to no, when running the role in assert mode, the role will not check if the grub command line has been modified according to this role.

If the following variable is set to no, the role will install packages and modify settings on the managed node even if the RHEL release is not contained in the list of supported RHEL releases. Default is yes. In assert mode (sap_hana_preconfigure_assert = yes), the role will always perform the RHEL release check but will display display "WARN" or "INFO" if the variable is set to no, instead of the default "FAIL" or "PASS".

If you want to provide you own list of supported RHEL releases (e.g. for testing), override the variable. Otherwise, the defaults as set in vars/RedHat_*.yml will be used.

If you want the role to check and if necessary enable SAP HANA repos, set the following variable to yes. Default is no.

If you want to provide you own list(s) of repositories for checking and enabling, override one or more of the following variables. Otherwise, the defaults as set in vars/RedHat_*.yml will be used.

If you want the role to set the RHEL release to a certain fixed minor release (according to installed RHEL release), set the following variable to yes. Default is no.

The following variable will make sure packages are installed at minimum required versions as defined in files vars/*.yml. Default is yes.

If the following variable is set to yes, the role will run a yum update before performing configuration changes. Default is no.
Note: The outcome of a yum update depends on the managed node’s configuration for sticky OS minor version, see the description of the release option in man subscription-manager. For SAP HANA installations, setting a certain minor version with subscription-manager release --set=X.Y is a strict requirement.

SAP Note 238241 defines kernel parameters that all Linux systems need to set. The default parameter recomendations are dependent on the OS release. Hence the OS dependant default setting is defined in ./vars/{{ansible_os_release}}.yml. If you need to add or change parameters for your system, copy these parameters from the vars file into the variable sap_hana_preconfigure_kernel_parameters and add or change your settings, as in the following example:

SAP Note 2055470 contains links to IBM documents for SAP HANA on POWER. Among these is a document which contains certain recommended Linux kernel settings for SAP HANA on POWER: Network_Configuration_for_HANA_Workloads_on_IBM_Power_Servers_V7.1.pdf. This document is linked from SAP note 2055470 via "SAP HANA on IBM Power Systems and IBM System Storage - Guides", then via "SAP on Linux and IBM Storage Guides (incl. HANA)", and then via "SAP on Power Linux Network and Fibre Channel Guides". The default parameter recommendations are defined in ./vars/{{ansible_os_release}}.yml. If you need to add or change parameters for your system, copy these parameters from the vars file into the variable sap_hana_preconfigure_kernel_parameters_ppc64le and add or change your settings, similar to the previous example.

SAP Note 3024346 defines kernel parameter settings for NetApp NFS. In case you want the role to set or check these parameters, set the following variable to yes. Default is no.

In case you do not want to automatically add the repository for the IBM service and productivity tools, set the following variable to no. Default is yes, meaning that the role will download and install the package specified in variable sap_hana_preconfigure_ibm_power_repo_url (see below) and also run the command /opt/ibm/lop/configure to accept the license.

The following variable is set to the location of package ibm-power-repo-lastest.noarch.rpm or a package with similar contents, as defined by variable __sap_hana_preconfigure_ibm_power_repo_url in vars/RedHat_7.yml and vars/RedHat_8.yml. You can replace it by your own URL by setting this variable to a different URL.

If the following variable is set to yes, the role will reboot the managed node if required. The default is no, in which case the role will only report that a reboot is required.

In case sap_hana_preconfigure_reboot_ok (see above) is set to no, we should make sure that a reboot requirement does not remain unnoticed. The following variable will cause the role to fail if a reboot is required, if undefined or set to yes, which is also the default. By setting the variable to no, the role will not fail if a reboot is required but just print a warning message.

By default, the role will activate tuned profile sap-hana for configuring kernel parameters (where possible). If you do not want to use the tuned profile sap-hana, set the following variable to no. In this case, the role will also modify GRUB_CMDLINE_LINUX, no matter how variable sap_hana_preconfigure_modify_grub_cmdline_linux (see below) is set. Note: If this variable is set to yes, the role may still modify GRUB_CMDLINE_LINUX in /etc/default/grub, by setting variable sap_hana_preconfigure_modify_grub_cmdline_linux to yes. This provides more flexibility for setting certain kernel parameters.

If you want to modify the grub2 line GRUB_CMDLINE_LINUX in /etc/default/grub, set the following variable to yes. The default is no. Setting this variable to yes probably only makes sense if sap_hana_preconfigure_run_grub2_mkconfig (see below) is also set to yes. Note: If variable sap_hana_preconfigure_use_tuned (see above) is set to no, GRUB_CMDLINE_LINUX will modified in any case, no matter how variable sap_hana_preconfigure_modify_grub_cmdline_linux is set. This is to guarantee that either the tuned settings or the static settings will be applied. If variable sap_hana_preconfigure_use_tuned (see above) is set to yes, sap_hana_preconfigure_modify_grub_cmdline_linux can still be set to yes for modifying GRUB_CMDLINE_LINUX, providing more flexibility for setting certain kernel parameters.

If you do not want to run grub2-mkconfig to regenerate the grub2 config file after a change to /etc/default/grub (see the desciption of the two previous parameters), set the following variable to no. The default is yes.

These variables are used in all sap-hana roles so that they are only prefixed with sap-hana. If you use sap-hana-mediacheck role, these variables are read in automatically. The variable is used in the checks for SAP Note 2235581.