Install a cluster

Olga Semme, Daria Barysheva

Step 1. Run installation

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

  1. Apply the Offline 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 window, enter a full path to the shell script that is received from the Arenadata support team and click Run.

    Verify installation
    Verify installation

  3. 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 ET services, it is required to upload all installation files and images to an initialized HTTP repository and Docker Registry on the host where the ET 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);

  • ET 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 ET 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. 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

  2. In the opened window, enter a full path to the shell script received from the Arenadata support team and click Run.

    Verify upload
    Verify upload

  3. Wait until the upload process is completed.

    NOTE
    In case of errors, you can find logs on the Jobs page.

Step 3. Verify results

The steps for checking the installation results are listed below:

  1. Check that ports 443 and 81 are listened at the host where cluster is installed. The first port is used by the Docker Registry service, the second one — by the HTTP Mirror service.

    $ sudo netstat -ntlp|grep L|grep -E "81|443"

    The result should look like this:

    tcp6       0      0 :::443                  :::*                    LISTEN      1694/docker-proxy-c
tcp6       0      0 :::81                   :::*                    LISTEN      1708/docker-proxy-c

  2. Check that the /opt/arenadata/etools/httprepo/packages/arenadata-repo folder exists at the host where the cluster is installed. This folder should contain the data necessary for offline installation of the products that you have chosen before getting a shell script from the Arenadata support team.

    $ ls -la /opt/arenadata/etools/httprepo/packages/arenadata-repo

    The following example displays the data that can be placed in this folder for ADS and ADS Control installation.

    total 0
drwxr-xr-x. 5 root root 45 May 23 16:01 .
drwxr-xr-x. 3 root root 28 May 23 16:00 ..
drwxr-xr-x. 3 root root 17 May 23 16:01 ADM
drwxr-xr-x. 3 root root 19 May 23 16:00 ADS
drwxr-xr-x. 3 root root 21 Nov 23 19:12 ADSCC
drwxr-xr-x. 3 root root 19 May 23 16:01 zookeeper
Found a mistake? Seleсt text and press Ctrl+Enter to report it