Qubinode kvmhost Setup Collection for Ansible

This Ansible Collection for Virtual Machines Setup provides a set of roles for configuring and managing KVM hosts in baremetal servers using RHEL-based Linux operating systems. This collection can help to simplify the process of deploying and managing virtual machines by automating the setup process.

Role Variables

variable	definition
project_dir	location of code and qcow iamge
required_rpm_pakcages	list of packages that will be installed
libvirt_services	libvirt services
libvirt_host_networks	dictionary variable that creates libvirt network xml file. must set the name, mode, and bridge key
libvirt_host_pool	Content Cell
kvm_host_ipaddr	default value is ansible_default_ipv4.address
kvm_host_ip	default value is ansible_default_ipv4.address
kvm_host_interface	default value is ansible_default_ipv4.interface
kvm_host_gw	default value is ansible_default_ipv4.gateway
kvm_host_macaddr	default value is ansible_default_ipv4.mac
kvm_host_netmask	default value is ansible_default_ipv4.netmask
kvm_host_mask_prefix	default value is ansible_default_ipv4.gateway
kvm_host_bootproto	default value is dhcp
kvm_bridge_type	default value is Bridge
storage_nic	default value is false
libvirt_disk	default value is false
qubinode_bridge_name	default qubibr0 name of bridge network
qubinode_bridge_fact	name of bridge to check ansible_qubibr0.active for active status
qcow_rhel_name	name of default qcow image
admin_user	ssh username for kvm server
kvm_host_domain	default value is "lab.example"
kvm_host_dns_server	default value is "1.1.1.1"
dns_servers	default value is"{{ dns_server }}" and 8.8.8.8
kvm_host_libvirt_dir	default value is /var/lib/libvirt/images
configure_bridge	set to false to skip creating a bridge interface
configure_shell	Configure the user bash shell login prompt
cockpit_packages	default packages for cockpit
cicd_test	set to true to test in container

Collection directories and files Reference

https://docs.ansible.com/ansible/latest/dev_guide/developing_collections_structure.html#collection-directories-and-files

collection/
├── docs/
├── galaxy.yml
├── meta/
│   └── runtime.yml
├── plugins/
│   ├── modules/
│   │   └── module1.py
│   ├── inventory/
│   └── .../
├── README.md
├── roles/
│   ├── role1/
│   ├── role2/
│   └── .../
├── playbooks/
│   ├── files/
│   ├── vars/
│   ├── templates/
│   └── tasks/
└── tests/

Code of Conduct

We follow the Ansible Code of Conduct in all our interactions within this project.

If you encounter abusive behavior, please refer to the policy violations section of the Code for information on how to raise a complaint.

Communication

We announce releases and important changes through Ansible's The Bullhorn newsletter. Be sure you are subscribed.

Join us in the #ansible (general use questions and support), #ansible-community (community and collection development questions), and other IRC channels.

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.

Contributing to this collection

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

We are actively accepting new contributors.

Any kind of contribution is very welcome.

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

We use the following guidelines:

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

Collection maintenance

The current maintainers are listed in the MAINTAINERS file. If you have questions or need help, feel free to mention them in the proposals.

To learn how to maintain / become a maintainer of this collection, refer to the Maintainer guidelines.

Governance

The process of decision making in this collection is based on discussing and finding consensus among participants.

Every voice is important. If you have something on your mind, create an issue or dedicated discussion and let's discuss it!

Tested with Ansible

External requirements

Supported connections

Included content

Using this collection

Installing the Collection from Ansible Galaxy

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

ansible-galaxy collection install qubinode.qubinode_kvmhost_setup_collection

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

---
collections:
  - name: qubinode.qubinode_kvmhost_setup_collection

Note that if you install the collection from Ansible Galaxy, 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 qubinode.qubinode_kvmhost_setup_collection --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 to install version 0.1.0:

ansible-galaxy collection install qubinode.qubinode_kvmhost_setup_collection:==0.1.0

See Ansible Using collections for more details.

Release notes

See the changelog.

Roadmap

More information

• Ansible Collection overview
• Ansible User guide
• Ansible Developer guide
• Ansible Collections Checklist
• Ansible Community code of conduct
• The Bullhorn (the Ansible Contributor newsletter)
• News for Maintainers

Licensing

GNU General Public License v3.0 or later.

See LICENSE to see the full text.