Getting started¶
This role is part of the DebOps libvirtd configuration¶
The debops.libvirtd_qemu
role manages the libvirtd QEMU-related
configuration. It can be used as standalone, however the role is intentionally
very limited and relies on the debops.libvirtd to do most of the
work related to package installation and environment setup. You are strongly
advised to use the roles and their playbooks together.
Example inventory¶
The role is used by the debops.libvirtd playbook and will be enabled
automatically on hosts that are included in the [debops_service_libvirtd]
Ansible inventory group.
This role can be enabled on virtualization hosts separately. You can do this by
adding a host to the [debops_service_libvirtd_qemu]
group:
[debops_service_libvirtd_qemu]
hostname
Example playbook¶
If you are using this role without DebOps, here's an example Ansible playbook
that uses the debops.libvirtd_qemu
role:
---
- name: Install and manage libvirtd QEMU configuration
collections: [ 'debops.debops', 'debops.roles01',
'debops.roles02', 'debops.roles03' ]
hosts: [ 'debops_service_libvirtd_qemu' ]
become: True
environment: '{{ inventory__environment | d({})
| combine(inventory__group_environment | d({}))
| combine(inventory__host_environment | d({})) }}'
roles:
- role: ferm
tags: [ 'role::ferm', 'skip::ferm' ]
ferm__dependent_rules:
- '{{ libvirtd_qemu__ferm__dependent_rules }}'
- role: libvirtd_qemu
tags: [ 'role::libvirtd_qemu', 'skip::libvirtd_qemu' ]
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::libvirtd_qemu
- Main role tag, should be used in the playbook to execute all of the role tasks as well as role dependencies.