# Tuned rules for recommend_profile. # # Syntax: # [PROFILE1] # KEYWORD11=RE11 # KEYWORD21=RE12 # # [PROFILE2] # KEYWORD21=RE21 # KEYWORD22=RE22 # KEYWORD can be: # virt - for RE to match output of virt-what # system - for RE to match content of /etc/system-release-cpe # process - for RE to match running processes. It can have arbitrary # suffix, all process* lines have to match for the PROFILE # to match (i.e. the AND operator) # /FILE - for RE to match content of the FILE, e.g.: # '/etc/passwd=.+'. If file doesn't exist, its RE will not # match. # chassis_type - for RE to match the chassis type as reported by dmidecode # syspurpose_role - for RE to match the system role as reported by syspurpose # All REs for all KEYWORDs have to match for PROFILE to match (i.e. the AND operator). # If 'virt' or 'system' is not specified, it matches for every string. # If 'virt' or 'system' is empty, i.e. 'virt=', it matches only empty string (alias for '^$'). # If several profiles matched, the first match is taken. # # Limitation: # Each profile can be specified only once, because there cannot be # multiple sections in the configuration file with the same name # (ConfigObj limitation). # If there is a need to specify the profile multiple times, unique # suffix like ',ANYSTRING' can be used. Everything after the last ',' # is stripped by the parser, e.g.: # # [balanced,1] # /FILE1=RE1 # # [balanced,2] # /FILE2=RE2 # # This will set 'balanced' profile in case there is FILE1 matching RE1 or # FILE2 matching RE2 or both. [atomic-host] virt= system=.*atomic.* [atomic-guest] virt=.+ system=.*atomic.* [throughput-performance] virt= system=.*(computenode|server).* [virtual-guest] virt=.+ [balanced]