API OVERVIEW

Querying Notebook Instances

This API is used to obtain information about notebook instances that meet specific conditions.

Creating a Notebook Instance

This API is used to create a notebook instance based on specified parameters.

Querying All Notebook Instances

This API is used to obtain information about all created notebook instances.

Querying Details of a Notebook Instance

This API is used to obtain the details of a specified notebook instance.

Updating a Notebook Instance

This API is used to modify the instance configurations, including its name, description, specifications, and image.

Deleting a Notebook Instance

This API is used to delete a created notebook instance and its related resources.

Saving a Running Instance as a Container Image

This API is used to save a running instance as a container image.

Querying the List of Valid Specifications Supported by Notebook Instances

This API is used to obtain the available specifications supported by notebook instances. This API applies to the following scenario: When you want to know the configuration options supported by a notebook instance, you can use this API to query the list of available specifications. Before using this API, ensure that you have logged in to the system and have the permission to access the target notebook instance. After this API is called, the system returns the valid specifications supported by the notebook instance. For example, the memory and CPU. If you do not have the permission to access the specified notebook instance or the notebook instance is not running, the API will return an error message.

Querying the List of Switchable Specifications Supported by Notebook Instances

This API is used to obtain the available specifications that can be switched during notebook instance creation.

Querying the Available Duration of a Running Notebook Instance

This API is used to obtain the available duration of a running notebook instance.

Prolonging a Notebook Instance

This API is used to prolong the running time of a running notebook instance. This API applies to the following scenarios: When you need to prolong the running time of a notebook instance to complete long-time tasks, you can call this API to do so. Before using this API, ensure that you have logged in to the system and have the permission to perform operations on the target notebook instance. In addition, the notebook instance must be running. After this API is called, the system prolongs the running time of the specified notebook instance, so that you can continue to use it. If you do not have the permission to perform operations on the specified notebook instance or the notebook instance is not running, the API will return an error message.

Starting a Notebook Instance

This API is used to start a created notebook instance.

Stopping a Notebook Instance

This API is used to stop a notebook instance that is running.

Obtaining Details About All Notebook Resource Pool Instances

This API is used to obtain details about all notebook resource pool instances associated with a user. This API is used when you need to select a resource pool when creating a notebook instance. Before using this API, ensure that you have registered and logged in to the system and have the permission to view resource pool instances. After the API is called, the API returns a list of detailed information about all resource pool instances, including the instance name, status, and node specifications. If you have not logged in to the system, do not have the required permission to access the resource pool, or an internal error occurs in the system, the API returns an error message, for example, unauthorized access, service unavailable, or internal error.

Obtaining Details About a Notebook Resource Pool

This API is used to obtain details about a notebook resource pool. This API is used when you need to query details about a specified cluster when creating a notebook instance job. Before using this API, ensure that the cluster has been managed and you have the required permission. After this API is called, the system returns the instance ID, name, flavor, instance status, and URL for accessing the cluster. If the cluster does not exist, is not managed, or you do not have the access permission, the API will return an error message.

Querying the Switch and Quota of a Specified Feature of the Current User

This API is used to query the switch status and quota information of a specified feature of the current user. This API is used when you need to know whether a specific feature is enabled, check the quota limit, or monitor the used resources. Before using this API, ensure that you have logged in and have the query permission, and the specified feature must exist. After this API is called, the system returns the details, such as whether the feature is enabled, total quota, and used resources. If you do not have the required permission, the feature does not exist, or the system is abnormal, the API will return an error message.

Querying Supported Images

This API is used to query all images by page based on specified conditions.

Registering a Custom Image

This API is used to register a custom image with ModelArts image management.

Querying the User Image List

This API is used to obtain the overview of user image information. Image names are used for aggregation.

Obtaining Details of an Image

This API is used to query image details.

Deleting an Image

This API is used to delete an image object. For a private image, you can also delete its SWR image content using parameters.

Synchronizing the Image Status

This API is used to correct the abnormal image status. This API is used when you need to synchronize the latest image status when the image status is abnormal due to misoperations, network problems, or system faults. Before using this API, ensure that the image exists and you have the required permission. After the synchronization, the image status is updated to the latest correct status, and related resources and configurations are synchronized. If the image does not exist, you do not have the operation permission, or an error occurs during the synchronization, the API will return an error message.

Deleting Image Groups

This API is used to delete all version objects from an image group. For a private image, you can also delete its SWR image content using parameters. This API applies to the following scenarios: When an image is no longer required, the configuration is incorrect, or resources need to be cleared, you can use this API to delete all versions within the specified image group. Before using this API, ensure that the image group exists and you have the permission to delete it. After the deletion is complete, all version objects within the image group are permanently removed, and related resources and configurations are cleared. If the image group does not exist, you do not have the operation permission, or the image is being used, the API will return an error message.

Updating an Image Group

This API is used to update the tags and description of an image group. This API is used when the image description or tag needs to be modified. Before using this API, ensure that the image group exists and you have the permission to update it. After the update is complete, the configuration file corresponding to the image group is updated. If the image group does not exist, you do not have the operation permission, or the image is being used, the API will return an error message.

Creating an Algorithm

This API is used to create an algorithm on ModelArts.

Querying the Algorithm List

This API is used to obtain the list of all algorithms on ModelArts.

Querying Algorithm Details

This API is used to obtain the details of a specified algorithm on ModelArts.

Modifying an Algorithm

This API is used to modify the information of an existing algorithm.

Deleting an Algorithm

This API is used to remove a registered algorithm from ModelArts.

Obtaining Supported Hyperparameter Search Algorithms

This API is used to query all hyperparameter search algorithms supported by the system.

Updating Training Experiment Information

This API is used to modify the configuration of an existing training experiment on ModelArts.

Obtaining Training Experiment Details

This API is used to query the details about a training experiment.

Deleting a Training Experiment

This API is used to delete a created training experiment.

Creating a Training Experiment

This API is used to create an experiment category on ModelArts.

Obtaining the Training Experiment List

This API is used to obtain the list of created training experiments created on ModelArts.

Verifying the Training Experiment Name

This API is used to check whether the training experiment name is duplicate before training experiment creation.

Creating and Publishing an Algorithm

This API is used to create and publish algorithms in algorithm management.

Creating a Training Job

This API is used to create a training job on ModelArts.

Querying the Details About a Training Job

This API is used to query the details about a training job on ModelArts.

Modifying the Description of a Training Job

This API is used to modify the description of an existing training job.

Deleting a Training Job

This API is used to delete a training job from ModelArts.

Terminating a Training Job

This API is used to terminate a training job on ModelArts. Only jobs in the creating, awaiting, or running state can be terminated.

Querying the Logs of a Specified Task in a Given Training Job (Preview)

This API is used to query the logs of a specified task in a given training job on ModelArts (preview).

Querying the Logs of a Specified Task in a Training Job (OBS Link)

This API is used to obtain the OBS link where the log files of a specified training job are stored.

Querying the Running Metrics of a Specified Task in a Training Job

This API is used to query the running metrics of a specified task in a training job on ModelArts.

Querying a Training Job List

This API is used to obtain the list of all training jobs on ModelArts.

Querying All Trials Using Hyperparameter Search

This API is used to obtain the detailed results of all trials in a specified hyperparameter search job.

Querying Information About a Trial Using Hyperparameter Search

This API is used to obtain the detailed results of a specific trial in a specified hyperparameter search job.

Obtaining the Hyperparameter Sensitivity Analysis Result

This API is used to query the hyperparameter sensitivity analysis result of a specified hyperparameter search job.

Obtaining the Path for Storing a Hyperparameter Sensitivity Analysis Image

This API is used to obtain the path of the hyperparameter sensitivity analysis result image.

Early Stopping a Trial of an Auto Search Job

This API is used to manually stop a trial of an ongoing automated search job.

Obtaining Information About the YAML Template of an Auto Search Job

This API is used to obtain the YAML configuration template details of an auto search job.

Obtaining the Content of the YAML Template of an Auto Search Job

This API is used to obtain the YAML configuration file details of an auto search job.

Creating a Training Job Tag

This API is used to add tags to an existing training job.

Deleting Tags of a Training Job

This API is used to remove a tag from an existing training job.

Obtaining Tags of a Training Job

This API is used to obtain the tag information of an existing training job.

Obtaining the Events of a Training Job

This API is used to obtain the events of a training job on ModelArts.

Obtain Training Quotas

This API is used to obtain the training resource quota of a user in ModelArts.

Obtaining the Stage Information List of a Training Job

This API is used to obtain the process stage information list of a training job on ModelArts.

Obtaining the Event Type List

This API is used to obtain the event type list supported by training management.

Obtaining the Historical Scheduling Information of a Training Job Instance

This API is used to query the instance IP address and node IP address of a training job. You can use the schedule_count parameter to query the instance information of a specific scheduling.

Training Job Event Reporting APIs

This API is used to report the training event to the service plane.

This API is used to obtain the public flavors supported by a training job.

This API is used to obtain the supported resource specifications of training jobs on ModelArts.

Obtaining the Preset AI Frameworks Supported by a Training Job

This API is used to query the list of preset AI frameworks supported by the current system.

Querying OS Configuration Parameters

This API is used to obtain the configuration parameters of ModelArts OS, such as network CIIDR and user resource quota. This API is used when you need to query the network configuration, resource allocation, or system management of ModelArts OS. Before using this API, ensure that you have the permission to access ModelArts OS and the service is running properly. After the query, the configuration parameters are returned for future resource planning and system optimization. If you do not have the required permission, the service is unavailable, or the request parameter is invalid, the API will return an error message.

Querying a Plug-in Template

This API is used to obtain details about a specified plug-in template. This API is used when you need to query the configuration, functions, or usage of a specific plug-in template. Before using this API, ensure that the plug-in template exists and you have the required permission. After the query, the details of the specified plug-in template are returned, including the configuration parameters and function description of the template, helping you develop and manage plug-ins. If the plug-in template does not exist or you do not have the access permission, the API will return an error message.

Obtaining Nodes in a Resource Pool

This API is used to obtain the node list of a specified resource pool. This API is used when you need to obtain the details about a resource pool, such as the node distribution, status, or resource usage. Before using this API, ensure that the resource pool has been created and is available, and you have the required permission. After the query, the system returns the detailed information about the nodes in the resource pool, including the node ID, status, and resource usage, helping you manage and optimize resources. If the resource pool does not exist, you do not have the permission to access the resource pool, or the request parameters are invalid, the API will return an error message.

Deleting nodes in batches

This API is used to delete nodes from a specified resource pool in batches. This API is used when you need to delete redundant nodes, re-allocate resources, or remove faulty nodes from a resource pool. Before using this API, ensure that the resource pool has been created and is available, you have the required permission, and at least one node is retained in the resource pool. After the deletion, the specified nodes are permanently removed, and the remaining nodes in the resource pool continue to work. If the resource pool does not exist, the node does not exist, you do not have the permission to perform the operation, or the number of nodes in the resource pool is insufficient, the API will return an error message.

Querying a Trace List

This API is used to obtain the event information recorded in the system. This API is used when you need to query the event records recorded in the system when monitoring the system status, locating faults, or auditing. Before using this API, ensure that you have the required permission and the event records exist in the system. After the query, the API returns the event list, including the event ID, type, time, and description. If you do not have the required permission, the event record does not exist, or the query parameter is incorrect, the API will return an error message.

Creating Network Resources

This API is used to create network resources in a system. This API is used when you need to create network resources, such as virtual networks, subnets, or routes, when you need to expand services, plan resources, or adjust the network architecture. Before using this API, ensure that you have the administrator permission and the system has sufficient resources to create network resources. After the creation, the network resources will be added to the system for future service configurations. If you do not have the required permission, the resources are insufficient, or the input parameter is incorrect, the API will return an error message.

Obtaining Network Resources

This API is used to obtain information about created network resources in the system. This API is used when you need to query the network resource list recorded in the system when monitoring network status, planning resources, locating network faults, or auditing. Before using this API, ensure that you have the required permission and the network resources exist in the system. After the query, the API returns the network resource list, including the resource ID, type, status, and creation time. If you do not have the required permission, the network resources do not exist in the system, or the query parameter is incorrect, the API will return an error message.

Obtaining a Network Resource

This API is used to obtain the details of a specified network resource. This API is used when you need to query details about a specified network resource, such as its configuration, status, or attributes. Before using this API, ensure that you have the required permission and the specified network resource exists in the system. After the query, the API returns the details of the specified network resource, including the resource ID, type, status, and configuration parameters. If the specified network resource does not exist, you do not have the operation permission, or the input parameters are incorrect, the API will return an error message.

Deleting a Network Resource

This API is used to remove specified network resources. This API is used when you need to delete a specified network resource when the network resource is no longer required, the configuration is incorrect, or resources need to be cleared. Before using this API, ensure that the network resource exists and you have the administrator permissions. After the deletion, the specified network resource is permanently removed, and related configurations and associations are cleared. If the specified network resource does not exist, you do not have the operation permission, or the resource is depended on by other resources, the API will return an error message.

Updating a Network Resource

This API is used to update the configuration information of a specified network resource. This API is used when you need to update the details of a specified network resource, such as adjusting attributes, fixing configuration errors, or optimizing resource settings. Before using this API, ensure that the network resource exists and you have the administrator permissions. After the update, the configuration information of the specified network resource is modified, and the latest resource status and attributes are displayed. If the specified network resource does not exist, you do not have the operation permission, or the input parameters are incorrect, the API will return an error message.

Querying the Real-Time Resource Usage

This API is used to obtain the real-time usage of all resource pools in the current project. This API is used when you need to query the real-time usage of resource pools when monitoring resource usage, optimizing resources, planning capacity, or troubleshooting faults. The resource usage includes the usage of CPU, memory, and storage resources. Before using this API, ensure that you have the required permission and there is a running resource pool. After the query, the API returns the real-time usage data of the resource pool, including the usage percentage, resource type, and timestamp. If you do not have the required permission, the resource pool does not exist, or the system cannot obtain the real-time data, the API will return an error message.

Creating Resource Pools

This API is used to create a resource pool in the system. This API is used when you need to allocate resources for new services, optimize resource management, or isolate resources. You can use this API to create a resource pool to manage compute, storage, and network resources. Before using this API, ensure that you have the administrator permission and the system has sufficient resources to create resource pools. After the creation, the resource pool will be added to the system and be available for future resource allocation and management. If you do not have the required permission, the system resources are insufficient, or the input parameter is incorrect, the API will return an error message.

Obtaining Resource Pools

This API is used to obtain information about resource pools created in the system. This API is used when you need to query the resource pool list recorded in the system when monitoring resource pool status, planning resources, managing resource allocation, or auditing. Before using this API, ensure that you have the required permission and the resource pool exists in the system. After the query, the API returns the resource pool list, including the resource pool ID, name, type, status, and resource quota. If you do not have the required permission, the resource pools do not exist in the system, or the query parameter is incorrect, the API will return an error message.

Obtaining a Resource Pool

This API is used to obtain the details of a specified resource pool. This API is used when you need to query details about a specified resource pool, such as its configuration, status, resource usage, or resource management. Before using this API, ensure that you have the required permission and the specified resource pool exists in the system. After the query, the API returns the resource pool details, including the resource pool ID, name, type, status, resource quota, and usage. If the specified resource pool does not exist, the user does not have the permission to perform the operation, or the input parameters are incorrect, the API will return an error message.

Deleting a Resource Pool

This API is used to delete a specified resource pool. This API is used when you need to delete a specified resource pool when the resource pool is no longer required, the configuration is incorrect, or resources need to be cleared. Before using this API, ensure that the resource pool exists and you have the administrator permissions. After the deletion, the specified resource pool is permanently removed, and related resources and configurations are cleared. If the resource pool does not exist, you do not have the operation permission, or the resource pool is depended on by other resources, the API will return an error message.

Updating a Resource Pool

This API is used to update the configuration and capacity of a specified resource pool. This API is used when you need to update the information about a resource pool when the resource pool capacity needs to be expanded, the configuration needs to be adjusted, or the performance needs to be optimized. Before using this API, ensure that the resource pool exists and you have the administrator permissions. After the update, the configuration and capacity of the resource pool will be updated, and the related resources and configurations will be adjusted. If the resource pool does not exist, the user does not have the permission to perform the operation, or the resource pool cannot be updated, the API will return an error message.

Monitoring a Resource Pool

This API is used to obtain the real-time or historical monitoring information about a specified resource pool. This API is used when you need to obtain the monitoring data of a resource pool in real time, such as resource usage, performance status, or historical data. Before using this API, ensure that the resource pool exists and you have the administrator permissions. After the API is called, the system returns the monitoring information of the resource pool, including the resource usage, performance metrics, and historical trends. If the resource pool does not exist, the user does not have the permission to perform the operation, or the resource pool is unavailable, the API will return an error message.

Resource Pool Statistics

This API is used to obtain the statistics of a specified resource pool. This API is used when you need to obtain the resource usage, allocation, or usage of a resource pool. Before using this API, ensure that the resource pool exists and you have the administrator permissions. After the API is called, the system returns the statistics of the resource pool, including the total resource usage, allocated resources, usage, and resource allocation trend. If the resource pool does not exist, the user does not have the permission to perform the operation, or the resource pool is unavailable, the API will return an error message.

Obtaining Resource Specifications

This API is used to obtain available resource specifications. This API is used when you need to view or select resource specifications to create resource pools, allocate resources, or learn available resource specifications. Before using this API, ensure that you have the required permissions (such as administrator permissions or resource management permissions). After the API is called, the system returns the resource specifications, including the specification ID, name, number of CPUs, memory size, and storage capacity. If you do not have the required permission or the resource specifications are not configured, the API will return an error message.

Obtain Jobs in a Resource Pool

This API is used to obtain the job list in a specified dedicated resource pool. This API is used when you need to obtain details about a dedicated resource pool, such as resource usage, job status, or resource allocation. Before using this API, ensure that the dedicated resource pool exists and you have the required permissions (such as administrator permissions or resource management permissions). After the API is called, the system returns the job list of the dedicated resource pool, including the job ID, name, status, and resource usage. If the dedicated resource pool does not exist, the user does not have the operation permission, or the resource pool is unavailable, the API will return an error message.

Querying dedicated resource pool Job Statistics

This API is used to obtain job statistics of a dedicated resource pool. This API is used when you need to obtain the job running information, resource usage, or job status distribution of a dedicated resource pool. Before using this API, ensure that the dedicated resource pool exists and you have the required permissions (such as administrator permissions or resource management permissions). After the API is called, the system returns the job statistics of the dedicated resource pool, including the total number of jobs, number of running jobs, number of completed jobs, and resource usage. If the dedicated resource pool does not exist, the user does not have the operation permission, or the resource pool is unavailable, the API returns an error message.

Viewing an Authorization List

This API is used to view the authorization information.

Configuring Authorization

This API is used to configure ModelArts authorization.

Deleting Authorization

This API is used to delete the authorization of a specified user or all users.

Creating a ModelArts Agency

This API is used to create a ModelArts agency for ModelArts-dependent services, such as Object Storage Service (OBS), Software Repository for Container (SWR), and Intelligent EdgeFabric (IEF).

Querying Details About a Workspace

This API is used to query the details about a workspace.

Modifying a Workspace

This API is used to update the configuration information of a specified workspace.

Deleting a Workspace

This API is used to delete a created workspace.

Querying a Workspace Quota

This API is used to obtain the resource quota of a specified workspace.

Modifying a Workspace Quota

This API is used to update the resource quota of a specified workspace.

Querying a Workspace List

This API is used to obtain the details of all created workspaces.

Creating a Workspace

This API is used to create a workspace. The name of the created workspace cannot be default , which is the name of the default workspace reserved by the system.

Querying the Authorization Mode

This API is used to obtain the authorization mode and permission configuration information of a specified resource or function. This API is used when system administrators can use this API to view the access permission settings of resources. Developers can use this API to verify whether authorization policies are correctly configured. Security auditors can use this API to check whether authorization configurations comply with security specifications. Before using this API, ensure that you have the query permission and the authorization mode of the target resource or function has been configured. After the API is called, the API returns details about the authorization mode, including the authorization mode type, rules, and permission scope. If you do not have the permission to access this API or the authorization mode of the target resource is not configured, the API will return an error message.

Updating the Authorization Mode

This API is used to modify the authorization mode and permission configuration information of a specified resource or function. This API is used when system administrators can use this API to adjust the access permission of resources. Developers can use this API to update authorization policies to meet new service requirements. Security auditors can use this API to modify authorization configurations to comply with new security specifications. Before using this API, ensure that you have the update permission and the authorization mode of the target resource or function exists. After the API is called, the API updates the authorization mode of the target resource and returns the updated authorization mode information. If you do not have the permission to access this API or the authorization mode of the target resource does not exist, the API will return an error message.

Authenticating Whether the Current Workspace Can Be Used

This API is used to check whether a user has the permission to access and use resources in the current workspace. This API is used when you try to access or operate resources in the workspace, and the system needs to check whether you have the required permission. Before using this API, ensure that you have logged in and the workspace exists. If the authentication is successful, the user can access and use resources in the workspace. If the authentication fails, the API returns an error message, for example, insufficient permissions or the workspace does not exist.

Obtaining OS Quotas

This API is used to obtain the quotas of some ModelArts OS resources, such as resource pool quotas and network quotas. This API is used when you need to know the usage limits of resource pools or network resources, plan resource allocation, or monitor resource usage. Before using this API, ensure that ModelArts OS is deployed and you have the required permissions (such as administrator permissions or resource management permissions). After the API is called, the system returns details about resource pool quotas and network quotas, helping you better plan and manage resources. If you do not have the required permission, the service is unavailable, or the quota information is not configured, the API will return an error message.

Creating Resource Pool Tags in Batches

This API is used to add or update multiple tags for a specified resource pool. It is used when administrators need to manage resource pools by category (such as cost ownership and environment ID), configure metadata (such as project ownership and owner information) in batches, or update existing tag values. Before calling this API, ensure that the target resource pool exists and can be managed, you have the permissions to manage resource pool tags, and the submitted tag data complies with the format requirements (for example, the key is not empty and the value length is limited). After this API is called, the system adds a new tag to the resource pool or overwrites the value of the tag with the same name, and other configuration attributes of the resource pool are not affected. If the resource pool does not exist, you do not have the required permissions, the tag format is incorrect, or the system service is abnormal, an error message (such as "404 Not Found", "403 Forbidden", "400 Bad Request", or "503 Service Unavailable") is returned.

Deleting Resource Pool Tags in Batches

This API is used to delete multiple tags from a specified resource. It is used when administrators need to delete redundant tags (such as expired categories and invalid metadata), adjust resource classification policies, or remove tags in batches due to permission changes. Before calling this API, ensure that the target resource exists and can be managed, you have the required permissions to manage resource tags, the tags to be deleted have been associated with the resource, and TMS is running properly. After this API is called, the specified tags will be completely deleted from the resource, and other configuration attributes of the resource will not be affected. If the resource does not exist, you do not have the required permissions, the tags have not been associated with the resource, or the system service is abnormal, an error message (such as "404 Not Found", "403 Forbidden", "400 Bad Request", or "503 Service Unavailable") is returned.

Obtaining All Tags of Resource Pools

This API is used to obtain all tags of resource pools in the current project. By default, all workspaces are queried, but tag data is not returned for workspaces to which you do not have permissions. This API is used when you need to manage, classify, or collect statistics on resource pool tags. Before using this API, ensure that you have the required permission and the resource pool exists. After the API is called, the system returns the resource pool tags of all accessible workspaces in the current project. If you do not have the required permission, the resource pool does not exist, or the project is not created, the API will return an error message.

Obtaining Tags of a Resource Pool

This API is used to obtain the tag information of a specified resource pool. This API is used when you need to view, manage, or collect statistics on resource pool tags. Before using this API, ensure that the resource pool exists and you have the required permission. After the API is called, the system returns the tag information of the specified resource pool, including the tag key and tag value. If the resource pool does not exist, you do not have the access permission, or the resource pool is not configured with tags, the API will return an error message.

Obtaining Node Pools

This API is used to obtain the list of a specified node pool. This API is used when you need to obtain the details about a node pool, such as the configuration, status, or resource management. Before using this API, ensure that the node pool exists and you have the administrator permissions. After the API is called, the system returns the node pool list, including the node pool ID, name, number of nodes, and status. If the node pool does not exist, the user does not have the permission to perform the operation, or the node pool is unavailable, the API will return an error message.

Creating a Node Pool

This API is used to create a node pool. This API is used when you need to create a node pool with specified configurations when you need to expand compute resources, optimize resource allocation, or deploy new services. Before using this API, ensure that you have the administrator permission and the node pool parameters (such as the number of nodes, specifications, and network configurations) are correctly set. After the creation, the node pool will be created and be available, and the related node information will be recorded. If you do not have the required permission, the parameter settings are incorrect, or system resources are insufficient, the API will return an error message.

Obtaining Details About a Specified Node Pool

This API is used to obtain the details of a specified node pool. This API is used when you need to obtain the details about a node pool, such as the configuration, status, resource usage, or resource management. Before using this API, ensure that the node pool exists and you have the permission to access the node pool. After the API is called, the system returns the details about the node pool, including the node pool ID, name, number of nodes, status, creation time, and configuration parameters. If the node pool does not exist, the user does not have the permission to access the node pool, or the node pool is unavailable, the API will return an error message.

Updating a Node Pool

This API is used to update the configurations of a specified node pool. This API is used when you need to expand the capacity of a node pool, adjust node specifications, optimize resource allocation, or repair node pool configurations. Before using this API, ensure that the node pool exists and you have the administrator permissions. After the update, the configurations of the node pool will be updated, including the number of nodes, node specifications, and network configurations. If the node pool does not exist, the user does not have the permission to operate the node pool, or the configuration parameters are incorrect, the API will return an error message.

Deleting a Node Pool

This API is used to remove a created node pool. This function is not supported for yearly/monthly resource pools. This API is used when you need to delete a specified node pool when the tasks in the node pool are complete, the configuration is incorrect, or resources need to be cleared. Before using this API, ensure that the node pool exists and you have the administrator permissions. After the deletion, the node pool is permanently removed, and related resources and configurations are cleared. If the node pool does not exist, the user does not have the permission to perform the operation, or the node pool cannot be deleted, for example, it is a yearly/monthly resource pool or the node pool is in use, the API will return an error message.

Obtaining Nodes in a Node Pool

This API is used to obtain details about all nodes in a specified node pool. This API is used when you need to obtain the details about a node pool, such as the node status, resource usage, or resource management. Before using this API, ensure that the node pool exists and you have the permission to access the node pool. After the API is called, the system returns the node list of the node pool, including the node ID, name, status, IP address, and resource usage. If the node pool does not exist, the user does not have the permission to access the node pool, or the node pool is unavailable, the API will return an error message.

Querying Order Details

This API is used to query order details.

Creating a Plugin

This API is used to create plugin instances.

Querying the Plugin List

This API is used to list plugin instances.

Querying Tasks

This API is used to obtain the jobs of the current user.

Stopping a Service

This API is used to stop a service by changing its status from "Running" to "Stopping" and then to "Stopped." Use this API to stop a running service and save on resource costs. You must have the permission to stop the service. After the API call succeeds, the service status changes to "Stopping." The system then releases resources and saves the status. If you lack permission to stop the service, an error is returned.

Starting a Service

This API is used to change the status of a service from Stopped or Failed to Deploying. This API is used when you need to restart a service that has been stopped or fails to be started. Before calling this API, ensure that the service status is Stopped or Failed and you have the permission to start the service. After the API is successfully called, the service status changes to Deploying. The system starts the deployment process, including resource preparation and configuration loading. If the current status of the service is not Stopped or Failed, or you do not have the permission to start the service, an error is returned when the service is called.

Obtaining Services

Pagination and filtering are supported.

Creating a Service

This API is used to deploy a trained model as a real-time service during development or O&M to provide prediction or processing capabilities through APIs or HTTP APIs. Before calling this API, you must have the permission to create a service and provide a valid model image path and complete service configuration information (such as the service name, model image path, resource configuration, and upgrade configuration). After the API is successfully called, the system successfully creates and deploys the service. The service status changes to Deploying, and the unique ID of the service is generated and returned to you. Service details (such as the status, creation time, and update time) are also recorded in the system. If you do not have the permission to create a service, the provided model image path is invalid, or the service configuration information is incomplete, an error message is returned when you call. If insufficient resources or other internal errors occur during the deployment, the system returns the error message and records the error in the log.

Obtaining Service Details

This API is used to query service details based on a service ID. The caller can obtain the service name, status, service instance, and configuration parameters based on a valid service ID. The caller must have sufficient permissions and the entered service ID must be valid. If the query is successful, the service details are returned. If the query fails, the specified error code and error information is returned. If the service ID is invalid, the version number does not exist, or the user does not have the permission, "400 Bad Request" or "403 Forbidden" is returned.

Updating Service Configurations

This API is applicable to scenarios where model service configurations need to be dynamically adjusted. It is used to update and upgrade model performance parameters, resource pool configurations, and service call configurations. By calling this API, you can upgrade an existing service to a new version. Before calling this API, ensure that the service status is stopped, failed, or running, and you have the permission to modify the service. After the update is successful, the new configuration takes effect immediately. If the update fails, the service retains the original configuration and returns an error message. Common exceptions include parameter verification errors, permission verification errors, and service status errors. If the service ID is invalid, the version number does not exist, or the user does not have the permission, "400 Bad Request" or "403 Forbidden" is returned. If the service status cannot be switched, "400 Bad Request" is returned.

Obtaining the Real-Time Service Event List

This API applies to scenarios where real-time service events need to be monitored and managed. For example, users or O&M personnel need to periodically check service log events to detect and handle problems in a timely manner. By calling this API, you can obtain all event records of the current real-time service, including the event type, event information, time, and occurrence times. You must have the permission to query the service event list to successfully access this API. After the request is successful, the event list is returned. If the request fails, error information is returned. Common exceptions include permission verification errors, service status errors, and parameter verification errors.

Deleting Specified Services

This API is used to delete specified services. It is used when you need to clear resources, release compute, or manage multiple services. Before using this function, ensure that you have the permission to delete services and provide a valid service ID list. After the execution is successful, the specified services are stopped and related resources are released. If the service ID is invalid, the permission is insufficient, or the service status does not allow deletion, an error message is returned.

Adding Tags

This API is used to add metadata tags for resources (such as models, datasets, and services). For example, in resource management or classification, you can add tags to mark the usage, status, or other attributes of resources. By calling this API, you can add tags in batches. If a tag key already exists, its value will be updated. You must have sufficient permissions and the target resource must exist. After the tags are added successfully, the resource contains the new tag information. If the tags fail to be added, an error message is returned. Common exceptions include permission verification errors, resource non-existence errors, and parameter verification errors.

Deleting a Resource Tag

This API is used to remove specific tags from resources (such as models, datasets, and services). For example, in resource management or classification, you can delete tags to adjust or clear resource metadata. By calling this API, you can delete specified tags in batches. You must have sufficient permissions and the target resource must exist. After the tags are deleted successfully, the resources do not contain the specified tags. If the deletion fails, an error message is returned. Common exceptions include permission verification errors, resource non-existence errors, and parameter verification errors.

This API is used to query resource tags.

This API is used to obtain tag information about resources (such as models, datasets, and services). For example, in resource management or classification, you can query tags to learn about the usage, status, or other attributes of resources. By calling this API, you can obtain all tags of a specified resource by resource ID. You must have sufficient permissions and the target resource must exist. After the query is successful, the resource tag list is returned. If the query fails, error information is returned. Common exceptions include permission verification errors, resource non-existence errors, and parameter verification errors.

Querying Tags of a Type of Resources

This API is used to obtain tags of a type of resources (for example, a specified service) in the current project. For example, in resource management and monitoring, you can query tags to learn about the classification and attributes of each type of resources. By calling this API, you can obtain the tag list of a specified service in all workspaces. The workspace tag data that you do not have the permission to obtain is filtered out and not returned. You must have sufficient permissions and the target resource must exist. After the query is successful, the tag list of the specified service is returned. If the query fails, error information is returned. Common exceptions include permission verification errors, resource non-existence errors, and parameter verification errors.

Querying the Resource List by Tag

This API is used to search for resources by tag or resource name. For example, in resource management and search, you can search for resources by tag or fuzzy search. By calling this API, you can perform exact or fuzzy query based on multiple tags or resource names. If no tag is specified, all resources are returned. You must have sufficient permissions and the target resource must exist. After the query is successful, the list of resources that meet the query conditions is returned. If the query fails, an error message is returned. Common exceptions include permission verification errors, resource non-existence errors, and parameter verification errors.

Obtaining Resource Quantity by Tag

This API is used to collect statistics on and obtain the number of resources that meet the specified tag or resource name conditions. For example, in resource management and monitoring, you can perform exact or fuzzy search by tag or resource name to collect statistics on the number of resources. By calling this API, you can query resources based on multiple tags or resource names. If no tag is specified, the total number of resources is returned. You must have sufficient permissions and the target resource must exist. After the query is successful, the total number of resources that meet the query conditions is returned. If the query fails, an error message is returned. Common exceptions include permission verification errors, resource non-existence errors, and parameter verification errors.

Querying Details About a Managed Resource Pool

This API allows you to query details about a managed resource pool by specifying the resource pool ID, including the instance ID, name, flavor, instance status, and accessible URL of the instance. This function is applicable to users who need to monitor or manage cloud resources. Before using this API, ensure that users have the access permission and the correct resource pool ID. After the execution is successful, you can obtain the required instance details for further resource management and configuration. If the resource pool ID is invalid or the user does not have the access permission, the API returns an error message, for example, "404 Not Found" or "401 Unauthorized".

Obtaining Flavors Available for a Notebook Instance

This API is used to query the list of switchable specifications supported by the current resource instance. It is applicable to the scenario where the instance resource configuration needs to be adjusted. Before using this API, ensure that you have logged in and have the query permission. After the execution is successful, you will obtain a detailed list of specifications that can be changed, including the specification ID, name, and resource quota. You can use the list to change the instance specifications. If you do not have the query permission or the resource instance ID is invalid, the API returns an error message, for example, "401 Unauthorized" or "404 Not Found".

Binding an Application Key

This API is used to bind the generated API key to a specified service. It is applicable to the scenario where an application needs to call a specific service. Before calling this API, ensure that the service instances have been created and a valid API key has been obtained. After the binding is successful, the API key is used as the identity authentication credential for service calls to ensure that only authorized users can access the service. If you attempt to bind an invalid API key, an error message will be displayed, prompting you to check the validity and binding status of the API key.

Deleting an Application Key

This API is used to delete a specified API key. It is applicable to the scenario where the administrator needs to revoke the permission to access an application or a user. Before calling this API, ensure that the API key to be deleted has been obtained and is not used in other services. After the API key is deleted, it cannot be used to access any related services. If you attempt to delete an API key that does not exist or has been deleted, an error message is displayed, prompting you to check the validity of the API key.

Unbinding an Application Key

This API is used to unbind an API key from a specified service. This API is applicable to the scenario where the permission of an API key to access a specified service needs to be revoked. Before calling this API, ensure that the API key to be unbound has been obtained and bound to the specified service. After the unbinding is successful, the API key does not take effect for the specified service, but can still be used for other services. If you attempt to unbind an API key that does not exist or is not bound to a specified service, an exception message is returned, prompting you to check the validity and binding status of the API key.

Obtaining an Application Key

This API is used to query the API key list in the current system. This API is applicable to the scenario where the administrator or user needs to view and manage API keys. Before calling this API, ensure that you have the corresponding query permission. The returned list contains the basic information about each API key, such as the API key value, creation time, and bound service. If there is no API key in the system, an empty list or corresponding exception information is returned, prompting you to check the search criteria.

Creating an Application Key

This API is used to create an API key in the system. It is applicable to scenarios where access credentials need to be generated for users or applications. Before calling this API, ensure that you have the creation permission and provide necessary parameters, such as the user ID or application ID. After the creation is successful, the system generates a unique API key and returns the detailed information about the API key, including the API key value and creation time. If the provided parameter is invalid or the same API key already exists in the system, an exception message is returned, prompting you to check the validity of the input data.

Batch Binding Application Keys

This API is used to bind multiple generated apikeys to specified services in batches for accessing them. Before calling this API, ensure that the service instances have been created and a valid API key has been obtained. After the binding is successful, the API key is used as the identity authentication credential for service calls to ensure that only authorized users can access the service. If you attempt to bind an invalid API key or an API key that has been bound to the current service, an exception message is returned, prompting you to check the validity and binding status of the API key.

Batch Unbinding Application Keys

This API is used to unbind bound API keys from a specified service in batches. This API is applicable to the scenario where the access permission of multiple API keys on a specified service needs to be revoked. Before calling this API, ensure that the API keys to be unbound have been obtained and bound to the specified service. After the unbinding is successful, the API keys do not take effect for the specified service, but can still be used for other services. If you attempt to unbind an API key that does not exist or is not bound to a specified service, an exception message is returned, prompting you to check the validity and binding status of the API key.

Creating a Private Network Connection

This API is used to create a private network connection point in a specified region. It is applicable to scenarios where private network connections need to be configured for applications or services. Before calling this API, ensure that you have the required permission and have provided the necessary parameters, such as the region ID, private access point name, and network configuration information. After the creation is successful, the system generates a private network access point and returns the detailed information about the access point, including the access point ID, creation time, and status. If the provided parameters are invalid or the private network connection configuration conflicts, the system returns the corresponding exception information to prompt the user to check the validity of the input data and the configuration conflict.

Changing a Private Network Request

This API is used to change the status of a private network connection request. The status can be APPROVE, REJECT, CANCEL, or RETRY. It is applicable to the scenario where the private network connection approval process needs to be managed. Before calling this API, ensure that you have the corresponding change permission and provide a valid private network request ID and required operation type. After the change is successful, the status of the private network request is updated to the specified operation result, and related logs are recorded. If the provided private network request ID is invalid, the operation type is not supported, or the permission is insufficient, an error message is returned, prompting you to check the validity and permission of the input data.

Querying Private Network Connection Requests

This API is used to query all private network connection request records. It is applicable to scenarios where the private network connection request status needs to be managed and monitored. Before calling this API, ensure that you have the corresponding query permission. The returned list contains the basic information about each private network connection request, such as the application ID, creation time, status, and region ID. If the current tenant has no private network connection request record, an empty list is returned. If the permission is insufficient or other system errors occur when the API is called, an error is reported, prompting you to check the permission or contact technical support.

This API is used to query the private network connection approval list.

This API is used to query all private network connection approval records. It is applicable to scenarios where the private network connection approval status needs to be managed and monitored. Before calling this API, ensure that you have the corresponding query permission. The returned list contains the basic information about each private network connection approval, such as the approval ID, application time, status (such as pending approval, approved, and rejected), requester information, and region ID. If the current tenant has no private network connection approval record, an empty list is returned. If the permission is insufficient or other system errors occur when the API is called, an error is reported, prompting you to check the permission or contact technical support.

Batch Deleting Private Network Connections

This API is used to delete specified intranet access points in batches. It is applicable to the scenario where multiple private network access points that are no longer used need to be deleted. Before calling this API, ensure that you have the deletion permission and provide a valid private network access point ID list. After the deletion is successful, the specified private network access point is removed completely and does not take effect for any service. If the private network access point ID list contains invalid or deleted IDs, an error message is displayed, prompting you to check the validity of the IDs. Additionally, if the permission is insufficient or other system errors occur when the API is called, error information is returned to prompt the user to check the permission or contact technical support.

Modifying a Request for Adding a Custom URL

This API is used to modify and add a custom URL for a private network connection. It is used when multiple private network connections need to be updated or added at the same time. Before calling this API, ensure that you have the update permission and provide the parameters to be updated, such as the IP address, VPC ID, and subnet ID. New configurations will be added to the specified private network connections and take effect for related services. In the provided private network access ID list, if an ID is invalid or does not exist, the API returns an error message, prompting you to check the ID validity. If the provided update parameter does not meet the format requirements (for example, the IP address format is incorrect), the API returns an error message, prompting you to check the parameter validity.

Obtaining the Dynamic Mounting Storage Information List

This API is used to obtain the list of dynamic storage volumes mounted to a specified notebook instance.

Dynamic Mounting of Notebook Storage

This API is used to mount dynamic storage to a specified directory of a running notebook instance. After this API is called, the system mounts the specified storage instance to the notebook instance in Asynchronous mode. After the mounting is complete, you can read and write files of the storage instance in the container. If you do not have the permission to access the specified notebook instance or the notebook instance is not running, an error message is returned.

Obtaining Details About a Dynamically Mounted Storage Instance

This API is used to obtain details about the storage instances that have been mounted to a running notebook instance.

Dynamic Unmounting of Notebook Storage

This API is used to dynamically unmount a dynamic storage instance from a running notebook instance.

Querying All Lite Server Instances of a User

This API is used to obtain details about all Lite Server instances of a user. It is used when you need to view the status and configuration of all Lite Server instances of a user for resource management and monitoring. Before using this API, ensure that you have logged in to the system and have the permission to view Lite Server instances. After this API is called, the system returns the list of all Lite Server instances of the user, including the instance ID, name, status, and creation time. If you do not have the required permission or have not logged in, the API returns an error message.

Creating a Lite Server

This API is used to create Lite Server ECSs, BMSs, and supernode servers. It is used when you need to quickly deploy and configure different types of server resources based on service requirements. Before calling this API, ensure that you have logged in to the system and have the permission to create Lite Servers. In addition, you need to provide required parameters, such as the server type, specifications, and network configuration. After the creation, the system returns the information about the created Lite Server instance, including the instance ID and status. If you do not have the required permission, the parameter settings are incorrect, or system resources are insufficient, the API returns an error message.

Querying Lite Server Instance Details

This API is used to obtain the details of a specified Lite Server instance. It is used when you need to view the configuration, status, and network information of a specific Lite Server instance for fault locating, resource management, and monitoring. Before using this API, ensure that you have logged in to the system, have the permission to view the Lite Server instance, and have a valid instance ID. After the query, the system returns the details of the specified Lite Server instance, including the instance ID, name, status, configuration, and network configuration. If you do not have the required permission, the instance ID is invalid, or the instance does not exist, the API returns an error message.

Deleting a Lite Server Instance

This API is used to delete a created Lite Server instance. It is used when a pay-per-use Lite Server instance is no longer needed, fails to be created, or is in the ERROR state. Before using this API, ensure that the Lite Server instance exists and you have the administrator permissions. After the deletion, the Lite Server instance is permanently removed, and related resources are cleared. If the Lite Server instance does not exist or you do not have the required permission, the API returns an error message.

Changing the Lite Server Instance Name

This API is used to change the name of a created DevServer instance. It is used when you need to rename a DevServer instance to better reflect the function or usage of the instance, or when the instance name does not comply with the current project naming rules. Before using this API, ensure that the DevServer instance exists and you have the permission to manage the instance. After the modification, the new name of the instance takes effect immediately and is updated in all related views and records. If the DevServer instance does not exist, you do not have the required permission, or the new name does not comply with the naming rules, the API returns an error message.

Synchronizing the Status of All Lite Server Instances of a User in Real Time

This API is used to obtain and synchronize the status of a Lite Server instance in real time. It is used when you need to monitor the status of a Lite Server instance in real time to ensure that the instance is running properly or detect and handle exceptions in a timely manner. Before using this API, ensure that you have logged in to the system and have the required permission, and the Lite Server instance has been created and is running. After this API is called, the latest status of the Lite Server instance is returned, including the instance ID, status, and resource usage. If you do not have the required permission or the Lite Server instance does not exist, the API returns an error message.

Starting a Lite Server Instance

This API is used to start a Lite Server instance that has been created but is not running. It is used when you need to use a Lite Server instance for development or testing. Before using this API, ensure that the Lite Server instance has been created and is stopped, and you have the permission to start the instance. If the Lite Server instance does not exist or is running, or you do not have the required permission, the API returns an error message.

Stopping a Lite Server Instance

This API is used to stop a running Lite Server instance. It is used when you need to stop a Lite Server instance to save resources or perform maintenance. Before using this API, ensure that the Lite Server instance has been created and is running, and you have the permission to stop the instance. If the Lite Server instance does not exist or is stopped, or you do not have the required permission, the API returns an error message.

Creating a Lite Server Supernode Tag

This API is used to add a custom tag to a Lite Server supernode. It is used when you need to manage Lite Server supernodes by category or mark specific information. Before using this API, ensure that the Lite Server supernode exists and you have the permission to create tags. After the creation, the tag is added to the specified supernode. You can quickly search for and manage the supernode by tag. If the Lite Server supernode does not exist, the tag already exists, or you do not have the permission to perform operations on the supernode, the API returns an error message.

Deleting a Lite Server Supernode Tag

This API is used to delete a Lite Server supernode tag. It is used when you need to delete unnecessary tags or correct tag errors. Before using this API, ensure that the Lite Server supernode exists, the supernode has the tag to be deleted, and you have the permission to delete tags. After the deletion, the specified tag is removed from the supernode, and other configurations and data of the supernode remain unchanged. If the Lite Server supernode does not exist, the tag does not exist, or you do not have the permission to perform operations on the supernode, the API returns an error message.

Querying Lite Server Supernode Tags

This API is used to obtain all tag information on a Lite Server supernode. It is used when you need to view or manage tags of a Lite Server supernode. Before using this API, ensure that the Lite Server supernode exists and you have the permission to query tags. After the query, the API returns all tag information on the supernode, including the tag name and related attributes. If the Lite Server supernode does not exist or you do not have the permission to perform operations on the supernode, the API returns an error message.

Reinstalling the OS Image of a Lite Server

This API is used to reinstall the OS image of a Lite Server. It is used when you need to update the OS version, rectify system faults, or reconfigure the system environment. Before using this API, ensure that the Lite Server exists and is stopped, and you have the permission to reinstall the OS. After the reinstallation, the new OS image is installed for the Lite Server and the Lite Server starts running. If the Lite Server does not exist, is running, or you do not have the required permission, the API returns an error message.

Changing the OS Image of a Lite Server

This API is used to change the OS image of a Lite Server. It is used when you need to change the OS of a Lite Server to meet different development or test requirements. Before using this API, ensure that the Lite Server exists and is stopped, and you have the permission to switch the OS. After the OS is switched, the Lite Server will install the new OS image and enter the running state. If the Lite Server does not exist, is in the running state, or you do not have the operation permission, the API will return an error message.

Changing the OS Image of a Lite Server Supernode

This API is used to change the OS image of a Lite Server supernode. It is used when you need to change the OS of a Lite Server supernode to meet different development or test requirements. Before using this API, ensure that the Lite Server supernode exists and is stopped, and you have the permission to switch the OS. After the OS is switched, the Lite Server supernode will install the new OS image and enter the running state. If the Lite Server supernode does not exist, is in the running state, or you do not have the operation permission, the API returns an error message.

Obtaining Details About All Supernode Instances of a User

This API is used to obtain details about all Lite Server supernode instances of a user. It is used when you need to view the configuration, status, and usage of all supernode instances. Before using this API, ensure that you have logged in to the system and have the permission to query supernode instances. After the query, the API returns details about all supernode instances, including the instance ID, OS, status, and resource usage. If you do not have the required permission or the system does not have supernode instances, the API returns an error message.

Obtaining Details About a Specified Supernode Instance

This API is used to obtain the details of a specific Lite Server supernode instance. It is used when you need to view the configuration, status, and usage of a specified supernode instance. Before using this API, ensure that you have logged in to the system and have the permission to query the supernode instance, and the specified supernode instance exists. After the query, the API returns details about a specified supernode instance, including the instance ID, OS, status, and resource usage. If you do not have the required permission to perform the operation, the specified supernode instance does not exist, or the instance ID is invalid, the API returns an error message.

Deleting a Lite Server Supernode Instance

This API is used to delete a pay-per-use supernode instance and remove the Lite Server supernode instances in the ERROR state. It is used when a supernode instance is in the ERROR state due to creation failure or other reasons. Before using this API, ensure that you have logged in to the system and have the permission to delete a supernode instance, and the specified supernode instance is pay-per-use and in the RUNNING or ERROR state. After the deletion, the specified supernode instance is permanently removed, and related resources are cleared. If the specified supernode instance does not exist, is not in the ERROR state, or you do not have the operation permission, the API returns an error message.

Restarting a Lite Server Instance

This API is used to restart a running Lite Server instance. It is used when you need to restart a specified Lite Server instance to apply configuration changes, solve running problems, or maintain the system. Before using this API, ensure that the Lite Server instance has been created and is running, and you have the permission to restart the instance. After the restart, the Lite Server instance restarts and enters the running state. You can continue to use the services provided by the instance. If the Lite Server instance does not exist or is stopped, or you do not have the required permission, the API returns an error message.

Starting a Lite Server Supernode

This API is used to start a Lite Server supernode that has been created but is not running. It is used when you need to start a Lite Server supernode for development or testing. Before using this API, ensure that the Lite Server supernode has been created and is stopped, and you have the permission to start the supernode. After the startup, the supernode enters the running state, and you can access and use the services provided by the server. If the Lite Server supernode does not exist, is in the running state, or you do not have the operation permission, the API returns an error message.

Stopping a Lite Server Supernode

This API is used to stop a running Lite Server supernode. It is used when you need to stop a Lite Server supernode to save resources or perform maintenance. Before using this API, ensure that the Lite Server supernode has been created and is running or fails to be stopped, and you have the permission to stop the supernode. After the operation, the supernode is stopped and does not provide services. If the Lite Server supernode does not exist, is stopped, or you do not have the permission to stop the supernode, the API returns an error message.

Mounting a Disk to a Lite Server

This API is used to mount an additional disk to a Lite Server. It is used when you need to expand the storage space of a Lite Server to meet larger data storage requirements. Before using this API, ensure that the Lite Server has been created and is running or stopped, you have the permission to mount disks, and the specified disk exists and is not used by other servers. After the mounting, the disk is mounted to the Lite Server, and you can access and use the new storage space. If the Lite Server does not exist, the specified disk does not exist or is in use, or you do not have the required permission, the API returns an error message.

Binding an EIP to a Lite Server

This API is used to bind an EIP to a Lite Server. It is used when you need to assign a fixed public IP address to a Lite Server so that the Lite Server can be accessed from the external network. Before using this API, ensure that the Lite Server has been created and is running, you have the permission to bind an EIP, and the specified EIP exists and is not used by other resources. After the binding, the EIP is bound to the Lite Server and the Lite Server can be accessed from the external network through the EIP. If the Lite Server does not exist, the Lite Server is stopped, the specified EIP does not exist or is in use, or you do not have the required permission, the API returns an error message.

Query Bound EIPs

This API is used to obtain the information about the EIP bound to the Lite Server. It is used when you need to view the EIP bound to the Lite Server and the detailed information. Before using this API, ensure that you have logged in to the system and have the permission to query the EIP, and the specified Lite Server exists. After the query, the API returns the details of the EIP bound to the Lite Server, including the EIP address, binding time, and status. If the Lite Server does not exist, the EIP is not bound to the Lite Server, or you do not have the required permission, the API returns an error message.

Querying the Specification List

This API is used to obtain information about all available resource specifications in the system. It is used when you need to know the available resource specifications so that you can select proper configurations when creating or adjusting a Lite Server instance. Before using this API, ensure that you have logged in to the system and have the permission to query specifications. After the query, the API returns information about all available resource specifications, including the specification ID, CPU, memory, and storage. If you do not have the required permission or the system does not have available resource specifications, the API returns an error message.

Unmounting a Disk from a Lite Server

This API is used to unmount a disk from a Lite Server. It is used when you need to release storage resources or reallocate disks. Before using this API, ensure that the Lite Server has been created and is running or stopped, you have the permission to unmount disks, and the specified disk has been mounted to the server. After the unmounting, the disk is unmounted from the Lite Server, and you can mount the disk to another server or perform other operations. If the Lite Server does not exist, the specified disk is not mounted to the server, or you do not have the required permission, the API returns an error message.

Creating a RoCE Network

This API is used to create a RoCE network in the system. It is used when you need to create a dedicated RoCE network for high-performance computing or low-latency applications. Before using this API, ensure that you have logged in to the system and have the permission to create a RoCE network, and the required network resources have been configured in the system. After the creation, a RoCE network is created, and details about the RoCE network are returned, including the network ID, subnet information, and configuration parameters. If you do not have the required permission, the system lacks necessary network resources, or the network configuration parameters are invalid, the API returns an error message.

Querying the Lite Server List of a Tenant

This API is used to obtain all Lite Server instances of a specified tenant. It is used when you need to view the details of all Lite Server instances of a tenant for management and monitoring. Before using this API, ensure that you have logged in to the system and have the permission to query the Lite Server list of a tenant. After the query, the API returns the details of all Lite Server instances of the tenant, including the instance ID, name, status, and resource configuration. If you do not have the required permission or the tenant does not have Lite Server instances, the API returns an error message.

Querying Lite Server Image Details

This API is used to obtain the details of a specified Lite Server image. It is used when you need to know the configuration and attributes of a Lite Server image so that you can select a proper image when creating or adjusting a Lite Server instance. Before using this API, ensure that you have logged in to the system and have the permission to query image details, and the specified image exists. After the query, the API returns the details of the specified Lite Server image, including the image ID, name, OS, version, and creation time. If you do not have the operation permission, the specified image does not exist, or the image ID is invalid, the API returns an error message.

Querying the Lite Server Image List

This API is used to obtain information about all available Lite Server images in the system. It is used when you need to know the available Lite Server images so that you can select a proper image when creating or adjusting a Lite Server instance. Before using this API, ensure that you have logged in to the system and have the permission to query images. After the query, the API returns information about all available Lite Server images, including the image ID, name, and architecture type. If you do not have the permission to perform the operation or no image is available in the system, the API returns an error message.

Querying the HyperInstance List of a Tenant

This API is used to obtain information about all hyper instances of a specified tenant. It is used when you need to view the details of all hyper instances of a tenant for management and monitoring. Before using this API, ensure that you have logged in to the system and have the permission to query the hyper instance list of a tenant. After the query, the API returns the details of all hyper instances of the tenant, including the instance ID, name, status, and resource configuration. If you do not have the required permission or the tenant does not have hyper instances, the API returns an error message.

Obtaining Operation Details

This API is used to obtain the details of a specified operation. It is used when you need to know the execution status of an operation for troubleshooting or operation audit. Before using this API, ensure that you have logged in to the system and have the permission to query the details of an operation, and the specified operation exists. After the query, the API returns the details of the specified operation, including the operation ID, operation type, execution status, start time, end time, and operation result. If you do not have the operation permission, the specified operation does not exist, or the operation ID is invalid, the API returns an error message.

Querying the Supported Lite Server Scaling Specifications and Capacity Calculation

This API is used to obtain supported scaling specifications of a Lite Server supernode and calculate the capacity. It is used when you need to know the scaling options supported by the Lite Server supernode so that you can select proper specifications when adjusting the supernode resources and evaluate the resource requirements after scaling. Before using this API, ensure that you have logged in to the system and have the permission to query the supernode scaling specifications, and the specified supernode exists. After the query, the API returns the list of supported scaling specifications and capacity calculation results, including the specification ID, CPU, memory, storage, and resource usage after scaling. If you do not have the required permission, the specified supernode does not exist, or no scaling specifications are available in the system, the API returns an error message.

Scaling Out Lite Server Supernodes

This API is used to increase the resource capacity of a Lite Server supernode. It is used when you need to improve the performance of a Lite Server supernode to support more loads or process more data. Before using this API, ensure that you have logged in to the system and have the permission to expand the supernode capacity, and the specified supernode exists and is running. After the scale-out, the resource capacity of the supernode is adjusted based on the specified specifications. You can use the increased resources immediately. If you do not have the required permission to perform the operation, the specified supernode does not exist, the supernode has reached the maximum capacity, or the specified scale-out specifications are invalid, the API returns an error message.

Scaling in Lite Server Supernodes

This API is used to reduce the resource capacity of a Lite Server supernode. It is used when you need to reduce resource usage of Lite Server supernodes to reduce costs or optimize resource allocation. Before using this API, ensure that you have logged in to the system and have the permission to reduce the supernode capacity, and the specified supernode exists and is running. After the scale-in, the resource capacity of the supernode is adjusted based on the specified specifications. You can use the reduced resources immediately. If you do not have the required permission to perform the operation, the specified supernode does not exist, the supernode has reached the minimum capacity, or the specified scale-in specifications are invalid, the API returns an error message.

Querying the Logical Capacity Calculation Result of the hyperinstance-clusters Supernode

This API is used to obtain the logical capacity calculation result of a specified hyper instance cluster. It is used when you need to know the resource usage and capacity planning of a supernode cluster for resource management and optimization. Before using this API, ensure that you have logged in to the system and have the permission to query the logical capacity of a supernode cluster, and the specified supernode cluster exists. After the query, the API returns the logical capacity calculation result of a specified supernode cluster, including the available capacity information. If you do not have the required permission to perform the operation, the specified supernode cluster does not exist, or the cluster ID is invalid, the API returns an error message.

Querying the Tor Information of an Instance

This API is used to obtain the Top-of-Rack (Tor) switch information of a specified instance. It is used when you need to know the Tor switch connected to an instance for network configuration. Before using this API, ensure that you have logged in to the system and have the permission to query the Tor information of an instance, and the specified instance exists. After the query, the API returns the Tor information of the specified instance. If you do not have the operation permission, the specified instance does not exist, or the instance is not connected to the Tor switch, the API returns an error message.

Obtaining the Hyper Cluster Details List

This API is used to obtain details about all hyper clusters. It is used when you need to know the configuration and status of all supernode networks in the system. Before using this API, ensure that you have logged in to the system and have the permission to query hyper cluster details. After the query, the API returns details about all supernode networks, including the ID, name, and subnet information. If you do not have the required permission or the system does not have hyper clusters, the API returns an error message.

Creating a Hyper Cluster

This API is used to create a hyper cluster in the system. It is used when you need to use a supernode network and create a hyper cluster. Before using this API, ensure that you have logged in to the system and have the permission to create a hyper cluster, and the required resources have been configured in the system. After the creation, a supernode network is created, and details about the supernode network are returned, including the ID, name, and subnet information. If you do not have the required permission, the system does not have the required resources, or the configuration parameters are invalid, the API returns an error message.

Querying Hyper Cluster Instance Details

This API is used to obtain the details of a specified hyper cluster instance. It is used when you need to know the configuration and status of a supernode network for management and monitoring. Before using this API, ensure that you have logged in to the system, have the permission to query hyper cluster details, and the specified supernode network exists. After the query, the API returns details about the specified supernode network, including the ID, name, and subnet information. If you do not have the required permission to perform the operation, the specified supernode network does not exist, or the ID is invalid, the API returns an error message.

Deleting a Hyper Cluster Instance

This API is used to delete a created hyper cluster instance. It is used when the supernode network is incorrectly configured or resources need to be cleared. Before using this API, ensure that the hyper cluster instance exists and you have the administrator permissions. After the deletion, the supernode network is permanently removed, and related resources and configurations are cleared. If the hyper cluster instance does not exist or you do not have the operation permission, the API returns an error message.

Performing Operations on Lite Server Instances in Batches

This API is used to perform unified operations, such as starting, stopping, restarting, or deleting Lite Server instances. It is used when you need to perform the same operation on multiple Lite Server instances, for example, stopping instances in batches during maintenance, restarting instances in batches after configuration update, or clearing unnecessary instances. Before using this API, ensure that the target Lite Server instance exists and you have the required operation permissions. After the operation, all specified Lite Server instances will be changed or removed according to the request, and related resources and configurations will be adjusted or cleared accordingly. If the target Lite Server instance does not exist, you do not have the operation permission, or the request parameters are incorrect, the API returns an error message.

Querying Lite Server Job Details

This API is used to obtain the details of a specified Lite Server job. It is used when you need to view the execution status, configuration parameters, and log information of a Lite Server job. Before using this API, ensure that the target Lite Server job exists and you have the view permission. After the query, the API returns the details of the specified Lite Server job, including the job ID, status, creation time, execution time, configuration parameters, and logs. If the target Lite Server job does not exist or you do not have the required permission, the API returns an error message.

Querying the Lite Server Job List

This API is used to obtain the Lite Server job list and filter jobs by status and ID. It is used when you need to view the brief information about multiple Lite Server jobs. For example, you can use this API to obtain the jobs that meet the filter criteria during job status monitoring, troubleshooting, or routine management. Before using this API, ensure that you have the view permission. After the query, the API returns the Lite Server jobs that meet the search criteria, including the ID, status, and creation time. If you do not have the required permission or the request parameters are incorrect, the API returns an error message.

Deleting Lite Server Jobs in Batches

This API is used to remove multiple Lite Server jobs. It is used when multiple Lite Server jobs are completed, incorrectly configured, or resources need to be cleared. Before using this API, ensure that the target Lite Server job exists and you have the administrator permissions. After the deletion, the specified Lite Server job is permanently removed, and related resources and configurations are cleared. If the target Lite Server job does not exist, you do not have the required permission, or the request parameters are incorrect, the API returns an error message.

Creating a Lite Server Task

This API is used to create a Lite Server task. It is used when you need to start a development, test, or deployment task on the Lite Server. Before using this API, ensure that you have the permission to create a task and the task configuration parameters meet the requirements. After the creation, the Lite Server task is created, and the task ID and other related information are returned. If you do not have the required permission, the parameters are incorrect, or the system resources are insufficient, the API returns an error message.

Obtaining the Lite Server Job Template List

This API is used to obtain the list of available Lite Server job templates. It is used when you need to view available job templates and select a proper template to create a Lite Server task. After the query, the API returns all available Lite Server job templates, including the template ID, name, and description. If no template is available in the system, the API returns an error message.

Obtaining Lite Server Job Template Details

This API is used to obtain the details of a specified Lite Server job template. It is used when you need to view the detailed configurations of a specified job template to learn about the parameter settings and usage description. After the query, the API returns the details of the specified template, including the template ID, name, description, and configuration parameters. If the target template does not exist, the API returns an error message.

Obtaining Lite Server Service Details

This API is used to obtain Lite Server deployment service details based on the service ID. It is used when you need to view the details of a deployed service, such as the status and APIs of the service. Before using this API, ensure that you have the permission to view services. After the query, the API returns the details of the deployed service, including the name, status, description, used model, and instance details. If you do not have the required permission or the ID does not exist, the API returns an error message.

Obtaining Operation Details of a Supernode

This API is used to obtain the details of a specified operation. It is used when you need to know the execution status of an operation for troubleshooting or operation audit. Before using this API, ensure that you have logged in to the system and have the permission to query the details of an operation, and the specified operation exists. After the query, the API returns the details of the specified operation, including the operation ID, operation type, execution status, start time, end time, and operation result. If you do not have the operation permission, the specified operation does not exist, or the operation ID is invalid, the API returns an error message.

Starting a Service Deployment

This API is used to restart a deployment that has been stopped or failed to be started. The deployment status changes from Stopped or Failed to Deploying. Before calling this API, ensure that the deployment status is Stopped or Failed and you have the permission to start the deployment. After the API is called, the deployment status changes to Deploying. The system starts the deployment process, including resource preparation and configuration loading. If the current status of the deployment is not Stopped or Failed, or you do not have the permission to start the deployment, an error is returned.

Stopping a Real-Time Service Deployment

This API is used to stop a real-time deployment, which allows you to stop a running or operable deployment instance in a specific state. This API is applicable to scenarios where services need to be maintained or upgraded, or exceptions are detected. You can stop a service when the service is in the Running, Deploying, Failed, or Alarm state. Before using this API, ensure that the deployment instances can be stopped and you have the permission to call APIs. After the execution, the deployment is stopped. Related resources are released and new requests are not processed. If the deployment is not allowed to stop, the call permission is insufficient, or an error occurs in the system, the corresponding error message is returned.

Interrupting a Service Deployment

This API is used to quickly stop deployments in the Upgrading or Deploying state. This API is used when a critical fault occurs during deployment and needs to be rectified immediately, resources need to be quickly released for deployment with a higher priority, or fast iteration is required in the test environment. To use this API, ensure that the deployment is in the Upgrading or Deploying state and you have the permission to stop the deployment. If the deployment is in the Deploying state, the deployment status changes to Stopped, related resources are released, and terminal operations are recorded. If the deployment is in the Upgrading state, the deployment status changes to Running. If the deployment status is not Upgrading or Deploying and you do not have the permission to perform the operation, an error message is returned. If the deployment ID is invalid, the version number does not exist, or the user does not have the permission, "400 Bad Request" or "403 Forbidden" is returned.

Obtaining Service Deployments

Supports pagination and filtering, which is applicable to the scenario where you need to view the deployment list based on specific conditions (such as the service status and name) on the management console or through APIs. Before calling this API, you must have the permission to obtain the deployment list and provide valid pagination parameters (such as the page number and number of records on each page) and filter criteria (such as the deployment status and name). After this API is called, the system returns the deployment list that meets the filter criteria, including the data of the specified page, total number of pages, and total number of records. If you do not have the permission to query the deployment list, or the provided pagination parameters and filter criteria are invalid, an error message is returned. If an internal error occurs during the query, the system returns an error message and records the error in the log.

Adding a Deployment

This API is used to deploy a model as a real-time service.

Obtaining Service Deployment Details

This API is used to query deployment details based on a service ID and deployment ID. You can obtain the deployment name, status, service instance, and configuration parameters based on a valid service ID and deployment ID. You must have the required permissions and the entered service ID and deployment ID must be valid. If the query is successful, the deployment details are returned. If the query fails, the specified error code and error message is returned. If the service ID or deployment ID is invalid, the version number does not exist, or the user does not have the permission, "400 Bad Request" or "403 Forbidden" is returned.

Updating Service Deployment Configurations

This API is used to dynamically adjust the model service deployment configuration.

Deleting a Service Deployment

This API is used to delete a deployment of a service. If the service ID or deployment ID is invalid, the version number does not exist, or the user does not have the permission, "400 Bad Request" or "403 Forbidden" is returned.

Switching a Deployment to a Specified Version

This API is used to switch a deployment to a specified version. It is applicable to scenarios where the deployment needs to be switched between different versions for testing or rollback. If the request contains a valid service ID, deployment ID, and target version number, the version number must be a valid version that has been released. You must have the permission to manage the target service deployment, and the deployment must be in the Running state. After the switch, the new version is used immediately. If the service ID or deployment ID is invalid, the version number does not exist, or the user does not have the permission, "400 Bad Request" or "403 Forbidden" is returned. If the deployment status cannot be switched, "400 Bad Request" is returned.

Obtaining the Deployment Versions of a Real-Time Service

This API is used to obtain the version list of a specified service deployed. It is applicable to scenarios where you need to know the available versions of the current service deployment, for example, selecting a version or confirming the current version information. If the request contains a valid service ID and deployment ID, you can use the sorting parameter to sort the list. You must have the permission to view the target service deployment. After the request is successful, all real-time version information about the service deployment is returned, including the version number, release time, and status. If the service ID or deployment ID is invalid or the user does not have the permission, "400 Bad Request" or "403 Forbidden" is returned. If the service deployment does not have a real-time version, an empty list is returned.

Deleting a Real-Time Service Deployment Version

This API is used to delete a real-time version of a specified service deployment. It is used when you need to clear versions that are no longer used or optimize resource management.

Obtaining the Deployment Version Details of a Real-Time Service

This API is used to obtain details about a specified service deployment version. It is applicable to scenarios where you need to view the detailed configuration and status of a specified version, for example, confirming the functions, performance parameters, or release history of the version. The request must contain a valid service ID, deployment ID, and version number. You must have the permission to view the target service deployment. After the request is successful, the detailed information about the version is returned, including the version number, release time, configuration parameters, and status. If the service ID and deployment ID are invalid, the version number does not exist, or you do not have the permission, "400 Bad Request" or "403 Forbidden" is returned. If the service deployment does not have the version information, "404 Not Found" is returned.

Obtaining the Service Deployment Instance List

This API is used to obtain the service deployment instances of the current and filter them by status, which can be Running and Deleted. Pagination and keyword filtering are supported. It is used when you need to manage and monitor service instance status. Before calling this API, ensure that you have the query permission and provide optional filter criteria and pagination parameters. The returned list contains the basic information about all deployment instances, including the deployment name, latest update time, and status. If the current tenant does not have any service instance that meets the conditions or the provided parameters are invalid, an empty list or the corresponding error message is returned, prompting you to check the validity and permission of the input data.

Querying the Deployed Pod List of a Service

This API is used to obtain the deployed pod list of a specified service. You can choose whether to obtain only the running pods. It is used when you need to manage and monitor the pod status of service deployment. Before calling this API, ensure that you have the query permission and provide a valid service ID and deployment ID. Optionally, add a filter for pod status, like obtaining only running pods. The returned list contains the basic information about all pods, including the pod name, IP address and name of the node where the pod is located, pod role, status, and latest update time. If the specified service ID is invalid or the current service does not have a pod, an empty list or the corresponding error message is returned, prompting you to check the validity and permission of the input data.

Deleting Service Deployment Instances

This API is used to delete a specified deployment instance. It is applicable to scenarios where deployment instances are no longer used and need to be cleared or released. Before calling this API, ensure that you have the deletion permission and provide a valid service instance ID and deployment ID. After the deployment instance is deleted, it is permanently removed and does not take effect for any request. If the provided service instance ID and deployment ID are invalid, the service instance has been deleted, or the permission is insufficient, an exception message is returned, prompting you to check the validity and permission of the input data.

Deleting a Pod

This API is used to delete a specified pod. It is applicable to scenarios where pod resources are no longer used and need to be cleared or released. Before calling this API, ensure that you have the deletion permission and provide a valid pod ID. After the pod is deleted, the pod is completely removed and does not take effect for any service request. If the provided pod ID is invalid, the pod has been deleted, or the permission is insufficient, an exception message is returned, prompting you to check the validity and permission of the input data.

Querying Pod Events

This API is used to obtain Kubernetes events of a specified pod. It is applicable to scenarios where the pod running status needs to be monitored and checked. Before calling this API, ensure that you have the query permission and provide a valid pod ID. The returned event list contains details about all events, including the event type, occurrence times, event name, event information, and occurrence time. If the provided pod ID is invalid, the pod does not exist, or the permission is insufficient, an error message is returned, prompting you to check the validity and permission of the input data.

Manual Service Scaling

This API is used to scale model service instances. By calling this API, you can scale an existing service without adding a new version. Errors include permission verification errors, service status errors, and parameter verification errors.

Creating an Auto Scaling Policy

This API is used to create a scheduled scaling policy for a deployed service. It is applicable to scenarios where the number of service instances needs to be automatically adjusted based on the service load or at a specified time. Before calling this API, ensure that the service has been deployed, a valid service ID has been obtained, and detailed scaling policy parameters, such as the scaling time, instance quantity range, and condition trigger, have been provided. After the creation, the system automatically adjusts the number of service instances based on the preset policy. This ensures the performance and availability of the service within the specified period. If the provided service ID is invalid, the parameter settings are incorrect, or the system resources are insufficient, an error message is displayed, prompting you to check the validity of the input data or contact technical support.

Viewing an Auto Scaling Policy

This API is used to view auto scaling policies for a deployed service. Before calling this API, ensure that the service has been deployed and a valid service ID has been obtained. After the query is successful, the policy information corresponding to the service is returned, such as the rule ID, rule name, scaling type, scaling status, scaling cron expression, and number of target instances. If the provided service ID is invalid, the parameter settings are incorrect, or the system resources are insufficient, an error message is displayed, prompting you to check the validity of the input data or contact technical support.

This API is used to delete an auto scaling policy.

This API is used to delete a scheduled scaling policy from a deployed service. This API applies to scenarios where a service needs to be automatically deleted based on the service load or at a specified time. Before calling this API, ensure that the service has been deployed and the valid service ID and deployment ID have been obtained. If the provided service ID is invalid, the parameter settings are incorrect, or the system resources are insufficient, an error message is displayed, prompting you to check the validity of the input data or contact technical support. This API is not open currently. It is used by the backend to clear automatic scaling policy rules of a service.

Modifying an Auto Scaling Policy

This API is used to modify a scheduled scaling policy for a deployed service. It is applicable to scenarios where the number of service instances needs to be automatically adjusted based on the service load or at a specified time. Before calling this API, ensure that the service has been deployed, a valid service ID and deployment ID have been obtained, and detailed scaling policy parameters, such as the scaling time, instance quantity range, and condition trigger, have been provided. After the policy is modified, the system automatically adjusts the number of service instances based on the preset policy. This ensures the performance and availability of the service within the specified period. If the provided service ID is invalid, the parameter settings are incorrect, or the system resources are insufficient, an error message is displayed, prompting you to check the validity of the input data or contact technical support.

Viewing Auto Scaling Policy Events

This API is used to view the events (change history) of auto scaling policies for deployed services. Before calling this API, ensure that you have obtained a valid user project ID, service ID, and deployment ID. After the API is called, the policy event ID, event status, rule execution information, number of instances before and after scaling, number of preset target instances, and execution record time are returned. If the provided service ID is invalid, the parameter settings are incorrect, or the system resources are insufficient, an error message is displayed, prompting you to check the validity of the input data or contact technical support.

Creating an HRA Policy

This API is used to create an HRA policy for a deployed service that supports HRA policies. It is used when you need to automatically adjust the number of service instances based on the service load or at a specified time. Before calling this API, ensure that the service has been deployed and a valid service ID has been obtained. In addition, detailed HRA policy parameters, such as the HRA time, instance quantity range, and conditional trigger, have been provided. After the creation, the system automatically adjusts the number of service instances based on the preset policy. This ensures the performance and availability of the service within the specified period. If the provided service ID is invalid, the parameter settings are incorrect, or the system resources are insufficient, an error message is displayed, prompting you to check the validity of the input data or contact technical support.

Obtaining the Ratio Detection Information of an Inference Unit

This API is used to view the ratio detection information of inference units on a deployed service. Before calling this API, ensure that the service has been deployed and a valid service ID has been obtained. After the query, the policy information of the service is returned, including the rule ID, rule name, policy status, and HRA result status. If the provided service ID is invalid, the parameter settings are incorrect, or the system resources are insufficient, an error message is displayed, prompting you to check the validity of the input data or contact technical support.

Modifying the HRA Policy Configuration of a Specified Deployment

This API is used to modify the HRA policy configuration of a specified deployment for a service with created HRA policies. It is used when you need to automatically adjust the number of service instances based on the service load or at a specified time. Before calling this API, ensure that the service has been deployed and a valid service ID and deployment ID have been obtained. In addition, detailed HRA policy parameters, such as the HRA rule list, HRA result status, and policy status, have been provided. After the policy is modified, the system automatically adjusts the number of service instances based on the preset policy. This ensures the performance and availability of the service within the specified period. If the provided service ID is invalid, the parameter settings are incorrect, or the system resources are insufficient, an error message is displayed, prompting you to check the validity of the input data or contact technical support.