Installation by Using the CLI
Use the CLI to install the HA software on a single server.
Preparing the Environment
Before installing the HA software, ensure that the dependencies listed in Table 6-1 to be installed have been installed in the installation environment. Otherwise, the HA software may fail to be installed.
- Before installing the dependencies, ensure that the installation environment is connected to the network and that sources are available.
- Before installing the dependencies, check whether they have been installed based on the Description column in the following table. If the dependencies have been installed, you do not need to install them again. Otherwise, install them based on the Installation Command or Procedure column in the following table.
Dependency |
Description |
Installation Command or Procedure |
---|---|---|
sudo |
Run the sudo command to check whether sudo has been installed. If the sudo command exists, sudo has been installed. |
|
Docker |
Run the docker command to check whether the Docker has been installed. If the docker command exists, Docker has been installed. |
NOTICE:
After installing Docker, you can add --userns-remap=default and --default-ulimit nofile=20480:40960 --default-ulimit nproc=1024:2048 after ExecStart=/usr/bin/dockerd in the /usr/lib/systemd/system/docker.service to enable the user namespace and file handle, and set the maximum number of fork processes for the container. You can add security configurations for other Docker daemons as required. |
arping |
Run the arping command to check whether arping has been installed. If the arping command exists, arping has been installed. |
|
inotifywait |
Run the inotifywait command to check whether inotifywait has been installed. If the inotifywait command exists, inotifywait has been installed. |
NOTICE:
|
gzip |
Run the gzip command to check whether gzip has been installed. If the gzip command exists, gzip has been installed. |
|
OpenSSL |
Run the openssl command to check whether OpenSSL has been installed. If the openssl command exists, OpenSSL has been installed. |
|
systemctl systemd-run |
Run the systemctl command to check whether systemctl has been installed. If the systemctl command exists, systemctl has been installed. Run the systemd-run command to check whether systemd-run has been installed. If the systemd-run command exists, systemd-run has been installed. |
|
getconf |
Run the getconf command to check whether getconf has been installed. If the getconf command exists, getconf has been installed. |
|
Expect |
Run the expect command to check whether Expect has been installed. If the expect command exists, Expect has been installed. |
|
iptables |
Run the iptables command to check whether iptables has been installed. If the iptables command exists, iptables has been installed. |
|
Ethtool |
Run the ethtool command to check whether Ethtool has been installed. If the ethtool command exists, Ethtool has been installed. |
|
sed |
Run the sed command to check whether sed has been installed. If the sed command exists, sed has been installed. |
|
find |
Run the find command to check whether find has been installed. If the find command exists, find has been installed. |
|
grep |
Run the grep command to check whether grep has been installed. If the grep command exists, grep has been installed. |
|
awk |
Run the awk command to check whether awk has been installed. If the awk command exists, awk has been installed. |
|
mount |
Run the mount command to check whether mount has been installed. If the mount command exists, mount has been installed. |
|
tar |
Run the tar command to check whether tar has been installed. If the tar command exists, tar has been installed. |
|
Python |
Run the python3 command to check whether Python has been installed. If version information is displayed, Python has been installed. Check whether the Python version is 3.6.0 or later. If Python is not installed or the version is not 3.6.0 or later, install or upgrade Python. |
NOTE:
Before installing Python using the source code package, you need to compile and install zlib first. |
unzip |
Run the unzip command to check whether tar has been installed. If the unzip command exists, tar has been installed. |
|
ifconfig |
Run the ifconfig command to check whether tar has been installed. If the ifconfig command exists, tar has been installed. |
|
flask requests |
Flask and requests are dependency libraries required by the external RESTful interface of AtlasEdge. |
|
For open-source third-party software installed, such as Python and Flask, visit the CVE official website to check for known vulnerabilities, and fix the vulnerabilities.
Obtaining Software Packages
Software Packages |
Description |
How to Obtain |
---|---|---|
Ascend-mindxedge-ha_{version}_linux-{arch}.zip |
HA software package is used for active/standby two-node cluster protection to ensure service application reliability. |
{version} indicates the package version and {arch} indicates the CPU architecture. You need to obtain the software package as required.
Installing Software
- Log in to the installation environment as the installation user of the software package.
- Run the su command and enter the password of the root user to switch to the root user.
- Upload the HA software package obtained in Obtaining Software Packages to a directory on the server.
- (Optional) Run the following command to create the installation path of the HA software:
mkdir -p /home/work
In the command, /home/work is the installation path. This path is only an example and can vary with the actual configurations. If you do not specify the installation path, the software is installed in the current path by default.
- Run the following command in the directory where the software package is stored to decompress the software package:
unzip Ascend-mindxedge-ha_{version}_linux-{arch}.zip
In the command, Ascend-mindxedge-ha_{version}_linux-{arch}.zip indicates the software version.
The decompressed files include the following:- Installation package: Ascend-mindxedge-ha_{version}_linux-{arch}.tar.gz
- CMS file: Ascend-mindxedge-ha_{version}_linux-{arch}.tar.gz.cms
- Certificate revocation list: Ascend-mindxedge-ha_{version}_linux-{arch}.tar.gz.crl
The CMS file and CRL are used to verify software packages. The software package verification is performed only during the upgrade, and is not performed during the installation. If the verification fails, the system displays a message indicating that the upgrade fails.
- Run the following command to decompress the software package decompressed in 5:
tar -mxvf Ascend-mindxedge-ha_{version}_linux-{arch}.tar.gz
- Run the following command to install the software package:
- If you have specified the installation path, run the ./install.sh -p /home/work command.
- If you have not specified the installation path, run the ./install.sh command.
After the installation is successful, the HA software is deployed in the installation path/ha directory, for example, /home/work/ha.