3.2.1

• update package version of saptune to 3.2.1
  • restore CPU performance settings on AWS and Google Cloud
    (changes Note 2205917, 2684254 and 3577842)
    (bsc#1250217)
  • SAP Note 2993054 updated to Version 4
    add parameter setting for net.ipv4.tcp_retries2

3.2.0

• update package version of saptune to 3.2.0

  • saptune version 3.2
    new features and SLE16 support
    (jsc#PED-8163)

  • SLE16 - Optimized out-of-the-box experience for SAP workloads
    SLES for SAP Applications should have by default all tunings enabled and packages started that are common for SAP workloads.
    (jsc#PED-10984)

  • SLE16 - Tune common values for SAP workloads per default
    (jsc#PED-10072)

  • SLE16 - OS tuning for SAP with saptune on SLE 16
    (jsc#SAPSOL-526)

  • SLE16 - preparing a SAP Solution 'SAP_Base' with one Note '1275776' to support base tuning on SLES and SLES4SAP 16.
    (jsc#SAPSOL-530)

  • SLE16 - implement new start behavior for saptune on 16.
    If the saptune package gets installed (by pattern or manually) it calls 'saptune solution apply SAP_Base' to initiate the base tuning.
    A customer can change this base tuning after package installation by 'saptune solution change <New_Solution>' or by 'saptune revert all' and 'saptune solution apply <New_Sol>'
    See man page saptune(7) for details
    (jsc#SAPSOL-533)

  • SLE16 - remove saptune-migrate man page
    (jsc#SAPSOL-347)

  • SLE16 - remove saptune daemon commands
    (jsc#SAPSOL-343)

  • SLE16 - remove saptune simulate commands
    (jsc#SAPSOL-345)

  • SLE16 - remove support for setting PAM limits
    (jsc#TEAM-10049, jsc#TEAM-8744)

  • SLE16 - Support dot releases for os tags and rpm version check
    (jsc#SAPSOL-568)

  • SLE16 - remove support for the v1 Custom Note name format
    (jsc#SAPSOL-532)

  • SLE16 - remove support for the comment-style version header format in vendor/custom Notes
    (jsc#SAPSOL-604)

  • SLE16 - drop support for the comment-style version headers
    (jsc#SAPSOL-605)

  • SLE16 - adapt saptune_check script to the new main configuration file location
    (bsc#1244077)

  • Enhanced the saptune supportconfig plugin,
    added 'saptune status', 'saptune note verify', /var/log/zypp,
    'saptune note list', 'saptune solution list',
    'saptune --format json saptune check',
    'saptune --format json note list',
    'saptune --format json solution list',
    'saptune --format json status' and
    'saptune --format json note verify'
    (jsc#SAPSOL-169)

  • Refresh changed Note parameter.
    This action is currently in state 'experimental'
    (jsc#TEAM-3943)

  • Add detection of offline CPUs when setting/verify governor or force_latency settings
    (bsc#1221020, jsc#TEAM-8427)

  • Enhance CPU handling with additional warnings and skip governor settings, if intel_idle and intel_pstate are disabled
    (jsc#TEAM-3759, jsc#TEAM-8427)

  • Set energy perf bias (EPB) even if secure boot is enabled, if the used cpupower command supports the operation.
    (bsc#1224801)

  • Fix Nvme disk detection
    (bsc#1233126)

  • Fix an index error in the rpm section code and explain the compliance/uncompliance state of a rpm version in the man page
    (bsc#1239841)

  • Check if orphaned overwrites exist.
    If an override file exists in /etc/saptune/override, but no related Note definition file or solution definition can be found in the working area /var/lib/saptune/working/ or in the custom/vendor directory /etc/saptune/extra, a warning message is printed and logged.
    Additional a line about orphaned overrides is added to the bottom of the 'saptune status' output.
    (jsc#TEAM-6598)

  • saptune alternatives should not listed as non-compliant
    (jsc#TEAM-8719)

  • Remove '(no change)' leftover for 'saptune note verify'
    (jsc#TEAM-9136)

  • Add json support to 'saptune check'
    Enhance json schema and update to version 1.1
    (jsc#TEAM-8959)

  • Force colored output by using the global option '--force-color'
    With that it will be possible to override the color-suppressing, if a pipe has been detected as there are use cases (e.g. piping into less) where the color codes can be useful.
    (jsc#TEAM-9205)

  • Add new command 'saptune configure ' to change values in the saptune config file.
    (jsc#TEAM-8703)

  • Add new command 'saptune configure reset' to reset the saptune configuration.
    This will revert the tuning (revert all) and reset the saptune configuration file back to the installation default.
    (jsc#SAPSOL-331)

  • Add new command 'saptune configure TrentoASDP ' to configure the discovery interval for saptune on Trento.
    (jsc#SAPSOL-117)

  • Tag handling clarification in the man page.
    The same tag cannot be used multiple times with different values in one section of a Note definition file, because all tags of a section are concatenated by AND (and not OR).
    (jsc#TEAM-9243)

  • Add new tag 'pmu_name' for CPU platform selection.
    May be helpful for special FORCE_LATENCY settings depending on the used CPU platform to get optimal performance.
    As the values are taken from /sys/devices/cpu/caps/pmu_name, it's an Intel CPU only feature for now.
    (jsc#TEAM-7073)

  • Add new tag 'virt' for virtualization type selection.
    Valid values are 'vm', 'chroot' and 'container' as reported by '/usr/bin/systemd-detect-virt -v|-c|-r'
    (jsc#TEAM-6070)

  • Add IBM Cloud VPC (not IBM Cloud Classic) detection used for tag 'csp'
    (jsc#SAPSOL-224)

  • Add additional actions for 'verify'
    'saptune note verify applied' and 'saptune verify applied'
    (jsc#TEAM-9204)

  • For internal used calculations increase the logging information for the used parameters, values and results
    (jsc#SAPSOL-168)

  • Adjust return code from 1 to 128 if a wrong saptune version is detected.
    (jsc#SAPSOL-209)

  • Add systemd hardening to the saptune systemd service file starting 15SP4
    (jsc#TEAM-7425)

  • Add new global option '--fun'. If set, the 'yes', 'no' in the compliant column of 'saptune note verify' is replaced by a smiley.
    (jsc#SAPSOL-236)

  • start reducing duplicate warning and info messages
    (jsc#SAPSOL-669)

  • Adapt man page and help output for global option '--fun'
    (jsc#SAPSOL-272)

  • Add list of exit codes to man page saptune(8)
    (jsc#TEAM-9836)

  • man pages - add warning about race condition of systemd units during system boot.
    saptune-note.5 already contained a description, now saptune.8 was enhanced as well.
    (bsc#1190508)

  • Add new man page saptune-solution(5)
    (jsc#TEAM-9870)

  • Add new man page saptune(7) describing the new tuning behavior during package installation
    (jsc#SAPSOL-533)

  • SLE16 - add new SAP Note 3565382 and 3577842

  • SLE16 - add Note 3577842 to all HANA related solutions
    (bsc#1240598)

  • SLE16 - remove Note 1771258
    (jsc#TEAM-10049)

  • SLE16 - remove ASE Solution and Notes 1680803 and 1805750
    (jsc#SAPSOL-531)

  • SLE12/15 - deprecate Notes 1680803,1805750 and Solution SAP-ASE
    The Note and the Solution might get removed in a future saptune version
    (jsc#SAPSOL-419)

  • SLE12/15 - deprecate Note 1771258
    (jsc#TEAM-8744)

  • SAP Note 2684254 and 2205917
    Intel architecture related settings (currently section 'cpu' and 'grub') are now tagged with 'arch=x86_64' in the Note definition file to no longer confuse customers on other architectures with 'useless' warnings and footnotes.
    And by adding the additional tag 'virt=bare-metal' users of virtual machines will also no longer be confused by these footnotes and warnings.
    (jsc#TEAM-9235)

  • SAP Note 1984787 updated to Version 43
    SAP Note 2578899 updated to Version 53
    SAP Note 3024346 updated to Version 14
    but without parameter value changes, only house keeping of the version section and comment updates

• add obsoletes/provides for sapconf to support the update/move from sapconf to saptune on plain SLES

• change Requires: /usr/bin/cpupower to Requires: cpupower
  and Requires: /usr/bin/md5sum to Requires: coreutils
  (jsc#TEAM-8743)

• add support for SLE16
  Installation and activation of SAP base tuning
  Update to SLE16

3.1.5

• update package version of saptune to 3.1.5
  • on Azure cloud create a saptune service drop-in file to start saptune after cloud-final.service
    (bsc#1235824, jsc#SAPSOL-523)
  • fix NVMe device detection and update man page saptune-note.5
    (bsc#1233126)
  • fix wrong error handling, if system limits.conf file is missing and skip reading system limits.conf file on SLES 16 as it can not contain customer changes
    (bsc#1236232)
  • fix value for grub transparent_hugepage entries in Note 2684254
    (bsc#1235579)

3.1.4

• update package version of saptune to 3.1.4
  • update man page 'saptune.8'.
    add warning about race condition of systemd units during system boot.
    (bsc#1190508)
  • for all note definition files we changed the link location for the related SAP Notes from 'launchpad.support.sap.com' to the new 'me.sap.com' location.
    (bsc#1232212)
  • SAP Note 1656250 updated to Version 69
    SAP Note 1805750 updated to Version 10
    SAP Note 2993054 updated to Version 3
    but without parameter value changes, only house keeping of the version section
    (bsc#1232212)
  • SAP Note 1680803 updated to Version 28
    SAP Note 2382421 updated to Version 47
    SAP Note 2578899 updated to Version 50
    SAP Note 2684254 updated to Version 24
    SAP Note 3024346 updated to Version 12
    (bsc#1232212)
  • With SAP Note 2684254 updated to Version 24 the setting of transparent hugepages (THP) will change from 'never' to 'madvise' for systems running 15SP5 and higher.

3.1.3

• update package version of saptune to 3.1.3

  • remove note 1868829 from solution S4HANA-APPSERVER as it is a HANA DB note and was added by accident
    (bsc#1226093)
  • for verify and simulate output table - wrap content of the columns 'actual', 'expected' and 'override', if they exceed a width of 30 characters (e.g. net.ipv4.ip_local_reserved_ports)
  • support inline comments in /etc/sysconfig/saptune
  • change handling of the performance options.
    Check, if the settings are supported in the get-Functions too.
    This should fix the problem with some special Azure VMs (E20d_v5) on newer SLES SPs
    (jsc#SAPSOL-110)
  • SAP Note 2578899 updated to Version 48
    setting kernel.pid_max to 4194304 and
    start sysctl-logger service

3.1.2

• update package version of saptune to 3.1.2

  • to support setups with saptune monitoring and heavy automation we limited the setting of our saptune lock to commands having
    the potential to change anything in the system.
    (bsc#1219500)
  • fix timestamp in log messages of saptune
  • remove redundant version information in header comment of note definition files
  • SAP Note 1656250 updated to Version 63
    SAP Note 1771258 updated to Version 8
    SAP Note 2382421 updated to Version 45
    SAP Note 3024346 updated to Version 10
    but without parameter value changes, only house keeping of the version section and comment updates
  • SAP Note 1984787 updated to Version 42
    SAP Note 2578899 updated to Version 47

• add require of package sysctl-logger
  (jsc#PED-5025)

3.1.1

• update package version of saptune to 3.1.1

  • typo in logfile directory name creates /varlog/saptune instead of /var/log/saptune
    (bsc#1215969)
  • SAP Note 2382421
    fix missing handling for Azure systems regarding parameter 'net.ipv4.tcp_timestamps'. This exclude setting was left out during the last SAP Note update by mistake.
  • add parameter IGNORE_RELOAD to /etc/sysconfig/saptune to prevent saptune from stopping and starting the system tuning during package update
    Related to sapconf bug bsc#1209408.

• create a flag file in preinstall and remove it in posttrans of the package installation to inform saptune that currently a package installation/update takes place so that some special situations can be handled as expected.

3.1.0

• update package version of saptune to 3.1.0
• machine readable interfaces for saptune
  add json output support
  related json v1 schemas can be found after installation on the system at /usr/share/saptune/schemas/1.0/
  (jsc#PED-2194, jsc#PED-2195, jsc#SLE-23696)
• enhance the identification of the cloud service provider
  (jsc#SLE-23779)
• add a command line syntax check
• colorized and filtered output for 'saptune note verify'
  It is now possible to uses a 'color scheme' for the output to highlight the non-compliant parameter or to limit the verify output to show only non-compliant parameter.
  (jsc#SLE-23727)
• add action 'saptune solution change' to switch to a new solution even that another solution was already applied.
  It's basically a 'revert OLDSOLUTION' && 'apply NEWSOLUTION'.
  This will change the Note order in case of additional applied Notes, but this is intended.
  The confirmation for the revert of the old solution can be suppressed by '--force'
  (jsc#PED-2196)
• introduce a Trento naming convention for custom solutions in the saptune man page to support trento checks.
  (jsc#PED-4118)
• deprecate action 'saptune note|solution simulate'.
  The action might get removed in a future saptune version
  (jsc#PED-2199)
• deprecate support for the v1 vendor or custom specific Note definition file format
  (jsc#SLE-23725)
• detect virtualization environment by 'systemd-detect-virt' and add the information to 'saptune status'.
  (jsc#SLE-23885)
• enhance saptune with the new action 'check' to directly call the external check script '/usr/sbin/saptune_check'.
  (jsc#SLE-23726)
• de-deprecate the MAXDB solution definition. It is still active supported by SAP.
  And add solution NETWEAVER+MAXDB
  (jsc#SLE-23724)
• support inline comments in the Note definition files
  (jsc#SLE-23729)
• rework Note representation in 'saptune status' output
  (jsc#SLE-24530)
• fix problem with 'verify' output, if a sysctl parameter is empty on the system
  (bsc#1199527)
• add hint to the manual page of saptune(8) regarding 'missing' line feed for 'saptune note applied' and 'saptune note enabled'.
  It's intended.
  (bsc#1193714)
• rework the version section to make it clear, which information needs to be provided
  (jsc#SLE-23722)
• add more information to 'saptune status':
  differ between 'enabled' and 'applied' Solutions and add the related Notes.
  differ between Notes and Solutions in the staging area.
  rename 'system state' line to 'systemd system state' to prevent misunderstandings.
  add virtualisation information.
• add tuning state to 'saptune status' output.
  The check of the tuning state (an internal 'verify' operation) can be skipped by using the flag '--non-compliance-check'.
  In this case the tuning state will be reported as unknown (checking disabled)
  'saptune status' will exit with a return code of '4', if the saptune service is enabled, the system is tuned, but the tuning state is 'not compliant'.
  (jsc#SLE-24928)
• add support for the IBM Power architecture to the vendor and model section tagging
  (jsc#SLE-23824)
• add new SAP Note 1868829 to set fs.aio-max-nr and add it to the HANADB related solutions.
• SAP Note 3024346 updated to Version 6
  SAP Note 1557506 updated to Version 16
  SAP Note 1656250 updated to Version 46
  SAP Note 1805750 updated to Version 9
  SAP Note 2161991 updated to Version 28
  SAP Note 2205917 updated to Version 63
  SAP Note 2382421 updated to Version 45
  SAP Note 2534844 updated to Version 15
  SAP Note BOBJ updated to Version 1
  but without parameter value changes, only house keeping of the version section and comment updates
• SAP Note 1984787 updated to Version 40
  SAP Note 2578899 updated to Version 46
  SAP Note 2684254 updated to Version 23
  SAP Note 1680803 updated to Version 27
  includes version 3.1 of 'SAP Applications on SAP Adaptive Server Enterprise - Best Practices for Migration and Runtime'
• Solution 'SAP-ASE' changed - remove SAP Note 1410736.
  The best practice document (version 3.1) for ASE was changed and the SAP Note 1410736 is no longer referenced.
  Instead the parameter 'net.ipv4.tcp_keepalive_time' is set in SAP Note 1680803 (the ASE SAP Note) directly.
• introduce an additional parameter 'SKIP_SYSCTL_FILES' in the /etc/sysconfig/saptune configuration file, which contains a comma separated list of sysctl.conf files or directories containing sysctl.conf files, which should be excluded from the 'additional defined' WARNING messages.
  Default is
  SKIP_SYSCTL_FILES="/boot"
  to skip the WARNINGS for '/boot/sysctl.conf-'
• check in preinstall and posttrans of the package installation, if the active tuned profile is still 'saptune', even that this profile no longer exists. If yes, try to remove it.
  (bsc#1194688)

3.0.2

• update package version of saptune to 3.0.2
• avoid excluding LVM slaves when getting valid block devices
  (bsc#1194299)
• fix 'not compliant' state for energy_perf_bias on Power systems and suppress misleading error message regarding missing 'mokutil'
  (bsc#1193435)
• fix wrong behaviour of 'saptune revert all', if the saptune service was stopped between the two commands 'apply' and 'revert all'
• 'saptune service enablestart|disablestop' now always perform both actions and does no longer stop working, if the service is already started|stopped.
  (bsc#1193241)
• restrict the sys section of the AWS note 1656250 to the availability of a nvme block device to support AWS x1e instances too.
  sys section definition of Note 1656250 changed.
  (bsc#1192029)
• abandon the dependency to 'mokutil' by relying on sysfs to detect a secure boot environment.
  Related to bsc#1193435
• support /etc/fstab entries with 4 instead of 6 fields as these are valid entries.
  Change error handling from 'panic' to error log messages.
  (bsc#1193580)
• enhance man page 'saptune.8'.
  Add entry 'configured Note' and some more descriptions of the entries from 'saptune service status'
  (bsc#1192697)
• as the Power systems (hardware architecture 'ppc64le') does not support files in '/sys/class/dmi' (this directory is not available on the 'ppc64le' hardware architecture) some of our section 'tags' will not work.
  Add some additional log messages to identify the cause and add a hint to the man page.
• fix block device settings (e.g. NRREQ) for multipath devices
  (bsc#1193576)
• 'saptune verify' will now report a non existing sysctl or sys parameter as 'not available on the system' (footnote) and this parameter will not affect the compliance state.
  But a warning is displayed to raise attention to may be typos in the parameter name.
• 'saptune status' now reports the 'real' unit state, no mapping of not running (inactive) service to simply 'stopped' any more.
  (bsc#1194334)

3.0.1

• update package version of saptune to 3.0.1
• fix the scheduler settings for multi path devices and suppress missleading warning messages regarding vendor and model information during block device detection
  (bsc#1192460)
• fix override of custom solutions
  (bsc#1192062)
• add missing update function for enabled solutions and add a special fix to correct the 3.0.0 behavior
  (bsc#1192053)
• saptune_check - degraded system is no longer considered an error
  (bsc#1192272)
• log missing model and vendor information to the saptune log file
  (bsc#1190509)