Software Package Description

Downloading Software Packages

The software is classified into the community edition and commercial edition, which contain the open source components and non-open source components of the cluster scheduling components, respectively. The community edition can be downloaded directly without applying for related permissions, but it cannot be used for commercial purpose. To download the commercial edition, you need to apply for related permissions.

Obtain the required software packages and digital signature files listed in Table 1.

**Table 1** Software package of each component (community edition)
Component	File List	Description	How to Obtain
Ascend-mindxdl-device-plugin_{version}_linux-{arch}.zip	device-plugin	Ascend Device Plugin binary file	Click this link to visit the Software Download tab page, select MindX 3.0.0, and download the component packages listed in this table.
	cert-importer	Binary file of the certificate import tool
	lib	Dynamic library file on which the encryption component depends
	Dockerfile	Image building text file for the Ascend Device Plugin
	Dockerfile-310P-1usoc	Image building text file for the Ascend Device Plugin on the Atlas 200I Soc A1 core board
	run_for_310P_1usoc.sh	Script for starting components in the Ascend Device Plugin image on the Atlas 200I Soc A1 core board
	device-plugin-310-{version}.yaml	Configuration file used when the Volcano is not used on the Ascend 310 devices
	device-plugin-310P-{version}.yaml	Configuration file used when the Volcano is not used on the Ascend 310P devices
	device-plugin-910-{version}.yaml	Configuration file used when the Volcano is not used on the Ascend 910 devices
	device-plugin-volcano-{version}.yaml	Configuration file used when the Volcano is used on the Ascend 910 devices
	device-plugin-310-volcano-{version}.yaml	Configuration file used when the Volcano is used on the Ascend 310 devices
	device-plugin-310P-volcano-{version}.yaml	Configuration file used when the Volcano is used on the Ascend 310P devices
	device-plugin-310P-1usoc-{version}.yaml	Configuration file used when the Volcano is not used on the Atlas 200I Soc A1 core boards
	device-plugin-310P-1usoc-volcano-{version}.yaml	Configuration file used when the Volcano is used on the Atlas 200I Soc A1 core boards
Ascend-mindxdl-hccl-controller_{version}_linux-{arch}.zip	hccl-controller	HCCL-Controller binary file
	cert-importer	Binary file of the certificate import tool
	Dockerfile	HCCL-Controller image building text file
	hccl-controller-{version}.yaml	HCCL-Controller startup configuration file (The KubeConfig file is not required.)
	hccl-controller-without-token-{version}.yaml	HCCL-Controller startup configuration file (The KubeConfig file is required.)
	lib	Dynamic library file on which the encryption component depends
Ascend-mindxdl-npu-exporter_{version}_linux-{arch}.zip	npu-exporter	NPU-Exporter binary file
	cert-importer	Binary file of the certificate import tool
	Dockerfile	Image building text file for the NPU-Exporter
	Dockerfile-310P-1usoc	Image building text file for the NPU-Exporter on the Atlas 200I Soc A1 core board
	run_for_310P_1usoc.sh	Script for starting components in the NPU-Exporter image on the Atlas 200I Soc A1 core board
	npu-exporter-{version}.yaml	NPU-Exporter startup configuration file
	npu-exporter-310P-1usoc-{version}.yaml	Startup configuration file of the NPU-Exporter on the Atlas 200I Soc A1 core board
	lib	Dynamic library file on which the encryption component depends
Ascend-mindxdl-volcano_{version}_linux-{arch}.zip	volcano-npu_{version}_linux-{arch}.so	Dynamic link library (DLL) for Volcano (Huawei-developed NPU scheduling plugin)
	Dockerfile-scheduler	Image building text file for the Volcano scheduler
	Dockerfile-controller	Image building text file for the Volcano controller
	volcano-{version}.yaml	Volcano startup configuration file
	vc-scheduler	Volcano scheduler binary file
	vc-controller-manager	Volcano controller binary file
Ascend-docker-runtime_{version}_linux-{arch}.run	ascend-docker-cli	Executable program required for running the Ascend Docker Runtime. You are not advised to run it directly.
	ascend-docker-destroy
	ascend-docker-hook
	ascend-docker-plugin-install-helper
	ascend-docker-runtime
	assets	Image resource of a document
	base.list*	Default mount list. During installation, the program installs different mount lists based on install-type.
	run_main.sh	Installation script. You are not advised to use it directly.
	uninstall.sh	Uninstallation script
	README.md	Ascend Docker Runtime description document, including design principles

**Table 2** Software package of each component (commercial version)
Component	File List	Description	How to Obtain
Ascend-mindxdl-noded_{version}_linux-{arch}.zip	noded	NodeD binary file	Click this link to visit the Software Download tab page, select MindX 3.0.0, and download the component packages listed in this table.
	cert-importer	Binary file of the certificate import tool
	noded-{version}.yaml	NodeD startup configuration file (The KubeConfig file is not required.)
	noded-without-token-{version}.yaml	NodeD startup configuration file (The KubeConfig file is required.)
	Dockerfile	NodeD image building text file
	lib	Dynamic library file on which the encryption component depends
Ascend-mindxdl-elastic-ms_{version}.zip	mindx_elastic-0.0.1-py37-none-linux_{arch}.whl	Binary file for resumable training, supporting dying gasp. Python 3.7 is required.
Ascend-mindxdl-elastic-ms_{version}.zip	mindx_elastic-0.0.1-py39-none-linux_{arch}.whl	Binary file for resumable training, supporting dying gasp. Python 3.9 is required.
Ascend-mindxdl-resilience-controller_{version}.zip	resilience-controller	Resilience-Controller binary file
	cert-importer	Binary file of the certificate import tool
	Dockerfile	Image building text file for the Resilience-Controller
	resilience-controller-{version}.yaml	Resilience-Controller startup configuration file (The KubeConfig file is not required.)
	resilience-controller-without-token-{version}.yaml	Resilience-Controller startup configuration file (The KubeConfig file is required.)
	lib	Dynamic library file on which the encryption component depends

{version} indicates the software version, and {arch} indicates the CPU architecture.

Verifying Digital Signatures of Software Packages

To prevent a software package from being maliciously tampered with during transmission or storage, download the corresponding digital signature file for integrity verification when downloading the software package.

After the software package is downloaded, verify its PGP digital signature according to the OpenPGP Signature Verification Guide. If the software package fails the verification, do not use the software package, and contact Huawei technical support.

Before a software package is used in installation or upgrade, its digital signature also needs to be verified according to OpenPGP Signature Verification Guide to ensure that the software package is not tampered with.

For enterprise users, visit https://support.huawei.com/enterprise/en/tool/pgp-verify-TL1000000054.

Parent topic: References