Scales up an Extreme Apsara File Storage NAS file system or a Cloud Paralleled File System (CPFS) file system.

Description

A General-purpose NAS file system is automatically scaled up when the threshold value is met. You do not need to call this operation to scale up a General-purpose NAS file system.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request parameters

Parameter Type Required Example Description
Action String Yes UpgradeFileSystem

The operation that you want to perform.

Set the value to UpgradeFileSystem.

FileSystemId String Yes 1ca404****

The ID of the file system.

  • Sample ID of a General-purpose NAS file system: 31a8e4****.
  • The IDs of Extreme NAS file systems must start with extreme-. Example: extreme-0015****.
  • The IDs of CPFS file systems must start with cpfs-. Example: cpfs-125487****.
Capacity Long Yes 100

The desired capacity of the file system.

The desired capacity of the file system must be greater than the original capacity of the file system. Unit: GiB.

DryRun Boolean Yes true

Specifies whether to perform a precheck on the request.

The precheck checks whether the request parameters are valid and whether the requested resources are available. The dry run does not scale up a file system or incur fees.

Valid values:

  • true: The validity of the request is checked but the request is not made. The check items include the request format, service limits, available NAS resources, and whether the required parameters are configured. If the precheck fails, an error message is returned. If the precheck is successful, the HTTP status code 200 is returned. No value is returned for the FileSystemId parameter.
  • false: The validity of the request is checked, and the request is made if the check is successful.
ClientToken String No 123e4567-e89b-12d3-a456-42665544****

The client token that is used to ensure the idempotence of the request. You can use the client to generate the value, but you must ensure that it is unique among different requests.

The token can contain only ASCII characters and cannot exceed 64 characters in length. For more information, see How do I ensure the idempotence of a request?

Note If you do not specify a value for this parameter, the system automatically uses the request ID as the client token. The ID of each request may be different.

Response parameters

Parameter Type Example Description
RequestId String 98696EF0-1607-4E9D-B01D-F20930B6****

The ID of the request.

Examples

Sample requests

http(s)://[Endpoint]/?Action=UpgradeFileSystem
&FileSystemId=1ca404****
&Capacity=100
&DryRun=true
&ClientToken=123e4567-e89b-12d3-a456-42665544****
&<Common request parameters>

Sample responses

XML format 

HTTP/1.1 200 OK
Content-Type:application/xml

<UpgradeFileSystemResponse>
    <RequestId>98696EF0-1607-4E9D-B01D-F20930B6****</RequestId>
</UpgradeFileSystemResponse>

JSON format 

HTTP/1.1 200 OK
Content-Type:application/json

{
  "RequestId" : "98696EF0-1607-4E9D-B01D-F20930B6****"
}

Error codes

For a list of error codes, visit the API Error Center.