Install a cluster
Step 1. Run installation
The last step of adding a new Enterprise Tools cluster is installing its services. To do this, you should:
Run the Offline Install action at the CLUSTERS tab.Switching to installing the cluster
In the opened window, enter the full path to the shell script that is received from the Arenadata support team, and click Run.Verifying installing
Wait until the installing process is completed.NOTEIn case of errors, you can find the logs at the JOBS tab.The installing process is completed
Step 2. Upload packages for offline installation
In addition to installing the cluster, you should process the shell script that is received from the Arenadata support team. It is necessary to enable offline installation of products in the future. To do this, you should:
Run the Upload Pack action at the CLUSTERS tab.Switching to uploading packages
In the opened window, enter the full path to the shell script received from the Arenadata support team, and click Run.Verifying uploading
Wait until the uploading process is completed.NOTEIn case of errors, you can find the logs at the JOBS tab.
Step 3. Verify results
The steps for checking the installation results are listed below:
Check that ports
81are 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
Check that the /opt/arenadata/etools/httprepo/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/arenadata-repo
The following example displays the data that can be placed in this folder for ADB installation.
total 0 drwxr-xr-x 4 root root 28 Feb 28 17:48 . drwxr-xr-x 3 root root 28 Feb 28 17:48 .. drwxr-xr-x 3 root root 32 Feb 28 17:48 ADB drwxr-xr-x 3 root root 17 Feb 28 17:48 ADM