Configuring other_build_image
When installing and upgrading MindCluster cluster scheduling components in batches using MindCluster Ascend Deployer, you can install and upgrade the components in batches on heterogeneous nodes (worker nodes whose architecture is different from that of the executor). Select a heterogeneous node as the build server of the heterogeneous image and configure other_build_image (heterogeneous server information) in inventory_file on the build server.
Heterogeneity Scenario Description
The following table lists the heterogeneous scenario supported by MindCluster Ascend Deployer.
Executor Architecture |
Architecture of the Master Node |
Architecture of the Worker Node |
|---|---|---|
x86 |
x86 |
Arm |
Configuring other_build_image
Parameter |
Required or Not |
Description |
|---|---|---|
IP |
Yes |
IP address of the server where the heterogeneous node is located. |
ansible_ssh_user |
Yes |
Account for logging in to a remote server using SSH on the heterogeneous node. The account must be root. |
ansible_ssh_pass |
No |
Password for logging in to a remote server using SSH on the heterogeneous node. If SSH key-based authentication is configured and the root user is allowed for login, you do not need to set this parameter. |
set_hostname |
No. This parameter is required when there are multiple master nodes or worker nodes. It is optional when there is only one node. |
Name of each heterogeneous node in a Kubernetes cluster. You are advised to use the master-1 or worker-1 format to fill in the names in sequence. If a Kubernetes cluster already exists, the names must be those of the heterogeneous nodes in the existing Kubernetes cluster. The names must be configured in lowercase, and cannot be filled in arbitrarily. |