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)