Directory Description
You can specify the directory for storing the HAF installation package. In this document, by default, the /opt/haf-software directory is used as the root directory for storing the HAF installation package, and the /opt/ directory is used as the root directory for installing the HAF software.
- The HAF installation package contains three software packages: haf-host, haf-target, and haf-tool, after the host node is installed, all related files are stored in the /opt/haf-host directory. After the offload node is installed, all related files are stored in the /opt/haf-target and /opt/haf-scripts directories. The haf-tool software package is used to run maintenance commands.
- You can specify the directory for storing the OmniData installation package. In this document, /opt/haf-software is used as the root directory for storing the OmniData installation package by default. The program installation directory is nested in the HAF installation directory, and /opt/haf-target/run/haf_user/omnidata is used as the root directory for installing the software. After the OmniData program package is decompressed, the omnidata and omnidata-setup directories are generated. All related files are stored in /opt/haf-target/run/haf_user/omnidata and /opt/haf-software/omnidata-setup.
The following table describes the installation packages and their directories.
The /opt/haf-software directory you created is used only for running the installation package and related installation, upgrade, and uninstallation scripts. The scripts must be executed by the root user. /opt/haf-host, /opt/haf-target, and /opt/haf-scripts are used for service running.
Installation Node |
Directory Category |
Directory Name |
Description |
|---|---|---|---|
All nodes (management, compute, and storage nodes) |
Directory for storing software packages |
/opt/haf-software |
Stores BoostKit-haf_1.0.zip. The haf-1.0.tar.gz package extracted from BoostKit-haf_1.0.zip contains the software package, tool script package, and installation configuration file required for HAF installation, which are: haf-host-1.0.tar.gz, haf-target-1.0.tar.gz, and haf-tool-1.0.tar.gz Stores the software package BoostKit-omnidata_1.1.0.zip required for OmniData installation. NOTE:
Scripts for deployment and installation are contained in haf-tool-1.0.tar.gz. Decompress haf-tool-1.0.tar.gz before installation. The decompressed files are described as follows: bin: binary files for inner signature verification. haf-scripts: scripts related to cgroup control. tools: haf-tool and related scripts. install-config: path for storing the configuration file during installation. haf_installer: installation program. haf_uninstaller: uninstallation program. haf_upgrade: upgrade program. |
Offload node (storage node) |
Directory for storing software packages |
/opt/haf-software/omnidata-setup |
Stores OmniData installation, upgrade, and uninstallation scripts and inner signature verification file, which are: omnidata-install.sh, omnidata-upgrade.sh, omnidata-destroy.sh, and verification |
Host node (management and compute nodes) |
Installation directory of HAF on the host node |
/opt/haf-host/bin |
Stores the binary file of the software on the host node: kmc_tool_bin |
/opt/haf-host/lib |
Stores dynamic libraries and JAR packages of the host node: libcrypto.so, libhaf_common.so, libhaf_link_host.so, libhaf_offload_device_internal.so, libhaf_offload_host.so, libkmc.so, libkmc_tool.so, liblog.so, libsdp.so, libsecurec.so, libssl.so, and jar/haf-jni-call-1.0.jar |
||
/opt/haf-host/tools |
Stores the management tool and script on the host node: haf-tool and scripts |
||
/opt/haf-host/env.sh |
Stores the script for setting environment variables on the host node. |
||
/opt/haf-host/haf_user.conf |
Stores the default offload user configuration file on the host node. |
||
/opt/haf-host/haf_host_install.conf |
Stores the default configuration file used during installation on the host node. |
||
Offload node (storage node) |
Installation directory of HAF on the offload node |
/opt/haf-target/bin |
Stores the binary file of the software on the offload node: haf_daemon, haf_executor, and kmc_tool_bin |
/opt/haf-target/lib |
Stores dynamic libraries and JAR packages of the offload node: libcrypto.so, libhaf_common.so, libhaf_link_host.so, libhaf_offload_device_internal.so, libhaf_offload_host.so, libhostJNI_device.so, libkmc.so, libkmc_tool.so, liblog.so, libsdp.so, libsecurec.so, libssl.so, libcpuchecker.so, and jar/haf-jni-call-1.0.jar |
||
/opt/haf-target/etc |
Stores the crontab job configurations generated during the installation: crontab.job |
||
/opt/haf-target/run |
Stores working directories, configuration files, and certificates required for HAF startup. |
||
/opt/haf-target/tools |
Stores the management tool and script on the offload node: haf-tool and scripts |
||
/opt/haf-target/haf.conf |
Stores the configuration file for running the offload node. |
||
/opt/haf-target/haf_target_install.conf |
Stores the configuration file for installing the offload node. |
||
Installation directory of OmniData on the offload node |
/opt/haf-target/run/haf_user/omnidata/deploy |
Stores installation and deployment scripts: generate-config.sh and get_ip.sh, log.sh |
|
/opt/haf-target/run/haf_user/omnidata/etc |
Stores the configuration files required for starting OmniData. |
||
/opt/haf-target/run/haf_user/omnidata/lib |
Stores the list of third-party open source software packages on which OmniData depends. This directory contains only boostkit-omnidata-server-1.1.0-aarch64.jar. Obtain other contents (boostkit-omnidata-server-1.1.0-aarch64-lib.zip) of the lib folder from the Kunpeng community. https://github.com/kunpengcompute/omnidata-openlookeng-connector/releases/tag/v1.1.0 |
||
/opt/haf-target/run/haf_user/omnidata/plugin |
Stores UDF plugins. Currently, the boostkit-omnidata-udf-1.1.0-aarch64 directory is included. This directory contains only boostkit-omnidata-udf-1.1.0-aarch64.jar. Obtain the third-party package (boostkit-omnidata-udf-1.1.0-aarch64.zip) that the JAR package depends on from the Kunpeng community. https://github.com/kunpengcompute/omnidata-openlookeng-connector/releases/tag/v1.1.0 |
Planning Installation Nodes
- During the deployment, you need to plan a root CA server for issuing authentication certificates to HAF host and offload nodes. If there is only one node, perform all operations on the node.
- When issuing certificates by using the root CA server, ensure that the time on each node is synchronized. Otherwise, the certificate verification fails due to the system time difference. You can configure NTP for synchronization.
Node |
OmniData |
Installing HAF |
Whether to Generate a Certificate |
Function |
|---|---|---|---|---|
server |
- |
Yes |
Yes |
Controller node/Root CA server (you need to plan your own root CA server) for issuing certificates |
agent1 |
- |
Yes |
Yes |
Host node for HAF offload |
agent2 |
- |
Yes |
Yes |
Host node for HAF offload |
agent3 |
- |
Yes |
Yes |
Host node for HAF offload |
ceph1/hdfs1 |
Yes |
Yes |
Yes |
Offload node that provides the HAF OmniData service |
ceph2/hdfs2 |
Yes |
Yes |
Yes |
Offload node that provides the HAF OmniData service |
ceph3/hdfs3 |
Yes |
Yes |
Yes |
Offload node that provides the HAF OmniData service |