API Doc
Search Docs...
⌘ K
OverviewDeploymentManagementOperationReferenceGlossary
    ACOS 6.3.0
  • Arcfra Cloud Operating System>
  • CLI command>
  • Managing clusters

Managing cluster services

Setting the CPU mode for network services

Procedure

To set the CPU mode for network services, execute the following command on any node in an ACOS (AVE) cluster:

zbs-cluster network_cpu_mode set --mode {share|isolate_normal}

Parameter Description
--mode {share|isolate_normal} Required. The CPU mode for network services.
  • share: Network services run on CPUs reserved for system services. This is the default mode after the cluster is deployed.
  • isolate_normal: Network services run on 2 additional CPUs reserved specifically for them. Use this mode in clusters where network services experience high load.

Output example

...
2025-12-12 10:19:53,716 cluster.py 1150 [18537] [INFO] Setting network cpu mode to isolate_normal for all cluster nodes...
...
2025-12-12 10:18:52,887 cluster.py 1158 [14225] [INFO] Successfully set network cpu mode to share for all cluster nodes

Setting service priority

Set the priority for the members of a service.

Procedure

Run the following command on any node in the cluster to set the priority of the service_name service:

zbs-tool service set_priority [--force] <service_name> <priority>

Parameter Description
--force Optional. Temporarily sets Current priority to the same value as Priority.

When viewing services running in the cluster, you can query Current priority.

Current priority is the current priority, which can be automatically adjusted based on node status within a range not higher than Priority. Using --force ensures that Current priority is the same as Priority at the current moment.

service_name Required. The name of the service whose priority is to be set. You can use zbs-tool service list to query the services and their members running in the cluster.
priority

Required. The service priority.

The format is IP:Port:priority, which can be used to set for one or more members of the same service. To set multiple members, separate them with commas (,), e.g., IP1:Port1:priority1,IP2:Port2:priority2.

  • IP:Port: The member of a service.
  • priority: The service's priority, which is an integer value between 0 and 255. The higher the value, the greater the priority.

Usage example

Set the priority of the taskd service member 10.0.100.42:10602 to 2, and set the priority of 10.0.100.53:10600 to 254.

zbs-tool service set_priority taskd 10.0.100.42:10602:2,10.0.100.53:10600:254

Output note

If the command succeeds, no output is displayed.

Registering service information

Execute this command during cluster deployment or upgrade to automatically register alarm rules and other service dependency information. If association rules are manually modified under special circumstances (in /etc/aquarium/register_conf/), this command can be executed to register the information for automatic updates.

Procedure

Run the following command on any node in the cluster:

zbs-deploy-manage register-service

Output note

The service registration process is displayed.

Setting VIP for services

Procedure

Run the following command to set the VIP of the service named service_name to ipv4_vip. Currently supported service_name includes iscsi and management:

vipservice-tool set <service_name> <ipv4_vip>

Output note

If the command succeeds, no output is displayed.

Removing VIP for services

Procedure

Run the following command to delete the VIP of the service named service_name:

vipservice-tool delete <service_name>

Output note

If the command succeeds, no output is displayed.

Switching the host of the service VIP

Procedure

Run the following command to switch the VIP of the service named service_name to another available node:

vipservice-tool drain <service_name>

Output note

If the command succeeds, no output is displayed.

Migrating service VIPs from zbs-taskd to vipservice for management

Procedure

Run the following command to migrate the VIP of management and iscsi services from zbs-taskd to vipservice for management:

vipservice-tool migrate

Output example

migrate service management from taskd to vipservice
migrate service management from taskd: done
migrate service iscsi from taskd to vipservice
migrate service iscsi from taskd: done