saptune 3 is here!
A few weeks ago I announced the upcoming release of saptune 3 https://blogs.sap.com/2021/09/28/saptune-3-is-on-the-horizon/ and what it will bring.
Now the time is up!
Around the end of last week saptune 3.0.0 turned up (almost) in the official repositories for:
- SUSE Linux Enterprise Server for SAP Applications 12 SP3
- SUSE Linux Enterprise Server for SAP Applications 12 SP4
- SUSE Linux Enterprise Server for SAP Applications 12 SP5
- SUSE Linux Enterprise Server for SAP Applications 15 (in a few days)
- SUSE Linux Enterprise Server for SAP Applications 15 SP1
- SUSE Linux Enterprise Server for SAP Applications 15 SP2
- SUSE Linux Enterprise Server for SAP Applications 15 SP3
The SLES for SAP Applications Guide (https://documentation.suse.com/) as well as SAP Note 1275776 have been updated.
As always the man pages shipped with the package are the most detailed source of information.
For those who love to lean back and watch some videos to see how things work, I plan to start with a technical saptune series on the YouTube SUSE Products channel very soon. Watch out for a blog post here about it!
I had some issues with saptune 3 and systems running in the cloud (Azure, GCP) with the official SUSE images.
The first one is not really a saptune issue.But saptune_check reports failed services. And one of them is apparmor. From my perspective the service is not able to run because the image seems to be a minimal installation and the pattern "apparmor" is not completely installed. And so the service could not start because of missing profiles. And the profiles are part of a package which is not installed in the image. So maybe you could forward this issue to the colleagues who are responsible for building the images for the marketplaces of the hyperscaler. According to the SAP notes the apparmor pattern should be installed starting with SLES15.
But is a failed service a problem for saptune? In my case I also had an failure in the fstab, causing a panic during the startup of saptune. Because of the two failures I'm not sure if the [FAIL] because of the services was also a showstopper or not.
So I fixed both issues and saptune was running. But not all parameters were applied. "saptune solution enabled" said "HANA (partial)". I tried it with "saptune solution apply HANA" but the answer war "There is already one solution applied". At the end I had to revert the solution to be able to apply it again. Is this the correct way to correct an already, but only partially, applied solution?
We are preparing an update package for saptune (3.0.1) currently which should be available within the next few weeks. Besides some minor bug fixing it also contains a new version of saptune_check.
That version will report a degraded system (services failed) only as a warning not a fail. If sapconf.service or saptune.service failed, this will reported as an error by the service check itself.
It is hard to tell if a failed service (besides saptune itself of cause) can be a problem. At least it indicates, that something is not right on the system and this needs to be investigated. It might cause issues, it might not. We decided to keep this degradation check in saptune_check to point to ( potential) problems.
I guess the partial applied solution is one of the bugs I mentioned. If a solution is applied, the update to v3 adds the new Cloud Notes, but marks them as manualy removed. This leads to a partial solution. The only workaround is exactly that would you did. Revert everything and re-apply the solution. Sorry for that.
The upcoming update will fix this.
Regarding the Marketplace images. Would you please open a SR or SAP Incident (BC-OP-LNX-SUSE) for this? This should ensure proper attention.
Thank you for sharing this info!
I've read some documentation about saptune v3, however I'm not able to find why is only a valid path migration from v1? I wonder if you can share some considerations moving from v2 to v3.0.2, taking into account v>3 are not using tuned service any more.
Sorry, but I don't get the question about path migration.
Migration from v2 to v3 is simple. Just update the package. The state before the update should be maintained. If saptune is not active, the update will leave it alone, even a running tuned. If saptune is active, it will be also after the update (now via the systemd service and tuned will be disabled and stopped).
If you setup saptune via scripts or deployment system, make sure that they do not contain any tuned actions. The best way to activate saptune is the new command 'saptune service takeover' or if you have to stay compatible with saptune v2 setups 'saptune daemon start' (marked deprecated, but redirects to 'saptune service takeover') works.
Thank you Sören,
My doubt was due to man saptune-migrate is focusing to 1-to-3 "Only a migration from version 1 to version 3 is supported!. In effect we got version 3 just updating the package and too unistalling v2 and installing v3.
Thank you for clarify.
Looks that saptune have new solutions for S4H that are not mentioned in sap note 1275776 - Linux: Preparing SLES for SAP environments.
saptuneknows the following tuning solutions (groups of SAP Notes):
BOBJ. Solution for running SAP BusinessObjects.
HANA. Solution for running an SAP HANA database.
MAXDB. Solution for running an SAP MaxDB database.
NETWEAVER. Solution for running SAP NetWeaver application servers.
S4HANA-APPSERVER. Solution for running SAP S/4HANA application servers .
S4HANA-APP+DB. Solution for running both SAP S/4HANA application servers and SAP HANA on the same host .
S4HANA-DBSERVER. Solution for running the SAP HANA database of an SAP S/4HANA installation .
SAP-ASE. Solution for running an SAP Adaptive Server Enterprise database.
NETWEAVER+HANA. Solution for running both SAP application servers and SAP HANA on the same host.
So far correct, but the 1275776 - Linux: Preparing SLES for SAP environments. lists no Solution anyway. Best is always to get a list of available Solutions by running: saptune solution list
Yep, but how get this info that in saptune is something new? We are setting it automatically by Ansible. I don't know if it is somewhere on git where will be possible follow it.
Yes, it is living on github https://github.com/SUSE/saptune so I've set there notification for new releases.
I keep the SUSE documentation up-to-date, but not all aspects(especially small ones) are described there. The SAP Note is more or less a starting point, only to introduce the most basic usage and points to the SLES documentation. Maintaining both is to much effort.
Also I write blog posts here and on https://www.suse.com/c/blog/ shortly before a new version will be released as well after it has been released.
You can subscribe to the public sle-updates mailing list (lists.suse.com Mailing Lists) to get informed about updates. As soon a package (like saptune) appears in the official repo, there is a mail about it.
The package changelog (rpm -q --changelog saptune) always has a summary of the changes.
And finally there is this GitHub repo for saptune: https://github.com/SUSE/saptune
If I'm not mistaken, it gets updated shortly before a new version has been released.