saptune 3.2 has been released!

Refresh

saptune note refresh

New Options

--force-color

--fun

JSON support for saptune check

The CPU tuning now will only be part on x86_64 bare metal systems. This addresses a recent request to not show CPU tuning on virtual machines on verify. Until now saptune has internally detected the impossibility of tuning CPUs under certain circumstances and explained it by warnings and footnotes. Some customers were worried even though.

This also means, that on virtual machines or on IBM Power systems, CPU tuning is not shown on verify including their GRUB counterparts:

The screenshot also shows a second improvement. As you know, some tunings can be done by different ways, namely:

• C-state settings: force_latency versus grub:intel_idle.max_cstate/grub:processor.max_cstate
• NUMA balancing: kernel.numa_balancing versus grub:numa_balancing
• Transparent Huge Pages: THP versus grub:transparent_hugepage

Before 3.2 missing GRUB entries have been listed as non-compliant (theoretically correct), but the overall compliance was met, if the alternatives have tuned the system. This caused confusion. Now the GRUB entries are marked with `-` if the counterpart is tuning the setting.

Man Page Additions

Two man pages have been added:

• saptune-solution(5)
• saptune(7)

With the feature set for Solutions growing, it was time for a dedicated man page.

In saptune(7) we will collect general information about saptune. For now it only contains an outlook to the behavior on the upcoming SLE 16.

Time To Say Good Bye!

When new things come, old ones have to go.

Some are finally gone now and some others are marked as deprecated.

Now is the time to check and update workflows and scripts!

saptune daemon

Ok, that is not a new one. For some version (== years) the commands saptune daemon start|stop|status are marked as deprecated and internally are redirected to their saptune service replacements. Now it gets serious.
In 3.2 for the upcoming SLE 16 the commands are removed and will not work anymore!

saptune note|solution simulate

The simulate commands are not really necessary and were rarely used.
They are marked as deprecated now and in 3.2 for the upcoming SLE 16 they are removed and will not work anymore!

saptune v1 file format

This should harm nobody. saptune warns for quite some time if the old deprecated format is found, but kept working.
In 3.2 for the upcoming SLE 16 support is removed and v1 custom Notes are ignored!
For your own custom Notes, the fix is quite simple: Just add a `[VERSION]` section.

ASE Solution, SAP Notes 1680803 and 1805750

After removing almost any OS tuning in their guides, we talked to the responsible SAP department and came to the conclusion, that the OS defaults on SLES are more than sufficient by now and additional tuning is not required anymore. With 3.2 we deprecate:

• “1680803 – SYB: SAP Adaptive Server Enterprise – Best Practice for SAP Business Suite and SAP BW”,
• “1805750 – SYB: Usage of HugePages on Linux Systems with SAP Sybase ASE” and the
• “ASE” Solution

In 3.2 for the upcoming SLE 16 all are removed and will not available anymore!

SAP Note 1771258

Another SAP Note that falls victim to progress. Setting limits via limits.conf only works for SAP instances started by SysV init scripts. For instances started by systemd, the limits must be set via a drop-in for the service unit and the nofile limit mentioned in the SAP Note is already set to the recommended value in the shipped one.
Therefore we have deprecated the SAP Note “1771258 – Linux: User and system resource limits” and the `LIMIT` feature itself.
In 3.2 for the upcoming SLE 16 it is removed and not available anymore! SLE 16 has no SysV support anyway and SAP systems must be started by systemd.

For SLES 12 and 15 it will not be removed as long SysV-based SAP software is supported.

ProtectSystem=full
ReadWritePaths=/etc/systemd/system/
ProtectHome=true
PrivateDevices=true
ProtectHostname=true
ProtectClock=true
ProtectKernelTunables=false
ProtectKernelModules=true
ProtectKernelLogs=true
ProtectControlGroups=false
MountAPIVFS=no
RestrictRealtime=true