addNasVolumeAccessControl
- 인쇄
- PDF
addNasVolumeAccessControl
- 인쇄
- PDF
기사 요약
이 요약이 도움이 되었나요?
의견을 보내 주셔서 감사합니다.
Classic 환경에서 이용 가능합니다.
개요
NAS의 접근제어 설정을 추가합니다.
설정된 접근제어 권한은 getNasVolumeAccessControlRuleList 액션을 통해 확인 가능합니다.
요청
요청 파라미터
파라미터 명 | 필수 여부 | 타입 | 제약사항 | 설명 |
---|---|---|---|---|
nasVolumeInstanceNo | Yes | String | - NAS볼륨인스턴스 번호 nasVolumeInstanceNo는 getNasVolumeInstanceList 액션을 통해 획득 가능 | |
accessControlRuleList.N.serverInstanceNo | Conditional | String | 중복 불가 | - 서버 인스턴스 번호 serverInstanceNo는 getServerInstanceList 액션을 통해 획득 가능 사용자가 소유하고 있는 서버의 인스턴스 번호만 입력 가능 한 개의 Rule에 serverInstanceNo 또는 customIp 둘중 한가지만 입력 |
accessControlRuleList.N.customIp | Conditional | String | 중복 불가 | - 커스텀 IP customIp는 getServerInstanceList 액션을 통해 획득 가능 사설 IP만 설정 가능 공인 IP 설정 불가 한 개의 Rule에 serverInstanceNo 또는 customIp 둘중 한가지만 입력 |
accessControlRuleList.N.writeAccess | No | Boolean | - 쓰기 권한 여부 Options : true | false Default : true |
응답
응답 바디
예시
요청 예시
GET {SERVER_API_URL}/addNasVolumeAccessControl
?nasVolumeInstanceNo=***3118
&accessControlRuleList.1.serverInstanceNo=***1003
&accessControlRuleList.1.writeAccess=true
&accessControlRuleList.2.customIp=***.***.3.81
&accessControlRuleList.2.writeAccess=true
응답 예시
<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>2</zoneNo>
<zoneName>KR-1</zoneName>
<zoneCode>KR-1</zoneCode>
<zoneDescription>KR-1 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>2</zoneNo>
<zoneName>KR-1</zoneName>
<zoneCode>KR-1</zoneCode>
<zoneDescription>KR-1 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>
에러 코드
아래 에러 코드는 이 액션(Action)에서 특징적으로 발생하는 에러입니다. 공통적으로 발생하는 에러에 대한 상세한 설명은 NAVER Cloud Platform API를 참고해주세요
HTTP Response Code | 리턴 코드 | 리턴 메시지 |
---|---|---|
400 | 24138 | The server information for setting up NFS is invalid. |
400 | 24152 | {0} IP is already entered. |
400 | 24153 | {0} IP is Loopback IP. |
400 | 24154 | {0} IP is public IP. |
400 | 24155 | Please check the IP {0}. |
400 | 24157 | IP {0} is not supported by region. |
이 문서가 도움이 되었습니까?