kernel_module resource¶
Use the kernel_module resource to manage kernel modules on Linux systems. This resource can load, unload, blacklist, install, and uninstall modules.
New in Chef Client 14.3.
Syntax¶
The kernel_module resource has the following syntax:
kernel_module 'name' do
load_dir String # default value: /etc/modules-load.d
modname String # default value: 'name' unless specified
unload_dir String # default value: /etc/modprobe.d
action Symbol # defaults to :install if not specified
end
where:
kernel_moduleis the resource.nameis the name given to the resource block.actionidentifies which steps the chef-client will take to bring the node into the desired state.load_dir,modname, andunload_dirare the properties available to this resource.
Actions¶
The kernel_module resource has the following actions:
:blacklist- Blacklist a kernel module.
:install- Default. Load kernel module, and ensure it loads on reboot.
:load- Load a kernel module.
:uninstall- Unload a kernel module and remove module config, so it doesn’t load on reboot.
:unload- Unload kernel module.
:nothing- Define this resource block to do nothing until notified by another resource to take action. When this resource is notified, this resource block is either run immediately or it is queued up to be run at the end of the Chef Client run.
Properties¶
The kernel_module resource has the following properties:
load_dirRuby Type: String | Default Value:
/etc/modules-load.dThe directory to load modules from.
modnameRuby Type: String | Default Value:
'name'The name of the kernel module.
notifiesRuby Type: Symbol, ‘Chef::Resource[String]’
A resource may notify another resource to take action when its state changes. Specify a
'resource[name]', the:actionthat resource should take, and then the:timerfor that action. A resource may notify more than one resource; use anotifiesstatement for each resource to be notified.A timer specifies the point during the Chef Client run at which a notification is run. The following timers are available:
:before- Specifies that the action on a notified resource should be run before processing the resource block in which the notification is located.
:delayed- Default. Specifies that a notification should be queued up, and then executed at the end of the Chef Client run.
:immediate,:immediately- Specifies that a notification should be run immediately, per resource notified.
The syntax for
notifiesis:notifies :action, 'resource[name]', :timer
subscribesRuby Type: Symbol, ‘Chef::Resource[String]’
A resource may listen to another resource, and then take action if the state of the resource being listened to changes. Specify a
'resource[name]', the:actionto be taken, and then the:timerfor that action.Note that
subscribesdoes not apply the specified action to the resource that it listens to - for example:file '/etc/nginx/ssl/example.crt' do mode '0600' owner 'root' end service 'nginx' do subscribes :reload, 'file[/etc/nginx/ssl/example.crt]', :immediately end
In this case the
subscribesproperty reloads thenginxservice whenever its certificate file, located under/etc/nginx/ssl/example.crt, is updated.subscribesdoes not make any changes to the certificate file itself, it merely listens for a change to the file, and executes the:reloadaction for its resource (in this examplenginx) when a change is detected.A timer specifies the point during the Chef Client run at which a notification is run. The following timers are available:
:before- Specifies that the action on a notified resource should be run before processing the resource block in which the notification is located.
:delayed- Default. Specifies that a notification should be queued up, and then executed at the end of the Chef Client run.
:immediate,:immediately- Specifies that a notification should be run immediately, per resource notified.
The syntax for
subscribesis:subscribes :action, 'resource[name]', :timer
unload_dirRuby Type: String | Default Value:
/etc/modprobe.dThe modprobe.d directory.