createLaunchConfiguration
- Print
- PDF
createLaunchConfiguration
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Available in VPC
Overview
Create a Launch Configuration.
Request
Note
To create a launch configuration with an XEN/RHV/KVM hypervisor-type server image, use serverImageNo and serverSpecCode.
In addition, using serverImageProductCode and serverProductCode, you can only create a server image of the XEN/RHV hypervisor type.
Request parameters
| Parameter name | Required | Type | Restrictions | Description |
|---|---|---|---|---|
| regionCode | No | String | - Region code Determine the Region in which the launch configuration will be created regionCode can be obtained through the getRegionList action Default: Select the first Region of the getRegionList search results | |
| serverImageProductCode | Conditional | String | - Server image product code When creating a server with scale-out, you can set it to use a new server image You must enter either the server image product code (serverImageProductCode) or the member server image instance number (memberServerImageInstanceNo) serverImageProductCode can be obtained through the getServerImageProductList action | |
| memberServerImageInstanceNo | Conditional | String | - Member server image instance number When creating a server with scale-out, you can set it to use the server image you created yourself You must enter either the server image product code (serverImageProductCode) or the member server image instance number (memberServerImageInstanceNo) memberServerImageInstanceNo can be obtained through the getMemberServerImageInstanceList action | |
| serverImageNo | Conditional | String | - Server image number When creating a server with scale-out, you can set it to use a new server image Member server image instance number (memberServerImageInstanceNo) and server image product code (serverImageProductCode) can't be used at the same time serverImageNo can be obtained through the getServerImageList action | |
| serverProductCode | No | String | - Server product code Determine the server specifications when creating a server with scale-out serverProductCode can be obtained through the getServerProductList action Default: The minimum specification is selected, where the minimum specification is based on 1. memory, 2. CPU, 3. default block storage size, 4. disk type (NET) | |
| serverSpecCode | Conditional | String | - Server specification code Determine the server specifications when creating a server with scale-out serverSpecCode can be obtained through the getServerSpecList action Available when using serverImageNo Default: Selected as the minimum specifications. The minimum specifications are determined in the following order: 1. determined in the order of memory (1), CPU (2), default block storage size (3), and disk type (NET) (4) | |
| isEncryptedVolume | No | Boolean | - Encryption status of the default block storage volume For RHV server image products, it decides the encryption status of the default block storage Options: true | false Default: false | |
| initScriptNo | No | String | - Initialization script number When the server is booted for the first time, the initialization script set by the user can be run initScriptNo can be obtained through the getInitScriptList action | |
| launchConfigurationName | No | String | Min: 1, Max: 255 Only lowercase English letters, numbers, and "-" are allowed, and it must start with an English letter It must end with an English letter or number | - Launch configuration name Default: NAVER Cloud Platform automatically assigns it |
| loginKeyName | No | String | - Login key name It decides a key that encrypts and decrypts the password when accessing server instances loginKeyName can be obtained through the getLoginKeyList action Default: Use the name of the most recently created login key. | |
| responseFormatType | No | String | - Format type of the response result Options: xml | json Default: xml |
Response
Response data type
- LaunchConfigurationList type
| LaunchConfigurationList extends CommonResponse |
|---|
| private Integer totalRows; |
| private List |
| LaunchConfiguration |
|---|
| private String regionCode; |
| private String launchConfigurationNo; |
| private String launchConfigurationName; |
| private String serverImageProductCode; |
| private String memberServerImageInstanceNo; |
| private String serverProductCode; |
| private String loginKeyName; |
| private Date createDate; |
| private CommonCode launchConfigurationStatus; |
| private String initScriptNo; |
| private Boolean isEncryptedVolume; |
Examples
Request example
ncloud vautoscaling createLaunchConfiguration --regionCode KR --serverImageProductCode SW.VSVR.OS.LNX64.CNTOS.0703.B050 --serverProductCode SVR.VSVR.STAND.C002.M008.NET.SSD.B050.G002 --isEncryptedVolume false --launchConfigurationName test-***
Response example
<createLaunchConfigurationResponse>
<requestId></requestId>
<returnCode>0</returnCode>
<returnMessage>success</returnMessage>
<totalRows>1</totalRows>
<launchConfigurationList>
<launchConfiguration>
<regionCode>KR</regionCode>
<launchConfigurationNo>***163</launchConfigurationNo>
<launchConfigurationName>test-***</launchConfigurationName>
<serverImageProductCode>SW.VSVR.OS.LNX64.CNTOS.0703.B050</serverImageProductCode>
<memberServerImageInstanceNo></memberServerImageInstanceNo>
<serverProductCode>SVR.VSVR.STAND.C002.M008.NET.SSD.B050.G002</serverProductCode>
<loginKeyName>test-***</loginKeyName>
<createDate>2020-12-07T13:08:50+0900</createDate>
<launchConfigurationStatus>
<code>CREAT</code>
<codeName>Created</codeName>
</launchConfigurationStatus>
<initScriptNo></initScriptNo>
<isEncryptedVolume>false</isEncryptedVolume>
</launchConfiguration>
</launchConfigurationList>
</createLaunchConfigurationResponse>
Was this article helpful?