1.8 KiB
puppet-sysctl
Overview
Manage sysctl variable values. All changes are immediately applied, as well as configured to become persistent. Tested on Red Hat Enterprise Linux 6.
sysctl: Definition to manage sysctl variables by setting a value.sysctl::base: Base class (included from the definition).
For persistence to work, your Operating System needs to support looking for
sysctl configuration inside /etc/sysctl.d/.
You may optionally enable purging of the /etc/sysctl.d/ directory, so that
all files which are not (or no longer) managed by this module will be removed.
Beware that for the purge to work, you need to either have at least one
sysctl definition call left for the node, or include sysctl::base manually.
You may also force a value to ensure => absent, which will always work.
For the few original settings in the main /etc/sysct.conf file, the value is
also replaced so that running sysctl -p doesn't revert any change made by
puppet.
Examples
Enable IP forwarding globally :
sysctl { 'net.ipv4.ip_forward': value => '1' }
Set a value for maximum number of connections per UNIX socket :
sysctl { 'net.core.somaxconn': value => '65536' }
Make sure we don't have any explicit value set for swappiness, typically because it was set at some point but no longer needs to be. The original value for existing nodes won't be reset until the next reboot :
sysctl { 'vm.swappiness': ensure => absent }
If the order in which the files get applied is important, you can set it by
using a file name prefix, which could also be set globally from site.pp :
Sysctl { prefix => '60' }
To enable purging of settings, you can use hiera to set the sysctl::base
$purge parameter :
---
# sysctl
sysctl::base::purge: true