diff --git a/README.md b/README.md index 03ae549..4862153 100644 --- a/README.md +++ b/README.md @@ -7,55 +7,86 @@ 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][1] API. +via the [libvirt](https://libvirt.org/) API. -[1]: https://libvirt.org/ +This collection is shipped with the `ansible` package. ## Tested with Ansible -TBD + +- 2.9 +- 2.10 +- 2.11 +- devel ## External requirements -TBD - -### Supported connections - -TBD +- python >= 2.6 +- [libvirt-python](https://pypi.org/project/libvirt-python/) ## Included content -TBD + +Modules: + +- [virt](https://docs.ansible.com/ansible/latest/collections/community/libvirt/virt_module.html) +- [virt_net](https://docs.ansible.com/ansible/latest/collections/community/libvirt/virt_net_module.html) +- [virt_pool](https://docs.ansible.com/ansible/latest/collections/community/libvirt/virt_pool_module.html) + +Inventory: + +- [libvirt](https://docs.ansible.com/ansible/latest/collections/community/libvirt/libvirt_inventory.html#ansible-collections-community-libvirt-libvirt-inventory) + +Connection: + +- [libvirt_lxc](https://docs.ansible.com/ansible/latest/collections/community/libvirt/libvirt_lxc_connection.html#ansible-collections-community-libvirt-libvirt-lxc-connection) +- [libvirt_qemu](https://docs.ansible.com/ansible/latest/collections/community/libvirt/libvirt_qemu_connection.html#ansible-collections-community-libvirt-libvirt-qemu-connection) ## Using this collection -Before using the libvirt community collection, you need to install the -collection with the `ansible-galaxy` CLI: +Before using the libvirt collection, you need to install it with the Ansible Galaxy command-line tool: ```bash ansible-galaxy collection install community.libvirt ``` -Alternatively, you can also include it in a `requirements.yml` file and -install it via `ansible-galaxy collection install -r requirements.yml` using -the format: +You can include it in a `requirements.yml` file and install it via `ansible-galaxy collection install -r requirements.yml`, using the format: ```yaml +--- collections: -- name: community.libvirt + - name: community.libvirt ``` -For more information regarding using collections with Ansible, see the Ansible -[user guide][3]. +You can also download the tarball from [Ansible Galaxy](https://galaxy.ansible.com/community/libvirt) 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: + +```bash +ansible-galaxy collection install community.libvirt --upgrade +``` -[3]: https://docs.ansible.com/ansible/latest/user_guide/collections_using.html +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: + +```bash +ansible-galaxy collection install community.libvirt:==X.Y.Z +``` + +See [Ansible Using collections](https://docs.ansible.com/ansible/latest/user_guide/collections_using.html) for more details. ## Contributing to this collection -While this community is still developing its guidelines, the aspiration is to -follow the following general guidelines: +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](https://github.com/ansible-collections/community.libvirt/blob/main/CONTRIBUTING.md)! + +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. @@ -63,27 +94,25 @@ follow the following general guidelines: - 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][4] documentation. - -[4]: https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html + those in developed, or those maintained, as shown in the Ansible [Release and Maintenance](https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html) documentation. -As a fallback, the [Ansible Community Guide][5] remains our community -reference set of guidelines. +We use the following guidelines: -[5]: https://docs.ansible.com/ansible/latest/community/index.html +* [CONTRIBUTING.md](https://github.com/ansible-collections/community.libvirt/blob/main/CONTRIBUTING.md) +* [REVIEW_CHECKLIST.md](https://github.com/ansible-collections/community.libvirt/blob/main/REVIEW_CHECKLIST.md) +* [Ansible Community Guide](https://docs.ansible.com/ansible/latest/community/index.html) +* [Ansible Development Guide](https://docs.ansible.com/ansible/devel/dev_guide/index.html) +* [Ansible Collection Development Guide](https://docs.ansible.com/ansible/devel/dev_guide/developing_collections.html#contributing-to-collections) ### Local Testing -If you want to develop new content for this collection or improve what is -already here, the easiest way to work on the collection is to clone it into -one of the configured [COLLECTIONS_PATHS][2] and work on it there. +To learn how to test your pull request locally, refer to the [Quick-start guide](https://github.com/ansible/community-docs/blob/main/create_pr_quick_start_guide.rst#id3). -[2]: https://docs.ansible.com/ansible/latest/reference_appendices/config.html#collections-paths +To learn how to test a pull request made by another person in your local environment, refer to the [Test PR locally guide](https://github.com/ansible/community-docs/blob/main/test_pr_locally_guide.rst). -### Testing with `ansible-test` +### Collection maintenance -TBD +Maintainers of this collection follow the [Maintainer guidelines](MAINTAINING.md). ### Publishing New Version @@ -96,17 +125,23 @@ Basic instructions without release branches: 5. Monitor the release job on the [Zuul Status Dashboard](https://dashboard.zuul.ansible.com/t/ansible/status). 6. Verify that the new version is available on [Ansible Galaxy](https://galaxy.ansible.com/community/libvirt). +See the [Releasing guidelines](https://github.com/ansible/community-docs/blob/main/releasing_collections_without_release_branches.rst) to learn more. + ## More Information ### Communication -This is a small collection with a small number of contributors. As such, there -is no formal Ansible Working Group. To communicate with the maintainers, please -make contact via one of the following methods: +To communicate, we use: + +- The `#ansible-community` [Libera.Chat](https://libera.chat/) IRC channel. +- [Issues](https://github.com/ansible-collections/libvirt/issues) in this repository. + +We announce important development changes and releases through Ansible's [The Bullhorn newsletter](https://docs.ansible.com/ansible/devel/community/communication.html#the-bullhorn). If you are a collection developer, be sure you are subscribed. + +We take part in the global quarterly [Ansible Contributor Summit](https://github.com/ansible/community/wiki/Contributor-Summit) virtually or in-person. Track [The Bullhorn newsletter](https://docs.ansible.com/ansible/devel/community/communication.html#the-bullhorn) and join us. -- IRC on [irc.libera.chat](https://libera.chat/) in the `#ansible-community` channel -- [Issues](https://github.com/ansible-collections/libvirt/issues) on Github +For more information about communication, refer to the [Ansible Communication guide](https://docs.ansible.com/ansible/devel/community/communication.html). ### Reference