Forge Home


Manage tuned


225 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.1.1 (latest)
  • 0.1.0
released May 30th 2023
This version is compatible with:
  • Puppet Enterprise 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x
  • Puppet >= 6.21.0 < 8.0.0
  • , , , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'jcpunk-tuned', '0.1.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add jcpunk-tuned
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install jcpunk-tuned --version 0.1.1

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



jcpunk/tuned — version 0.1.1 May 30th 2023


Manage the tuned daemon

Table of Contents

  1. Description
  2. Setup - The basics of getting started with tuned
  3. Usage - Configuration options and additional functionality
  4. Limitations - OS compatibility, etc.
  5. Development - Guide for contributing to the module


Install/uninstall the tuned daemon, configure the settings, and set the profile. You can run this in one-shot or daemon mode by setting the required options.


Beginning with tuned

Most users can probably get by with

include tuned

By default the tuned recommended profile is activated unless you select another one. This means two puppet runs are required in the default case: one to install tuned and one to populate the fact.

If you set active_profile to a specific value, rather than the fact fallthrough, just one run is required.


The parameters you're most likly to need are:

  • main_conf_ini_settings
  • enable_profile_now
  • active_profile

Odds are something like this should point you in the right direction:

class { 'tuned':
  enable_profile_now => false,
  active_profile => 'hpc-compute',
  services_ensure => 'stopped',
  main_conf_ini_settings => {
    'use tuned oneshot mode' => {
      'setting' => 'daemon',
      'value' => 0,


class { 'tuned':
  active_profile => 'desktop',
  main_conf_ini_settings => {
    'disable dynamic tuning' => {
      'setting' => 'dynamic_tuning',
      'value' => 0,


When run with the defaults, two runs are required to get the facts populated and utilized.