Configuring Batch Upgrade
Perform the following operations before batch upgrading NPU drivers and firmware, MCU firmware, CANN packages, MindCluster components (performance test, fault diagnosis, and cluster scheduling), and MindIE image, as well as configuring HCCN parameters. For details about all software packages supported by MindCluster Ascend Deployer, see Software Packages That Can Be Installed and Upgraded.
The following configuration modes are supported. This section describes how to perform a batch upgrade, which can be skipped for upgrade on a single server.
- Method 1: Editing inventory_file
- Method 2: Using an Excel file to configure deployment parameters for software installation or upgrade
Editing inventory_file
- Log in to the MindCluster Ascend Deployer executor.
- Configure the IP addresses and usernames of other target devices on the MindCluster Ascend Deployer executor.
Go to the ascend-deployer/ascend_deployer directory, edit inventory_file, comment out or delete localhost ansible_connection='local' ansible_ssh_user='root' under [worker], set related parameters based on Table 1, and run the :wq command to save the settings and exit.
Table 1 Parameter description Parameter
Required or Not
Description
IP
Yes
Server IP address.
ansible_ssh_user
Yes
Account for logging in to a remote server using SSH. The account must be root.
ansible_ssh_pass
No
Password for logging in to a remote server using SSH.
If SSH key-based authentication is configured and the root user is allowed for login, you do not need to set this parameter.
npu_num
No
Number of NPUs. You can check whether the number of identified NPUs is the same as the planned number of NPUs.
Example:
[worker] 10.125.45.171 ansible_ssh_user="root" ansible_ssh_pass="xxxxxx" # Use the actual IP address of the target device. 10.125.45.172 ansible_ssh_user="root" ansible_ssh_pass="xxxxxx" # Use the actual IP address of the target device.
- Both IPv4 and IPv6 addresses are supported. The type of IP addresses used by an SSH client such as PuTTY to connect to the execution device must be the same as that configured in inventory_file, which should be either IPv4 or IPv6.