Ansible collection: kemopq.virtual_resources

Collection for creating virtual resources (virtual machines, networks, volumes) on different virtualization platforms (currently only libvirt is supported).
For virtual machines type and number of instances are defined. VMs are created with names:
<vm_type><vm_suffix>1, <vm_type><vm_suffix>2, ... Default <vm_suffix> is "-node" Each VM can have several network interfaces and volumes attached. Image can be provided for boot volume (currently only ubuntu18.04 is supported). VM can also boot from network interface (pxe or uefi boot is possible - ovfm package should be installed on main host for uefi boot).
Currently supported OS:

• Ubuntu (tested with Ubuntu18.04)
• Debian (tested with Debian9.9)
• Centos (tested with Centos7)

Installing collection

Install this collection locally:

ansible-galaxy collection install kemopq.virtual_resources -p ./collections

./collections folder should be included to collections_path parameter in ansible configuration file (ansible.cfg). See: https://docs.ansible.com/ansible/latest/reference_appendices/config.html#ansible-configuration-settings-locations

[defaults]
collections_path = ./collection
host_key_checking = False

Additional parameter host_key_checking is added, so ssh to created VM is done without key checking.

Using collection

Roles and module can be used on your ansible playbook.

- name: Your playbook
  hosts: all
  gather_facts: no

  collections:
      - kemopq.virtual_resources

  tasks:
    - name: Include virtual_resources role
      import_role:
        name: libvirt

    - name: Get MAC list of osnode VMs for os_internal network
      kemopq.virtual_resources.getmac:
        vm_type: 'osnode'
        vm_suffix: '-node'
        network: 'os_internal'
      register: getmac_result

    - name: Print mac list
      debug:
        msg: "{{ getmac_result.mac_list }}"

Configuration parameters

Template of configuration file is in config folder. It's well commented. The configuration file has three parts:

• storage pool definition
• network definition
• virtual machines definition

Running your playbook

When running your playbook a path to configuration file should be provided. Additionaly next parameters should be specified:

virt_resources_action Possible values are:

• 'deploy': virtual resources are created
• 'destroy': virtual resources are destroyed
• 'vmstart': VMs, which didn't start immediately after creation, are started virt_resources_type Possible values are:
• 'all': actions on all virtual resources
• 'virt_vol_pool': actions on volume pool
• 'virt_network': actions on networks
• 'virt_machine': actions on virtual machines virt_machines_type List of virtual machines types, on which actions are executed. If parameter is not provided, actions will be executed on all VMs.

ansible-playbook  -i localhost, -e virt_resources_action=[deploy/destroy/vmstart] -e virt_resources_type=[all/virt_vol_pool/virt_network/virt_machines] -e "@<your_config_file>.yml" <your_playbook>.yml

Plugins

Filters:

• netint_to_list (network interfaces configuration data is transformed to list of interfaces for easier VM creation)
• volumes_to_int (volumes configuration data is transformed to list of volumes for easier VM creation)

Modules:

• getmac (returns a list of MAC addresses for a given network for all instances of vm type)
• get_os_version (returns OS version name, major and minor version of given OS image)