-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
2 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,5 @@ | ||
| --- | ||
| title: "Announcing Trento Version 2.3.0" | ||
| title: "Announcing Trento Version 2.3.1" | ||
| date: 2024-06-18T12:15:00+02:00 | ||
| hideLastModified: true | ||
| showInMenu: false | ||
|
|
@@ -48,7 +48,7 @@ In SUSE in general, and in the Trento team in particular, we strive to make our | |
|  | ||
|
|
||
| # Saptune Configuration Checks | ||
| The previous version of Trento brought the integration of [saptune](https://github.com/SUSE/saptune) into the console, giving SAP administrators visibility on the tool even when they are not working at operating system level. Version 2.3.0 of Trento reinforces such integration by introducing saptune related configuration checks, which has been possible thanks to significant improvements in the Checks development environment. Now we can execute checks not only against clusters but also individual hosts and they can behave in a non-boolean fashion, understanding expectations which evaluations can return a range of results rather than a simple true or false. On this regard, there are two types of saptune checks: those that have a host as a target, and those that have a cluster as a target. | ||
| The previous version of Trento brought the integration of [saptune](https://github.com/SUSE/saptune) into the console, giving SAP administrators visibility on the tool even when they are not working at operating system level. Version 2.3.1 of Trento reinforces such integration by introducing saptune related configuration checks, which has been possible thanks to significant improvements in the Checks development environment. Now we can execute checks not only against clusters but also individual hosts and they can behave in a non-boolean fashion, understanding expectations which evaluations can return a range of results rather than a simple true or false. On this regard, there are two types of saptune checks: those that have a host as a target, and those that have a cluster as a target. | ||
|
|
||
|  | ||
|
|
||
|
|
||