DCImanager 6 software is installed on:

  • platform server — physical or virtual based on KVM, Hyper-V or VMware ESXi virtualization;
  • location server — physical or virtual, based on KVM virtualization. Read more in the article Locations. General information.

To distribute the load evenly, it is recommended to use separate servers for platform and location.

To use the web interface of the platform, you will need an Internet browser. For the platform web interface to display correctly, the width of the image in the browser should be at least 1280px. For more information about supported browsers, see the article Workstation setup.

Hardware requirements


Minimal system requirements:


Platform serverLocation server
CPU2.4 GHz2.4 GHz
Cores
RAM8 Gb8 Gb

Disk space

(root partition of the disk)

110 Gb100 Gb

Intel and AMD processors with x86_64 architecture are supported. Processors with ARM architecture are not supported.

Correct platform operation is not guaranteed if the processor does not support SSE4.2 instruction set.

If you use one server for platform and location, you will need at least 210 GB of root partition to run DCImanager 6. The amount of disk space consumed depends on the amount of equipment added to DCImanager 6.

System requirements


Supported operating system:

  • AlmaLinux 8;
  • Ubuntu 20.04.

CentOS 7 operating system:

  • not supported for new product installations;
  • for existing product installations is supported until EOL on June 30, 2024.

For DCImanager 6 to work correctly, install the platform on the latest stable version of the operating system. Install the platform on an unmodified installation of the operating system without third-party repositories and additional services. Do not install the software manually.

The server must have Docker software version at least 20.10.10 installed. Update the Docker version if necessary.

When creating partitions on the hard drive, allocate the maximum size for the root partition.

Network settings


Allow incoming connections to the ports:

  • 22/TCP — for SSH;
  • 80/TCP — for http;
  • 443/TCP — for https.

Do not disable the firewalld service. Disabling the service may cause Docker to fail.

Allow access to the resources:

Access to resources should be available permanently. Lack of access can lead to platform malfunctions. For example, if the license server is not available, the platform license may be deactivated.