Installation Preparations on Huawei

Downloading the Huawei CSI Software Package

Mon, 01 Jan 0001 00:00:00 +0000

This section describes how to download the software package and the component structure of the software package.

Open a browser and enter https://github.com/Huawei/eSDK_K8S_Plugin/releases in the address box.
Download the software package of the 4.11.0 version based on the CPU architecture.
- Software package naming rule: Plug-in name (eSDK_Storage_CSI) + Version number + CPU architecture
- CSI supports the following CPU architectures: x86, Arm, and PPC64LE.
Decompress the downloaded software package. The following table shows the component structure of the software package.

Uploading a Huawei CSI Image

Mon, 01 Jan 0001 00:00:00 +0000

Huawei provides the huawei-csi image for users. For details about how to obtain the image file, see Downloading the Huawei CSI Software Package .

To use the CSI image on the container management platform, you need to import the CSI image to the cluster in advance:

Method 1: (Recommended) Use Docker to upload the CSI image to the image repository. For details, see Uploading an Image to the Image Repository .
Method 2: Manually import the CSI image to all nodes where Huawei CSI needs to be deployed. For details, see Uploading an Image to a Local Node .

Uploading an Image to the Image Repository

The installation of Huawei CSI depends on the following image files provided by Huawei. Import and upload the image files in sequence. For details about how to obtain the image files, see Downloading the Huawei CSI Software Package .

Checking User Configurations on Huawei Storage

Mon, 01 Jan 0001 00:00:00 +0000

After Huawei storage is connected to the container platform, Huawei CSI needs to manage storage resources on Huawei storage based on service requirements, such as creating and mapping volumes. In this case, Huawei CSI needs to use the users created on Huawei storage to communicate with Huawei storage. The following table lists the user information required for different storage devices.

Table 1 User requirements for connecting storage to CSI

Checking Volume Snapshot-Dependent Components

Mon, 01 Jan 0001 00:00:00 +0000

This section describes how to check the volume snapshot-dependent components in the cluster.

If Huawei CSI is deployed in a version earlier than Kubernetes v1.20, perform the following steps:

Run the following command to check the Kubernetes version. The following uses Kubernetes v1.16.0 as an example.
```
kubectl get node
```
The following is an example of the command output.
```
NAME STATUS ROLES AGE VERSION
test-master Ready master 311d v1.16.0
test-node Ready <none> 311d v1.16.0
```
Copy the helm directory in the Kubernetes CSI component package to any directory on the master node. For details about the Helm tool path, see Table 1 .

Checking the Host Multipathing Configuration

Mon, 01 Jan 0001 00:00:00 +0000

If you plan to use the FC/iSCSI/NVMe over RoCE/NVMe over FC protocol to access Huawei storage in a container environment, you are advised to use host multipathing software to enhance the link redundancy and performance of the host and storage. If you do not want to use the software, skip this section.

For details about the OSs and multipathing software that can be interconnected with Huawei CSI software, see the OS compatibility in Compatibility and Features .

Checking the Status of Host-Dependent Software

Mon, 01 Jan 0001 00:00:00 +0000

This section describes how to check whether the status of host-dependent software on worker nodes in a cluster is normal. In this example, the host OS is CentOS 7.9 x86_64.

Check the status of the iSCSI client.
```
systemctl status iscsi iscsid 
```
Check the status of the NFS client.
```
systemctl status rpcbind 
```

Check the status of DM-Multipath.

systemctl status multipathd.socket multipathd

Check the status of UltraPath.
```
systemctl status nxup
```
Check the status of UltraPath-NVMe.

Checking the Images on Which CSI Depends

Mon, 01 Jan 0001 00:00:00 +0000

The installation of Huawei CSI depends on the images listed in the following table. If all worker nodes in the cluster have been connected to the Internet and can pull images online, you can skip this section. If nodes in the cluster cannot connect to the Internet, download the corresponding image file based on the Kubernetes version and upload it to the image repository or import it to all worker nodes in the Kubernetes cluster.