Install a cluster

Step 1. Run installation

The last step of adding a new Arenadata Enterprise Tools cluster is to install its services. To do this:

  1. Apply the Install action to the cluster selected on the Clusters page by clicking the actions default dark actions default light icon in the Actions column.

    Switch to cluster installation
    Switch to cluster installation
  2. In the opened dialog box, on the Configuration tab:

    • Enable the Offline Install toggle.

    • In the Packfile field, enter a full path to the unpacked shell script received from the Arenadata support team. The file must be located on the ADET host in a directory where script execution is allowed by the operating system security policy.

    • Click Next.

      Configure installation parameters
      Configure installation parameters
  3. On the Raising concerns tab:

    • If necessary, enable the Raise non-blocking concern toggle to run the action without blocking the cluster during action execution.

    • Click Next.

  4. On the Confirmation tab:

    • Add a comment with a brief description of the changes.

    • Select the Verbose checkbox to display additional information about the action execution on the Jobs page.

    • Click Run.

  5. Wait until the installation process is completed.

    NOTE
    In case of errors, you can find logs on the Jobs page.
    Cluster installation is completed
    Cluster installation is completed

Step 2. Upload packages for offline installation

In addition to installing the ADET services, it is required to upload all installation files and images to an initialized HTTP repository and Docker Registry on the host where the ADET cluster is deployed. It is necessary for future offline deployment of Arenadata products.

Disk space consumption specifics

During the execution of the Upload Pack action in ADCM, disk space is actively used due to the specifics of data processing:

  1. Archive extraction: packages are extracted into the installation directory (/opt/arenadata/etools/ by default or another selected directory).

  2. Temporary files: files are created in system directories (for example, /tmp).

  3. Docker images: temporary layers are created by Docker in the data storage directory (the directory specified in the Docker Root Dir parameter — for example, /var/lib/docker).

As a result, total disk space consumption can significantly exceed the size of the original packages (two times or more). If there is not enough space at any stage (extraction, temporary file creation, or Docker image loading), an error of the following type can occur: ApplyLayer exit status 1 …​ no space left on device.

Check the amount of available disk space for the following directories:

  • Docker data storage directory (path specified in the Docker Root Dir parameter);

  • ADET installation directory (/opt/arenadata/etools/);

  • temporary directories (/tmp).

Before uploading packages, it is recommended to match their size with the available disk space. Ensure that the /opt/arenadata/etools/ directory (or any other selected directory) has sufficient free space for .tar.gz archives based on the disk space check results performed using the commands below.

In case of insufficient disk space errors, perform the following steps on the host:

  1. Determine the Docker data storage directory:

    $ sudo docker info | grep 'Docker Root Dir'

    The result should look like this:

    Docker Root Dir: /var/lib/docker
  2. Check available disk space:

    $ sudo df -h /var/lib/docker
    $ sudo df -h /opt/arenadata/etools
    $ sudo df -h /tmp
    NOTE
    If the command output for the specified directories shows the same mount point (the Mounted on column), it means that the directories are located in the same filesystem and use a common disk space. In this case, refer to the value in the Avail column for that filesystem rather than for each directory separately.
  3. Check actual disk space usage:

    $ sudo du -sh /var/lib/docker
    $ sudo du -sh /opt/arenadata/etools
    $ sudo docker image ls
  4. If necessary, remove unused Docker objects:

    IMPORTANT
    • The command removes unused Docker images, containers, networks, and temporary data used by various services and applications on the server, not only ADET components.

    • Before running the command, ensure that the resources being removed are not used by other services or applications.

    $ sudo docker system prune -a

To upload the packages, perform the following steps:

  1. Copy the pack file received from the Arenadata support team to the host where the ADET cluster is deployed.

    The pack file is a self-extracting shell script that contains product packages and images required for offline installation. It is usually distributed as a compressed archive with a name similar to adqm_v26.3.3.20_arenadata1_ee_centos_7_x86_64.sh.xz.

    Before running the Upload Pack action, unpack the archive on the ADET host, for example:

    $ xz -d adqm_v26.3.3.20_arenadata1_ee_centos_7_x86_64.sh.xz

    After unpacking, the Packfile field should point to the resulting .sh file, not to the original .xz archive.

    You can place the pack file in any directory on the ADET host, for example, /tmp. However, the selected directory must allow script execution according to the operating system security policy. In some distributions, for example, ALT Linux, execution of scripts from /tmp can be prohibited. In this case, create and use another directory where script execution is allowed.

  2. Apply the Upload Pack action to the cluster selected on the Clusters page by clicking the actions default dark actions default light icon in the Actions column.

    Switch to uploading packages
    Switch to uploading packages
  3. In the opened dialog box, on the Configuration tab:

    • In the Packfile field, enter the full path to the unpacked pack file on the ADET host. The path must point to the .sh file located in a directory where script execution is allowed, for example: /tmp/adqm_v26.3.3.20_arenadata1_ee_centos_7_x86_64.sh.

    • Click Next.

      Configure package upload parameters
      Configure package upload parameters
  4. On the Raising concerns tab:

    • If necessary, enable the Raise non-blocking concern toggle to run the action without blocking the cluster during action execution.

    • Click Next.

  5. On the Confirmation tab:

    • Add a comment with a brief description of the changes.

    • Select the Verbose checkbox to display additional information about the action execution on the Jobs page.

    • Click Run.

  6. Wait until the upload process is completed.

    NOTE
    In case of errors, you can find logs on the Jobs page.
Found a mistake? Seleсt text and press Ctrl+Enter to report it