Kaspersky Security for Virtualization 6.0 Light Agent

Registering existing tenants and their virtual machines

January 25, 2024

ID 259236

If the tenant protection infrastructure is configured without the use of the Integration Server REST API, you need to add information about the tenants and their virtual machines to the Integration Server database in order to generate tenant protection reports.

Registration of an existing tenant and its virtual machines in the Integration Server database consists of the following steps:

  1. Creating a tenant in the Integration Server database.

    The tenant creation procedure is automated using the Integration Server REST API.

    The actions performed in response to the REST API request depend on the tenant type specified when calling the REST API method. To enter the tenant data into the Integration Server database without creating a tenant protection infrastructure, specify the simple tenant type.

    Specify the following information in the REST API request:

    • Tenant name.
    • Tenant type: simple.

    As a result, the tenant data is saved in the Integration Server database and the tenant is assigned an identifier.

  2. Registering tenant virtual machines in the Integration Server database.

    The virtual machine registration procedure is automated by means of the Integration Server REST API.

    In the request to the REST API, specify the identifier (BIOS ID) of each virtual machine and the tenant ID of the tenant to which these virtual machines belong.

    As a result, the data on the tenant virtual machines is saved in the Integration Server database.

  3. Activating a tenant.

    The tenant activation procedure is automated using the Integration Server REST API.

    After activation, the tenant status is saved in the Integration Server database. You can get information about the tenant status using the Integration Server REST API or by viewing the list of tenants in the Integration Server Console.

    For a simple tenant, its status ("Active" or "Inactive") does not affect the protection state of tenant virtual machines.

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.