Set sysctl system control parameters via Opscode Chef
- Debian/Ubuntu
- RHEL/CentOS
- Scientific Linux
- PLD Linux (not tested)
There are two main ways to interact with the cookbook. This is via chef attributes or via the provided LWRP.
- node['sysctl']['params'] - A namespace for setting sysctl parameters
- node['sysctl']['conf_dir'] - Specifies the sysctl.d directory to be used. Defaults to /etc/sysctl.d on the Debian and RHEL platform families, otherwise nil
- node['sysctl']['allow_sysctl_conf'] - Defaults to false. Using conf_dir is highly recommended. On some platforms that is not supported. For those platforms, set this to true and the cookbook will rewrite the /etc/sysctl.conf file directly with the params provided. Be sure to save any local edits of /etc/sysctl.conf before enabling this to avoid losing them.
Actions
- apply (default)
- remove
Attributes
- key
- value
# set vm.swapiness to 20 via attributes
node.default['sysctl']['params']['vm']['swappiness'] = 20
# set vm.swapiness to 20 via sysctl_param LWRP
sysctl_param 'vm.swappiness' do
value 20
end
# remove sysctl parameter and set net.ipv4.tcp_fin_timeout back to default
sysctl_param 'net.ipv4.tcp_fin_timeout' do
value 30
action :remove
end
This cookbook can be tested using vagrant, but it depends on the following vagrant plugins
vagrant plugin install vagrant-omnibus
vagrant plugin install vagrant-berkshelf
Tested with
- Vagrant (version 1.3.5)
- vagrant-berkshelf (1.3.4)
- vagrant-omnibus (1.1.2)
To test we have written tests in bats and executed via test-kitchen.
Much of the tooling around this cookbook is exposed via thor and test kitchen, so it is highly recommended to learn more about those tools. However, to give a quick glance at how to do some tests, you can execute the following commmands
bundle install
bundle exec rubocop
bundle exec thor foodcritic:lint
bundle exec kitchen test default-ubuntu-1204
bundle exec kitchen test default-centos-64
The above will do ruby style (rubocop) and cookbook style (foodcritic) checks followed by ensuring proper cookbook operation on two separate linux platforms (Ubuntu 12.04 LTS Precise 64-bit and CentOS 6.4). Please run the tests on any pull requests that you are about to submit and write tests for defects or new features to ensure backwards compatibility and a stable cookbook that we can all rely upon.
This coobook is also setup to run the style checks while you work via the guard gem.
There are a lot of different documents that talk about system control parameters, the hope here is to point to some of the most useful ones to provide more guidance as to what the possible kernel parameters are and what they mean.