Help Center/ ModelArts/ API Reference/ Resource Pool Management/ Obtaining Custom Node Configurations of a Resource Pool

Updated on 2025-11-27 GMT+08:00

CLI Examples

View PDF

Obtaining Custom Node Configurations of a Resource Pool

This API is used to obtain custom node configurations of a resource pool.

You can debug this API through automatic authentication in API Explorer or use the SDK sample code generated by API Explorer. Obtain its CLI example hcloud ModelArts ShowPoolNodeConfig.

Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.

If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.
If you are using identity policy-based authorization, no identity policy-based permission required for calling this API.

GET /v2/{project_id}/pools/{pool_name}/node-config

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Definition: User project ID. For details, see Obtaining a Project ID and Name. Constraints: N/A Range: N/A Default Value: N/A
pool_name	Yes	String	Constraints: N/A

None

Status code: 200

**Table 2** Response body parameters
Parameter	Type	Description
apiVersion	String	Definition: The value is fixed at v2. Range: N/A
kind	String	The value is fixed at NodeConfig.
metadata	NodeconfigMeta object	Definition: Metadata of a resource pool node.
spec	NodeconfigSpec object	Definition: Specifications of a resource pool node.
status	NodeconfigStatus object	Definition: Status of a resource pool node.

**Table 3** NodeconfigMeta
Parameter	Type	Description
name	String	The value is fixed at node-config.

**Table 4** NodeconfigSpec
Parameter	Type	Description
configs	Object	Custom node configurations, including binding cores to nodes, enabling cache clearing, and enabling transparent huge pages currently. "configs": { "cpu_manager": { "mode": "static/none" //static indicates to enable core binding, and none indicates to disable core binding. }, "drop_cache": { "mode": "enable/disable" //enable indicates to enable cache clearing. }, "transparent_hugepage": { "mode": "always/madvise/never" //always indicates to enable transparent huge pages, never indicates to disable transparent huge pages, and madvice indicates that the system determines whether to enable this function. } }

**Table 5** NodeconfigStatus
Parameter	Type	Description
phase	String	Plugin instance status. Options: Pending: The plugin is being installed. Running: All of the plugin instances are running. This specifies that the plugin runs properly. Updating: The plugin is being updated. Abnormal: The plugin instances are abnormal and the plugin cannot be used. You can click the status to view the failure cause. Deleting: The plugin is being deleted.