Component Description

This section describes the driver and firmware installation packages of common hardware devices. For details about the driver and firmware installation packages of other hardware models, contact Huawei technical support.

FeatureRetrieval is provided by the binary dynamic shared library and depends on the Ctrl CPU open SDK, OpenBLAS, and Faiss. Before using FeatureRetrieval, install these dependency libraries.
For details about how to obtain the Ctrl CPU open SDK and install the environment, see the CANN Software Installation Guide or CANN Software Installation (Open Form, Atlas 200/300/500 inference product).
If you need to deploy FeatureRetrieval in the Docker environment, deploy the Docker container by referring to Installation and Deployment > Installing Cluster Scheduling Components > Common Operations > Installing the Ascend Docker Runtime in the MindX DL Cluster Scheduling User Guide, and then install FeatureRetrieval.

**Table 1** Dependency packages
Abbreviation	Full Name	Default Installation Path
CANN development kit	Ascend-cann-toolkit_{version}_linux-{arch}.run	/usr/local/Ascend/ascend-toolkit/latest
npu-driver	Driver software packages corresponding to the Ascend 310 AI Processor Ascend310-hdk-npu-driver_{version}_linux-{arch}.run Driver software packages corresponding to the Atlas inference products Ascend310P-hdk-npu-driver_{version}_linux-{arch}.run	/usr/local/Ascend
npu-firmware	Firmware software packages corresponding to the Ascend 310 AI Processor Ascend310-hdk-npu-firmware_{version}.run Firmware software packages corresponding to the Atlas inference products Ascend310P-hdk-npu-firmware_{version}.run	/usr/local/Ascend
Ctrl CPU open SDK	Ascend-cann-device-sdk_<version>_linux-<arch>.zip	Runtime (MiniOS) and driver source packages generated after decompression
Runtime (MiniOS)	CANN-runtime-<version>-minios.aarch64.run NOTE: The Runtime (MiniOS) package name depends on the used CANN version. FeatureRetrieval is compatible with Runtime (MiniOS) packages of different versions. The same Runtime (MiniOS) package has different default installation paths in the development environment and operating environment.	/usr/local/AscendMiniOs (development environment) /usr/local/AscendMiniOSRun (operating environment)
Driver source package	Firmware software packages corresponding to the Ascend 310 AI Processor Ascend310-driver-{version}-minios.aarch64-src.tar.gz Firmware software packages corresponding to the Atlas inference products Ascend310P-driver-{version}-minios.aarch64-src.tar.gz	It is used to package the OS image file on the device during FeatureRetrieval deployment.

If you want to deploy FeatureRetrieval in the Docker container environment, pay attention to the following:
1. Because the FeatureRetrieval uses the open Ctrl CPU solution, ensure that the retrieval-related folders (such as /usr/local/Ascend/driver, /usr/local/Ascend/develop/, and /usr/local/AscendMiniOs) in the Docker container are correctly mounted. Otherwise, the retrieval compilation in the container may fail.
2. If bash install.sh is executed on the host (outside the container), ensure that the executable files and operator OM files compiled in the container can be accessed outside the container. If this step needs to be performed in the container, ensure that the container instance has the privilege permission so that FeatureRetrieval can be successfully deployed.
For third-party open-source software, if the version has vulnerabilities, fix and update them timely based on the corresponding description of the open-source version.

Parent topic: Installing Dependencies