diff --git a/modules/cluster-node-tuning-operator-default-profiles-set.adoc b/modules/cluster-node-tuning-operator-default-profiles-set.adoc index 2bc11d2b3695..85fba8449529 100644 --- a/modules/cluster-node-tuning-operator-default-profiles-set.adoc +++ b/modules/cluster-node-tuning-operator-default-profiles-set.adoc @@ -20,7 +20,7 @@ spec: - data: | [main] summary=Optimize systems running OpenShift (provider specific parent profile) - include=-provider-${f:exec:cat:/var/lib/tuned/provider},openshift + include=-provider-${f:exec:cat:/var/lib/ocp-tuned/provider},openshift name: openshift recommend: - profile: openshift-control-plane diff --git a/modules/custom-tuning-specification.adoc b/modules/custom-tuning-specification.adoc index 4fd6c6f0edd5..d1af2d82fe7c 100644 --- a/modules/custom-tuning-specification.adoc +++ b/modules/custom-tuning-specification.adoc @@ -348,7 +348,7 @@ ifdef::rosa-hcp-tuning[] machine pools. endif::rosa-hcp-tuning[] -This functionality takes advantage of `spec.providerID` node object values in the form of `://` and writes the file `/var/lib/tuned/provider` with the value `` in NTO operand containers. The content of this file is then used by TuneD to load `provider-` profile if such profile exists. +This functionality takes advantage of `spec.providerID` node object values in the form of `://` and writes the file `/var/lib/ocp-tuned/provider` with the value `` in NTO operand containers. The content of this file is then used by TuneD to load `provider-` profile if such profile exists. The `openshift` profile that both `openshift-control-plane` and `openshift-node` profiles inherit settings from is now updated to use this functionality through the use of conditional profile loading. Neither NTO nor TuneD currently include any Cloud provider-specific profiles. However, it is possible to create a custom profile `provider-` that will be applied to all Cloud provider-specific cluster nodes.