Kaspersky Unified Monitoring and Analysis Platform

Preparing the single.inventory.yml inventory file

April 8, 2024

ID 222158

KUMA components can be installed, updated, and removed in the directory containing the unpacked installer by using the Ansible tool and the user-created YML inventory file containing a list of the hosts of KUMA components and other settings. If you want to install all KUMA components on the same server, you must specify the same host for all components in the inventory file.

To create an inventory file for installation on a single server:

  1. Copy the archive with the kuma-ansible-installer-<version name>.tar.gz installer to the server and unpack it using the following command (about 2 GB of disk space is required):

    sudo tar -xpf kuma-ansible-installer-<version name>.tar.gz

  2. Go to the KUMA installer folder by executing the following command:

    cd kuma-ansible-installer

  3. Copy the single.inventory.yml.template template and create an inventory file named single.inventory.yml:

    cp single.inventory.yml.template single.inventory.yml

  4. Edit the settings in the single.inventory.yml inventory file.

    If you want predefined services to be created during the installation, set deploy_example_services to true.

    deploy_example_services: true

    The predefined services will appear only as a result of the initial installation of KUMA. If you are upgrading the system using the same inventory file, the predefined services are not re-created.

  5. Replace all kuma.example.com strings in the inventory file with the name of the host on which you want to install KUMA components.

The inventory file is created. Now you can use it to install KUMA on a single server.

We recommend backing up the inventory file that you used to install the program. You can use it to add components to the system or remove KUMA.

Sample inventory file for installation on a single server

Did you find this article helpful?
What can we do better?
Thank you for your feedback! You're helping us improve.
Thank you for your feedback! You're helping us improve.