Table of Contents

1. Description
2. Setup - The basics of getting started with tuned
   • What tuned affects
   • Beginning with tuned
3. Usage - Configuration options and additional functionality
4. Reference - An under-the-hood peek at what the module is doing and how
5. Limitations - OS compatibility, etc.
6. Development - Guide for contributing to the module
   • Acceptance Tests - Beaker env variables

Description

This Puppet module manages some facets of tuned and ktune.

This is a SIMP module

This module is a component of the System Integrity Management Platform, a compliance-management framework built on Puppet.

If you find any issues, they may be submitted to our bug tracker.

This module is optimally designed for use within a larger SIMP ecosystem, but it can be used independently:

• When included within the SIMP ecosystem, security compliance settings will be managed from the Puppet server.

Setup

What tuned affects

This module manages the following resouces:

• /etc/tuned.conf
• /etc/sysconfig/ktune
• /etc/sysctl.ktune
• tuned package
• tuned service

Beginning with tuned

Just include the tuned class on the systems you want to manage.

Usage

Include the class from hiera:

---
classes:
  - tuned

File contents can be tweaked by adding more hieradata:

---
tuned::disktuning_alpm: false
tuned::io_scheduler: cfq

Reference

Please refer to REFERENCE.md

Limitations

SIMP Puppet modules are generally intended for use on Red Hat Enterprise Linux and compatible distributions, such as CentOS. Please see the metadata.json file for the most up-to-date list of supported operating systems, Puppet versions, and module dependencies.

Development

Please read our [Contribution Guide] (https://simp.readthedocs.io/en/stable/contributors_guide/index.html).