addNasVolumeAccessControl

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

Add NAS access control settings.
The access control permissions that have been set up can be viewed through the getNasVolumeAccessControlRuleList action.

Request

Request parameter

Response

Response body

• NasVolumeInstanceList

Examples

Request examples

GET {SERVER_API_URL}/addNasVolumeAccessControl
?nasVolumeInstanceNo=***3118
&accessControlRuleList.1.serverInstanceNo=***1003
&accessControlRuleList.1.writeAccess=true
&accessControlRuleList.2.customIp=***.***.3.81
&accessControlRuleList.2.writeAccess=true

Response examples

<addNasVolumeAccessControlResponse>
  <requestId>febe8512-95d7-48c7-a665-f5876c54197f</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>
        <nasVolumeInstanceCustomIp>
          <customIp>***.***.3.81</customIp>
        </nasVolumeInstanceCustomIp>
      </nasVolumeInstanceCustomIpList>
      <nasVolumeServerInstanceList>
        <serverInstance>
          <serverInstanceNo>***1003</serverInstanceNo>
          <serverName>s1669aa4e78c</serverName>
          <serverDescription/>
          <cpuCount>2</cpuCount>
          <memorySize>4294967296</memorySize>
          <baseBlockStorageSize>53687091200</baseBlockStorageSize>
          <platformType>
            <code>LNX64</code>
            <codeName>Linux 64 Bit</codeName>
          </platformType>
          <loginKeyName>juhoon-kim</loginKeyName>
          <isFeeChargingMonitoring>false</isFeeChargingMonitoring>
          <publicIp>***.***.46.237</publicIp>
          <privateIp>***.***.3.81</privateIp>
          <serverImageName>tensorflow-centos-7.3-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-10-22T16:19:50+0900</createDate>
          <uptime>2018-11-23T17:38:44+0900</uptime>
          <serverImageProductCode>SPSW0LINUX000066</serverImageProductCode>
          <serverProductCode>SPSVRSSD00000003</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>SSD</code>
            <codeName>SSD</codeName>
          </baseBlockStorageDiskDetailType>
          <serverInstanceType>
            <code>STAND</code>
            <codeName>Standard</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>
</addNasVolumeAccessControlResponse>

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.