Selecting infrastructure for SVM deployment

At this step, you need to select the virtual infrastructure in which you want to deploy the SVM. If SVM deployment was not previously performed in this virtual infrastructure, you need to configure the connection of the SVM Management Wizard to the virtual infrastructure. Then select the hypervisors or OpenStack projects for SVM deployment depending on the type of virtual infrastructure.

To configure the connection of SVM Management Wizard to the virtual infrastructure:

Click the Add button.
In the Virtual infrastructure connection settings window that opens, specify the following settings:
- Type
  Type of virtual infrastructure object that SVM Management Wizard will connect to.
  
  Depending on the type of virtual infrastructure, select a hypervisor, virtual infrastructure administration server, or Keystone microservice.
  
  For a virtual infrastructure based on the ALT Virtualization Server platform, you need to select KVM as the type of virtual infrastructure object that the SVM Management Wizard will connect to.
  
  For a virtual infrastructure on the VK Cloud platform, select Keystone microservice (OpenStack platform) as the type of virtual infrastructure object to which you want SVM Management Wizard to connect.
- Protocol
  Protocol used to connect SVM Management Wizard to the virtual infrastructure. By default, HTTPS protocol is used.
  
  The Protocol field is displayed if you are configuring a connection to a virtual infrastructure based on the OpenStack platform, VK Cloud platform or TIONIX Cloud Platform.
- Addresses
  Addresses of the virtual infrastructure objects that SVM Management Wizard will connect to.
  
  Depending on the type of virtual infrastructure, you need to specify the hypervisor address or the address of the virtual infrastructure administration server. To connect to an OpenStack-based infrastructure, you need to specify the address of the Keystone microservice.
  
  The address can be specified as the IP address in IPv4 format or the fully qualified domain name (FQDN).
  
  You can specify multiple addresses by separating them with a semicolon, a space, or a new line. The number of correctly recognized addresses is shown under the list of addresses.
  
  In this field, you can also specify the port used to connect to the virtual infrastructure object in the format <IP address>:<port>.
  
  If you are configuring a connection to Microsoft Windows Server (Hyper-V) hypervisors that are part of a hypervisor cluster managed by the Windows Failover Clustering service, you can specify the address of the cluster. All hypervisors that are part of the cluster will be added to the list.
  
  If you are configuring a connection to VMware ESXi hypervisors managed by VMware vCenter Servers running in Linked mode, you can specify the address of any of these VMware vCenter Servers. All the hypervisors running on VMware vCenter servers in Linked mode will be added to the list.
  
  If you are configuring a connection to hypervisors that are managed by Microsoft SCVMM, you can specify the settings for connecting to Microsoft SCVMM. All hypervisors that are managed by Microsoft SCVMM will be added to the list.
  
  If you are configuring a connection to an infrastructure managed by Nutanix Prism Element, you need to specify the Nutanix Prism Element address. If the infrastructure is managed by Nutanix Prism Central, specify the Nutanix Prism Central address. All Nutanix Prism Element servers managed by Nutanix Prism Central will be added to the list.
- OpenStack domain
  Name of the OpenStack domain that contains an account used to connect SVM Management Wizard to the virtual infrastructure object.
  
  An OpenStack domain is a collection of OpenStack accounts, groups of infrastructure objects, and projects in virtual infrastructures based on OpenStack (including infrastructures based on the VK Cloud platform or TIONIX Cloud Platform). Each account belongs to a particular OpenStack domain.
  
  The OpenStack domain field is displayed if you are configuring a connection to a virtual infrastructure based on the OpenStack platform, VK Cloud platform or TIONIX Cloud Platform.
- User name
  Name of the user account that the SVM Management Wizard uses to connect to the virtual infrastructure during SVM deployment, removal and reconfiguration. This account must have privileges that are sufficient for SVM deployment, removal and reconfiguration.
  
  If you use a domain account to connect to a virtual infrastructure object, you can specify the account name in the <domain>\<user name> or <user name>@<domain> format.
- Password
  Password of the user account that the SVM Management Wizard uses to connect to the virtual infrastructure during SVM deployment, removal and reconfiguration.
If you are deploying an SVM in a virtual infrastructure running on Citrix Hypervisor, VMware vSphere, KVM, Proxmox VE, Skala-R, HUAWEI FusionSphere, Nutanix Acropolis, OpenStack, ALT Virtualization Server, Astra Linux, VK Cloud platform, or TIONIX Cloud Platform, when connecting the Integration Server to the virtual infrastructure during Kaspersky Security operation, we recommend using an account with restricted permissions for virtual infrastructure operations. Select the Account with limited rights check box and specify the settings of the user account that the Integration Server will use to connect to the virtual infrastructure during Kaspersky Security operation.
If the check box is cleared, during Kaspersky Security operation the Integration Server will connect to the virtual infrastructure using the same user account that is used for SVM deployment, removal and reconfiguration.

In a virtual infrastructure running on the Microsoft Hyper-V platform, you can connect to the virtual infrastructure during Kaspersky Security operation only by using the same user account that is used for SVM deployment, removal and reconfiguration.
Click the Connect button.
The Virtual infrastructure connection settings window closes. The Wizard adds the selected virtual infrastructure objects to the list and attempts to establish a connection.

The Wizard verifies the authenticity of all virtual infrastructure objects with which the connection is established.

Authenticity is not verified for a Microsoft Windows Server (Hyper-V) hypervisor.

For Keystone microservices, authenticity is verified only when using the HTTPS protocol to connect the SVM Management Wizard to the virtual infrastructure.

To verify authenticity, the Wizard receives the SSL certificate or fingerprint of the public key from each virtual infrastructure object and verifies them.

If the authenticity of the received certificate(s) cannot be established, the Verify certificate window opens with a message about this. Click the link in this window to view the details of the received certificate. If the certificate complies with the security policy of your organization, you can confirm the authenticity of the certificate and continue connecting to the virtual infrastructure object. The received certificate will be installed as a trusted certificate on the device where the Kaspersky Security Center Administration Console is installed. If you do not consider this certificate to be authentic, click the Cancel button in the Verify certificate window to disconnect, and replace the certificate with a new one.

If the authenticity of the open key could not be established, the Verify public key fingerprint window opens with a message about this. You can confirm the authenticity of the open key and continue the connection. The open key fingerprint will be saved on the device where the Kaspersky Security Center Administration Console is installed. If you do not consider this open key to be authentic, click the Cancel button in the Verify public key fingerprint window to terminate the connection.

If a connection cannot be established with a virtual infrastructure object, information about the connection errors is displayed in the table.

The table displays information about the virtual infrastructures whose connections are configured for SVM Management Wizard. If SVMs are already deployed in the virtual infrastructure, the table also contains information about them. Each row of the table displays a hierarchical list of virtual infrastructure objects and the following information:

Name/Address
Depending on the type of virtual infrastructure, the column may contain the following:
- IP address or the fully qualified domain name (FQDN) of the virtual infrastructure administration server
- IP address or the fully qualified domain name of the hypervisor
- IP address or the fully qualified domain name of the Keystone microservice
- Name of the OpenStack domain
- Name of the OpenStack project
- Name of the SVM deployed on the hypervisor
If SVM deployment is restricted, or if a connection with the virtual infrastructure cannot be established, the warning icon is displayed. A description of the restriction or connection error is shown in the table and in the tooltip of the warning sign.
State
This column contains information on the state of the virtual infrastructure object or the SVM.

For the hypervisor, one of the following values is specified: Enabled or Disabled. If a connection to the hypervisor cannot be established, the column shows Disconnected.

For the Keystone microservice, the OpenStack project, and the OpenStack domain, one of the following values is specified: Enabled or Disconnected.

One of the following values is specified for an SVM: Enabled, Disabled.
Protection
This column contains the Kaspersky Security version number.
Type
This column contains the type of virtual infrastructure object that the SVM Management Wizard will connect to.

For a virtual infrastructure based on the ALT Virtualization Server platform, KVM is displayed as the type of virtual infrastructure object that the SVM Management Wizard connects to.

For a virtual infrastructure on the VK Cloud platform, Keystone microservice (OpenStack Platform) is displayed as the type of virtual infrastructure object to which the SVM Management Wizard connects.

You can search the list of virtual infrastructure objects based on the Name/Address column. The search starts as you type in the Search field. The table displays only those virtual infrastructure objects that meet the search criteria. To reset the search results, delete the contents of the Search field.

You can update the list of virtual infrastructure objects using the Refresh button above the table. When updating a list, the Wizard verifies the SSL certificates or fingerprints of the public key, just like what happens when adding virtual infrastructure objects to the list.

You can use buttons in the Name/Address column to:

Remove selected virtual infrastructure from the list.
The Integration Server continues to connect to the virtual infrastructure removed from this list, and to receive the information required for SVM operation.
If you cannot connect to the virtual infrastructure, open the Virtual infrastructure connection settings window to change the settings of the account used to make the connection.
After the settings are modified, the Wizard verifies the SSL certificates or fingerprints of the public key, just like what happens when adding virtual infrastructure objects to the list.

To select infrastructure for SVM deployment:

Depending on the type of the virtual infrastructure, select check boxes in the table to the left of the names of the hypervisors on which you want to deploy an SVM, or the OpenStack projects in which you want to deploy an SVM.
You can select hypervisors or OpenStack projects that are not subject to SVM deployment restrictions.

If SVMs are being deployed in an infrastructure based on the OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform, simultaneous SVM deployment in different infrastructures is not supported. You can deploy SVMs in only one of these infrastructures at a time, or in one or more infrastructures of other types.

The simultaneous deployment of SVMs within OpenStack projects, which are running on different Keystone microservices, is not supported. You can simultaneously deploy SVMs only in OpenStack projects that are running on the same Keystone microservice.
If you want to enable concurrent SVM deployment on several hypervisors, or within several OpenStack projects, select the Allow parallel deployment on N hypervisors or Allow parallel deployment on N SVMs check box (depending on the type of the virtual infrastructure), and specify the number of hypervisors on which SVMs will be deployed concurrently, or the number of SVMs.

Proceed to the next step of the wizard.

Page top