changeNasVolumeSize
- Print
- PDF
changeNasVolumeSize
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
The latest service changes have not yet been reflected in this content. We will update the content as soon as possible. Please refer to the Korean version for information on the latest updates.
Can be used in a Classic environment.
Overview
Resize NAS volume.
Request
Request parameter
Parameter name | Requirement status | Type | Restrictions | Description |
---|---|---|---|---|
nasVolumeInstanceNo | Yes | String | - NAS volume instance number You can obtain nasVolumeInstanceNo through the getNasVolumeInstanceList action. | |
volumeSize | Yes | Long | 500 GB or more/10,000 GB or less | - NAS volume capacity Options : 500GB ~ 10,000GB |
isAsync | No | Boolean | - Async status Options : true | false Default : false |
Response
Response body
Examples
Request examples
GET {SERVER_API_URL}/changeNasVolumeSize
?nasVolumeInstanceNo=***3118
&volumeSize=1000
Response examples
<changeNasVolumeSizeResponse>
<requestId>dccb8b18-d15d-4927-b98a-c9bd7512ddf2</requestId>
<returnCode>0</returnCode>
<returnMessage>success</returnMessage>
<totalRows>1</totalRows>
<nasVolumeInstanceList>
<nasVolumeInstance>
<nasVolumeInstanceNo>***3118</nasVolumeInstanceNo>
<nasVolumeInstanceStatus>
<code>CREAT</code>
<codeName>NAS create</codeName>
</nasVolumeInstanceStatus>
<nasVolumeInstanceOperation>
<code>NULL</code>
<codeName>NAS NULL OP</codeName>
</nasVolumeInstanceOperation>
<nasVolumeInstanceStatusName>created</nasVolumeInstanceStatusName>
<createDate>2018-11-26T11:09:28+0900</createDate>
<nasVolumeDescription></nasVolumeDescription>
<mountInformation>***.***.53.74:/n***2613_test10</mountInformation>
<volumeAllotmentProtocolType>
<code>NFS</code>
<codeName>NFS</codeName>
</volumeAllotmentProtocolType>
<volumeName>n***2613_test10</volumeName>
<volumeTotalSize>1073741824000</volumeTotalSize>
<volumeSize>1073741824000</volumeSize>
<snapshotVolumeConfigurationRatio>0.0</snapshotVolumeConfigurationRatio>
<snapshotVolumeSize>0</snapshotVolumeSize>
<isSnapshotConfiguration>false</isSnapshotConfiguration>
<isEventConfiguration>false</isEventConfiguration>
<region>
<regionNo>1</regionNo>
<regionCode>KR</regionCode>
<regionName>Korea</regionName>
</region>
<zone>
<zoneNo>3</zoneNo>
<zoneName>KR-2</zoneName>
<zoneCode>KR-2</zoneCode>
<zoneDescription>Pyeongchon zone</zoneDescription>
<regionNo>1</regionNo>
</zone>
<isReturnProtection>false</isReturnProtection>
<nasVolumeInstanceCustomIpList/>
<nasVolumeServerInstanceList>
<serverInstance>
<serverInstanceNo>***507</serverInstanceNo>
<serverName>s165d2104110</serverName>
<serverDescription></serverDescription>
<cpuCount>1</cpuCount>
<memorySize>2147483648</memorySize>
<baseBlockStorageSize>53687091200</baseBlockStorageSize>
<platformType>
<code>LNX64</code>
<codeName>Linux 64 Bit</codeName>
</platformType>
<loginKeyName>juhoonkim</loginKeyName>
<isFeeChargingMonitoring>false</isFeeChargingMonitoring>
<publicIp></publicIp>
<privateIp>***.***.0.56</privateIp>
<serverImageName>centos-6.6-64</serverImageName>
<serverInstanceStatus>
<code>RUN</code>
<codeName>Server run state</codeName>
</serverInstanceStatus>
<serverInstanceOperation>
<code>NULL</code>
<codeName>Server NULL OP</codeName>
</serverInstanceOperation>
<serverInstanceStatusName>running</serverInstanceStatusName>
<createDate>2018-09-13T17:33:26+0900</createDate>
<uptime>2018-11-23T17:32:23+0900</uptime>
<serverImageProductCode>SPSW0LINUX000044</serverImageProductCode>
<serverProductCode>SPSVRSTAND000003</serverProductCode>
<isProtectServerTermination>false</isProtectServerTermination>
<portForwardingPublicIp>***.***.51.90</portForwardingPublicIp>
<zone>
<zoneNo>3</zoneNo>
<zoneName>KR-2</zoneName>
<zoneCode>KR-2</zoneCode>
<zoneDescription>Pyeongchon zone</zoneDescription>
<regionNo>1</regionNo>
</zone>
<region>
<regionNo>1</regionNo>
<regionCode>KR</regionCode>
<regionName>Korea</regionName>
</region>
<baseBlockStorageDiskType>
<code>NET</code>
<codeName>Network Storage</codeName>
</baseBlockStorageDiskType>
<baseBlockStorageDiskDetailType>
<code>HDD</code>
<codeName>HDD</codeName>
</baseBlockStorageDiskDetailType>
<serverInstanceType>
<code>COMPT</code>
<codeName>Compact Server</codeName>
</serverInstanceType>
<userData></userData>
<accessControlGroupList>
<accessControlGroup>
<accessControlGroupConfigurationNo>***9995</accessControlGroupConfigurationNo>
<accessControlGroupName>ncloud-default-acg</accessControlGroupName>
<accessControlGroupDescription>Default AccessControlGroup</accessControlGroupDescription>
<isDefault>true</isDefault>
<createDate>2018-04-09T11:12:54+0900</createDate>
</accessControlGroup>
</accessControlGroupList>
<instanceTagList/>
</serverInstance>
</nasVolumeServerInstanceList>
</nasVolumeInstance>
</nasVolumeInstanceList>
</changeNasVolumeSizeResponse>
Error codes
Errors that may occur while using this action are listed below. For more information about common errors, please refer to NAVER Cloud Platform API.
HTTP Response Code | Return code | Return message |
---|---|---|
400 | 10107 | Unable to create(change) volume anymore since creation limitation setting has been exceeded. Creation limitation(GB): {0} Created(GB) : {1} |
400 | 23013 | Insufficient storage space required to create volume. Please contact your manager for troubleshooting. |
400 | 24303 | {0} GB volume is in use. You can not change the volume size to less than the amount of use. |
Was this article helpful?