changeLoadBalancedServerInstances
- Print
- PDF
changeLoadBalancedServerInstances
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Available in Classic
Change the server instance bound to a load balancer. Previously bound information is reset and bound anew.
Request
The following describes the request format for the endpoint. The request format is as follows:
| Method | URI |
|---|---|
| GET | /changeLoadBalancedServerInstances |
Request headers
For headers common to all Load Balancer APIs, see Load Balancer common headers.
Request query parameters
The following describes the parameters.
| Field | Type | Required | Description |
|---|---|---|---|
loadBalancerInstanceNo | String | Required | Number of the load balancer instance for which you want to change the bound setting |
serverInstanceNoList.N | List<String> | Required | List of server instance numbers to bind to the load balancer
|
Request example
The following is a sample request.
curl --location 'https://ncloud.apigw.ntruss.com/loadbalancer/v2/changeLoadBalancedServerInstances
?loadBalancerInstanceNo=*******
&serverInstanceNoList.1=*******'
--header 'x-ncp-apigw-timestamp: {Timestamp}'
--header 'x-ncp-iam-access-key: {Access Key}'
--header 'x-ncp-apigw-signature-v2: {API Gateway Signature}'
Response
The following describes the response format.
Response body
See LoadBalancerInstance for the response body.
Response status codes
For response status codes common to NAVER Cloud Platform, see Ncloud API response status codes.
Response example
The following is a sample response.
<changeLoadBalancedServerInstancesResponse>
<requestId>d6e80b53-658a-4adc-9683-83be3675d508</requestId>
<returnCode>0</returnCode>
<returnMessage>success</returnMessage>
<totalRows>1</totalRows>
<loadBalancerInstanceList>
<loadBalancerInstance>
<loadBalancerInstanceNo>********</loadBalancerInstanceNo>
<virtualIp>***.***.***.***,**.***.***.***</virtualIp>
<loadBalancerName>YOUR_LOAD_BALANCER</loadBalancerName>
<loadBalancerAlgorithmType>
<code>RR</code>
<codeName>Round Robin</codeName>
</loadBalancerAlgorithmType>
<loadBalancerDescription></loadBalancerDescription>
<createDate>2024-06-07T19:28:24+0900</createDate>
<domainName>***.com</domainName>
<loadBalancerInstanceStatusName>changing</loadBalancerInstanceStatusName>
<loadBalancerInstanceStatus>
<code>USED</code>
<codeName>NET USED state</codeName>
</loadBalancerInstanceStatus>
<loadBalancerInstanceOperation>
<code>CHANG</code>
<codeName>NET CHANGE OP</codeName>
</loadBalancerInstanceOperation>
<networkUsageType>
<code>PBLIP</code>
<codeName>Public</codeName>
</networkUsageType>
<isHttpKeepAlive>false</isHttpKeepAlive>
<connectionTimeout>60</connectionTimeout>
<certificateName></certificateName>
<region>
<regionNo>1</regionNo>
<regionCode>KR</regionCode>
<regionName>Korea</regionName>
</region>
<zoneList>
<zone>
<zoneNo>2</zoneNo>
<zoneName>KR-1</zoneName>
<zoneCode>KR-1</zoneCode>
<zoneDescription>Gasan zone</zoneDescription>
<regionNo>1</regionNo>
</zone>
</zoneList>
<loadBalancerRuleList>
<loadBalancerRule>
<protocolType>
<code>HTTP</code>
<codeName>http</codeName>
</protocolType>
<loadBalancerPort>80</loadBalancerPort>
<serverPort>80</serverPort>
<l7HealthCheckPath>/</l7HealthCheckPath>
<certificateName></certificateName>
<proxyProtocolUseYn>N</proxyProtocolUseYn>
<stickySessionUseYn>N</stickySessionUseYn>
<http2UseYn>N</http2UseYn>
</loadBalancerRule>
</loadBalancerRuleList>
<loadBalancedServerInstanceList>
<loadBalancedServerInstance>
<serverInstance>
<serverInstanceNo>********</serverInstanceNo>
<serverName>YOUR_SERVER</serverName>
<serverDescription></serverDescription>
<cpuCount>2</cpuCount>
<memorySize>4294967296</memorySize>
<baseBlockStorageSize>53687091200</baseBlockStorageSize>
<platformType>
<code>UBS64</code>
<codeName>Ubuntu Server 64 Bit</codeName>
</platformType>
<loginKeyName>YOUR_LOGIN_KEY</loginKeyName>
<isFeeChargingMonitoring>false</isFeeChargingMonitoring>
<publicIp></publicIp>
<privateIp>**.**.***.**</privateIp>
<serverImageName>ubuntu-18.04</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>2024-06-07T18:28:59+0900</createDate>
<uptime>2024-06-07T18:34:46+0900</uptime>
<serverImageProductCode>SPSW0LINUX000130</serverImageProductCode>
<serverProductCode>SPSVRSSD00000003</serverProductCode>
<isProtectServerTermination>false</isProtectServerTermination>
<portForwardingPublicIp>***.**.**.**</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>
<initScriptNo></initScriptNo>
<accessControlGroupList>
<accessControlGroup>
<accessControlGroupConfigurationNo>******</accessControlGroupConfigurationNo>
<accessControlGroupName>ncloud-default-acg</accessControlGroupName>
<accessControlGroupDescription>Default AccessControlGroup</accessControlGroupDescription>
<isDefault>true</isDefault>
<createDate>2021-06-22T18:09:57+0900</createDate>
</accessControlGroup>
</accessControlGroupList>
<instanceTagList/>
</serverInstance>
<serverHealthCheckStatusList>
<serverHealthCheckStatus>
<protocolType>
<code>HTTP</code>
<codeName>http</codeName>
</protocolType>
<loadBalancerPort>80</loadBalancerPort>
<serverPort>80</serverPort>
<l7HealthCheckPath>/</l7HealthCheckPath>
<proxyProtocolUseYn>N</proxyProtocolUseYn>
<serverStatus>false</serverStatus>
</serverHealthCheckStatus>
</serverHealthCheckStatusList>
</loadBalancedServerInstance>
</loadBalancedServerInstanceList>
</loadBalancerInstance>
</loadBalancerInstanceList>
</changeLoadBalancedServerInstancesResponse>
Response status codes
The following describes the response status codes.
| HTTP status code | Code | Message | Description |
|---|---|---|---|
| 400 | 24091 | No IP address is assigned to the server instance (no. {0}). | No IP address assigned to the server instance |
| 400 | 24109 | The input parameter instance number is invalid | Invalid instance number |
| 400 | 24120 | The input parameter server instance number is invalid | Invalid server instance number |
| 400 | 24123 | The input parameter load balancer instance number is invalid. | Invalid load balancer instance number |
| 400 | 25027 | You may not change since (other) user is operating the target load balancer. | Unable to change because another user is running the target load balancer |
| 400 | 25050 | (Other)Unable to operate load balancer since use is manipulating the applying. | Unavailable because the server is being applied to a load balancer |
Was this article helpful?