Bug 1672213

Summary:	tuned profile sap-hana-vmware retirement
Product:	Red Hat Enterprise Linux 7	Reporter:	Rolf Rueck <rrueck>
Component:	tuned	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED ERRATA	QA Contact:	Robin Hack <rhack>
Severity:	low	Docs Contact:	Marie Hornickova <mdolezel>
Priority:	unspecified
Version:	7.7-Alt	CC:	bfinger, jeder, jskarvad, olysonek, rhack, tgummels, thozza
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	tuned-2.11.0-6.el7	Doc Type:	Deprecated Functionality
Doc Text:	.The `sap-hana-vmware` Tuned profile has been deprecated The `sap-hana-vmware` Tuned profile has been deprecated. For backward compatibility, this profile is still provided in the `tuned-profiles-sap-hana` package, but the profile will be removed in future major release of Red Hat Enterprise Linux. The recommended replacement is the `sap-hana`Tuned profile.	Story Points:	---
Clone Of:
Clones:	1715541 (view as bug list)		Environment:
Last Closed:	2020-03-31 19:12:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1709724, 1715541, 1716960, 1754591

Description Rolf Rueck 2019-02-04 09:49:42 UTC

Description of problem:

The tuned profile sap-hana-vmware does only provide two additional parameters to the sap-hana profile which it is based on.

Disables LRO is only recommended on special situations and needs to be set by hand to the correct network interface, before it takes effect.

vm.swappiness is outdated and no longer in sync with best practices from a VMware side.

As such the profile does not provide any benefit for customers.

Actual results:

sap-hana-vmware profile provided


Expected results:

sap-hana profile used instead

Additional info:

A additional bugzilla will be raised for change in insights rules.

Comment 2 Jaroslav Škarvada 2019-02-07 10:26:54 UTC

(In reply to Rolf Rueck from comment #0)
Are there best practices we could use for it?  If not, I still would keep this profile for RHEL-7 not to cause regression - low benefit or no benefit (this is arguable regarding the LRO tuning) is not argument to remove something from the stable release. We could drop it for next RHEL releases.

Comment 3 Rolf Rueck 2019-02-07 11:27:02 UTC

(In reply to Jaroslav Škarvada from comment #2)
> (In reply to Rolf Rueck from comment #0)
> Are there best practices we could use for it?  If not, I still would keep
> this profile for RHEL-7 not to cause regression - low benefit or no benefit
> (this is arguable regarding the LRO tuning) is not argument to remove
> something from the stable release. We could drop it for next RHEL releases.

Non that I am aware of. The SAP HANA relevant parameters are already part of the sap-hana profile, which is part of the sap-hana-vmware.

This profile is advised from Insights as the profile to be used with SAP HANA on VMWare. This violates the recommendations of SAP and VMWare regarding what parameters should be used on a system.
Customer are complaining (rightfull) about this.

If we only remove the offending parameter vm.swappiness, the profile is useless, as the LRO tuning requires the administrator to active configure a file with the network interface. It is not recommended to deploy this on all interfaces.

If removing it is not possible, I would like to have it marked deprecated, so that customers are not advised to use it any more.

Comment 4 Jaroslav Škarvada 2019-02-07 15:55:07 UTC

(In reply to Rolf Rueck from comment #3)
> (In reply to Jaroslav Škarvada from comment #2)
> > (In reply to Rolf Rueck from comment #0)
> > Are there best practices we could use for it?  If not, I still would keep
> > this profile for RHEL-7 not to cause regression - low benefit or no benefit
> > (this is arguable regarding the LRO tuning) is not argument to remove
> > something from the stable release. We could drop it for next RHEL releases.
> 
> Non that I am aware of. The SAP HANA relevant parameters are already part of
> the sap-hana profile, which is part of the sap-hana-vmware.
> 
> This profile is advised from Insights as the profile to be used with SAP
> HANA on VMWare. This violates the recommendations of SAP and VMWare
> regarding what parameters should be used on a system.
> Customer are complaining (rightfull) about this.
> 
> If we only remove the offending parameter vm.swappiness, the profile is
> useless, as the LRO tuning requires the administrator to active configure a
> file with the network interface. It is not recommended to deploy this on all
> interfaces.
> 
> If removing it is not possible, I would like to have it marked deprecated,
> so that customers are not advised to use it any more.

OK, no problem with deprecation for RHEL-7 and we can drop the profile upstream.

Comment 5 Travis Gummels 2019-05-22 17:35:18 UTC

Jaroslav,

Are you planning to deprecate sap-hana-vmware via this bug or another?  This bug has no acks so it is not on the radar for getting completed in 7.7.

Travis

Comment 6 Jaroslav Škarvada 2019-05-23 08:41:04 UTC

(In reply to Travis Gummels from comment #5)
> Jaroslav,
> 
> Are you planning to deprecate sap-hana-vmware via this bug or another?  This
> bug has no acks so it is not on the radar for getting completed in 7.7.
> 
> Travis

For RHEL-7 we are going to mark it as deprecated (we will used this BZ for it) and drop in RHEL-8 as discussed earlier in this bugzilla.

Comment 18 errata-xmlrpc 2020-03-31 19:12:11 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1008