Bug 1461838 - RFE: Add "process" rule for recommend_profile
RFE: Add "process" rule for recommend_profile
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tuned (Show other bugs)
x86_64 Linux
unspecified Severity medium
: rc
: ---
Assigned To: Jaroslav Škarvada
: FutureFeature, Patch, Upstream
Depends On:
Blocks: 1465887 TUNED-7.5-REBASE
  Show dependency treegraph
Reported: 2017-06-15 08:34 EDT by jmencak
Modified: 2017-08-09 12:05 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description jmencak 2017-06-15 08:34:11 EDT
Description of problem:
There is currently no way of "recommend"ing a profile based on processes running on the system.  I believe it would be useful if a "tuned" user could specify (in /etc/tuned/recommend.conf) something like


Multiple process=<regex> key-value pairs within a profile section would serve as a logical AND condition, i.e. the profile would only be selected if all processes were running on the system.

Version-Release number of selected component (if applicable):

Additional information:
At the moment the motivation for this is selecting a tuned profile for an Openshift router based on the presence of a haproxy process, but I'm sure there might be other use cases.
Comment 2 Jaroslav Škarvada 2017-06-15 10:24:59 EDT
I think it will be beneficial.

Unfortunately the current parser (configobj) doesn't allow multiple keywords (i.e. multiple 'process=regex' lines), but it shouldn't be problem to differentiate it by unique suffix, e.g.:

Comment 3 Jaroslav Škarvada 2017-06-15 12:24:01 EDT
Upstream patch adding this functionality:
Comment 5 jmencak 2017-06-16 03:32:05 EDT
Tested upstream patch in #3, works fine.

Note You need to log in before you can comment on or make changes to this bug.