getLoadBalancedServerInstanceList
- Print
- PDF
getLoadBalancedServerInstanceList
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Overview
Gets a list of server instances bound to a load balancer.
Request
Request header
Header | Description |
---|---|
x-ncp-apigw-timestamp | It is the number of milliseconds that have elapsed since January 1, 1970 00:00:00 UTC. If the time difference with the API Gateway server is more than 5 minutes, the request is considered invalid. |
x-ncp-apigw-api-key | API key issued by API Gateway (not used in the API v2.) |
x-ncp-iam-access-key | API key issued by NAVER Cloud Platform or access key issued by IAM |
x-ncp-apigw-signature-v2 | Signature used to encrypt the body with the “secret key” that maps with the “access key.” The HMAC encryption algorithm is HMAC SHA256. |
Request parameters
Parameter | Required | Type | Limitations | Description |
---|---|---|---|---|
loadBalancerInstanceNo | Y | String | Load balancer instance number. You can get a list of server instances bound to a specific load balancer instance. Get available values by using the getLoadBalancerInstanceList action. |
Response
Response body
Examples
Request example
GET {LOADBALANCER_API_URL}/loadbalancer/v2/getLoadBalancedServerInstanceList?loadBalancerInstanceNo=1083198
Response example
Errors that may occur while using this action are listed below. For information on common errors, refer to NAVER Cloud Platform.
<getLoadBalancedServerInstanceListResponse>
<requestId>4037a499-0ea5-445c-933f-cbbb42fb155c</requestId>
<returnCode>0</returnCode>
<returnMessage>success</returnMessage>
<totalRows>1</totalRows>
<serverInstanceList>
<serverInstance>
<serverInstanceNo>1083616</serverInstanceNo>
<serverName>s1674e938b61</serverName>
<serverDescription></serverDescription>
<cpuCount>2</cpuCount>
<memorySize>4294967296</memorySize>
<baseBlockStorageSize>53687091200</baseBlockStorageSize>
<platformType>
<code>LNX64</code>
<codeName>Linux 64 Bit</codeName>
</platformType>
<loginKeyName>penguinit</loginKeyName>
<isFeeChargingMonitoring>false</isFeeChargingMonitoring>
<publicIp></publicIp>
<privateIp>10.41.84.42</privateIp>
<serverImageName>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-11-26T14:52:32+0900</createDate>
<uptime>2018-11-26T14:55:29+0900</uptime>
<serverImageProductCode>SPSW0LINUX000046</serverImageProductCode>
<serverProductCode>SPSVRSSD00000003</serverProductCode>
<isProtectServerTermination>false</isProtectServerTermination>
<portForwardingPublicIp>106.10.32.172</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>8813</accessControlGroupConfigurationNo>
<accessControlGroupName>ncloud-default-acg</accessControlGroupName>
<accessControlGroupDescription>Default AccessControlGroup</accessControlGroupDescription>
<isDefault>true</isDefault>
<createDate>2017-04-29T21:34:31+0900</createDate>
</accessControlGroup>
</accessControlGroupList>
<instanceTagList/>
</serverInstance>
</serverInstanceList>
</getLoadBalancedServerInstanceListResponse>
Was this article helpful?