Getting started¶
Example inventory¶
To manage kernel modules on a host, you need to add it to the
[debops_service_kmod]
Ansible inventory group:
[debops_service_kmod]
hostname
Example playbook¶
If you are using this role without DebOps, here's an example Ansible playbook
that uses the debops.kmod
role:
---
- name: Manage kernel modules
collections: [ 'debops.debops', 'debops.roles01',
'debops.roles02', 'debops.roles03' ]
hosts: [ 'debops_service_kmod' ]
become: True
environment: '{{ inventory__environment | d({})
| combine(inventory__group_environment | d({}))
| combine(inventory__host_environment | d({})) }}'
roles:
- role: python
tags: [ 'role::python', 'skip::python', 'role::kmod' ]
python__dependent_packages3:
- '{{ kmod__python__dependent_packages3 }}'
python__dependent_packages2:
- '{{ kmod__python__dependent_packages2 }}'
- role: kmod
tags: [ 'role::kmod', 'skip::kmod' ]
Ansible tags¶
You can use Ansible --tags
or --skip-tags
parameters to limit what
tasks are performed during Ansible run. This can be used after a host was first
configured to speed up playbook execution, when you are sure that most of the
configuration is already in the desired state.
Available role tags:
role::kmod
- Main role tag, should be used in the playbook to execute all of the role tasks as well as role dependencies.
Other resources¶
List of other useful resources related to the debops.kmod
Ansible role:
- Manual pages: modprobe.d(5), modules-load.d(5)
- Linux Kernel Modules page on Debian Wiki
- Kernel Modules page on Arch Wiki