offline_kubespray/collection/community/libvirt/README.md

community.libvirt Collection

This repo hosts the community.libvirt Ansible Collection.

The collection includes the libvirt modules and plugins supported by Ansible libvirt community to help the management of virtual machines and/or containers via the libvirt API.

This collection is shipped with the ansible package.

Tested with Ansible

• 2.9
• 2.10
• 2.11
• devel

External requirements

• python >= 2.6
• libvirt-python

Included content

Modules:

• virt
• virt_net
• virt_pool

Inventory:

• libvirt

Connection:

• libvirt_lxc
• libvirt_qemu

Using this collection

Before using the libvirt collection, you need to install it with the Ansible Galaxy command-line tool:

ansible-galaxy collection install community.libvirt

You can include it in a requirements.yml file and install it via ansible-galaxy collection install -r requirements.yml, using the format:

---
collections:
  - name: community.libvirt

You can also download the tarball from Ansible Galaxy and install the collection manually wherever you need.

Note that if you install the collection from Ansible Galaxy with the command-line tool or tarball, it will not be upgraded automatically when you upgrade the Ansible package. To upgrade the collection to the latest available version, run the following command:

ansible-galaxy collection install community.libvirt --upgrade

You can also install a specific version of the collection, for example, if you need to downgrade when something is broken in the latest version (please report an issue in this repository). Use the following syntax:

ansible-galaxy collection install community.libvirt:==X.Y.Z

See Ansible Using collections for more details.

Contributing to this collection

The content of this collection is made by people just like you, a community of individuals collaborating on making the world better through developing automation software.

We are actively accepting new contributors.

All types of contributions are very welcome.

You don't know how to start? Refer to our contribution guide!

The aspiration is to follow the following general guidelines:

• Changes should include tests and documentation where appropriate.
• Changes will be lint tested using standard python lint tests.
• No changes which do not pass CI testing will be approved/merged.
• The collection plugins must provide the same coverage of python support as the versions of Ansible supported.
• The versions of Ansible supported by the collection must be the same as those in developed, or those maintained, as shown in the Ansible Release and Maintenance documentation.

We use the following guidelines:

• CONTRIBUTING.md
• REVIEW_CHECKLIST.md
• Ansible Community Guide
• Ansible Development Guide
• Ansible Collection Development Guide

Local Testing

To learn how to test your pull request locally, refer to the Quick-start guide.

To learn how to test a pull request made by another person in your local environment, refer to the Test PR locally guide.

Collection maintenance

Maintainers of this collection follow the Maintainer guidelines.

Publishing New Version

Basic instructions without release branches:

1. Create changelogs/fragments/<version>.yml with release_summary: section (which must be a string, not a list).
2. Run antsibull-changelog release --collection-flatmap yes
3. Make sure CHANGELOG.rst and changelogs/changelog.yaml are added to git, and the deleted fragments have been removed.
4. Tag the commit with <version>. Push changes and tag to the main repository.
5. Monitor the release job on the Zuul Status Dashboard.
6. Verify that the new version is available on Ansible Galaxy.

See the Releasing guidelines to learn more.

More Information

Communication

To communicate, we use:

• The #ansible-community Libera.Chat IRC channel.
• Issues in this repository.

We announce important development changes and releases through Ansible's The Bullhorn newsletter. If you are a collection developer, be sure you are subscribed.

We take part in the global quarterly Ansible Contributor Summit virtually or in-person. Track The Bullhorn newsletter and join us.

For more information about communication, refer to the Ansible Communication guide.

Reference

• Ansible Collection overview
• Ansible User guide
• Ansible Developer guide
• Ansible Community code of conduct

License

GNU General Public License v3.0 or later.

See LICENCE to see the full text.