createLaunchConfiguration
- Print
- PDF
createLaunchConfiguration
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
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 VPC environment.
Summary
Create Launch Configurations.
Request
Note
To create a launch configuration in XEN/RHV/KVM hypervisor type, use serverImageNo and serverSpecCode.
If you use serverImageProductCode and serverProductCode, you can only create a launch configuration in XEN/RHV hypervisor type.
Request Parameters
| Parameter name | Requirement status | Type | Restrictions | Description |
|---|---|---|---|---|
| regionCode | No | String | Region code You can decide the region in which an Launch Configuration will be created. You can obtain the regionCode through the getRegionList action. Default: Select the first region of the getRegionList search results | |
| serverImageProductCode | Conditional | String | Server image product code You can set to use a new server image when creating a server with scale-out. One of the server image product code (serverImageProductCode) and member service image instance number (memberServerImageInstanceNo) must be entered. You can obtain the serverImageProductCode through the getServerImageProductList action. | |
| memberServerImageInstanceNo | Conditional | String | Member server image instance number You can set to use a server image created directly when creating a server with scale-out. One of the server image product code (serverImageProductCode) and member service image instance number (memberServerImageInstanceNo) must be entered. You can obtain the memberServerImageInstanceNo through the getMemberServerImageInstanceList action. | |
| serverImageNo | Conditional | String | - Server image number Entered when creating a launch configuration using a new server image You cannot use it with the member server image instance number (memberServerImageInstanceNo) and the server image product code (serverImageProductCode) at the same time serverImageNo can be obtained through the getServerImageList action | |
| serverProductCode | No | String | Server product code You can decide the server specifications when creating a server with scale-out. You can obtain the serverProductCode through the getServerProductList action. Default: The minimum specifications are selected. The minimum specifications are determined in the order of memory (1), CPU (2), default block storage size (3) and disk type (NET) (4). | |
| serverSpecCode | Conditional | String | - Server specification code Decides the specifications of the launch configuration to be created serverSpecCode can be obtained through the getServerSpecList action Available when using serverImageNo. Default: selects the minimum specifications. The minimum specifications are determined in the following order: 1. memory, 2. CPU, 3. default block storage size, and 4. disk type (NET) | |
| isEncryptedVolume | No | Boolean | Encryption status of the default block storage volume For RHV server image products, you can decide the encryption status of default block storage. Options : true | false Default : false | |
| initScriptNo | No | String | Initialization script number When the server boots for the first time, it can execute the initialization script set by the user. You can obtain the initScriptNo through the getInitScriptList action. | |
| launchConfigurationName | No | String | Min : 1, Max : 255 Only lower case English letters, numbers, and "-" are allowed, and it has to start with an English letter. It must end with an English letter or number. | Launch Configuration name Default: NAVER Cloud Platform automatically grants it. |
| loginKeyName | No | String | Login key name You can decide a key that encrypts and decrypts a password when accessing a server instance. You can obtain the loginKeyName through the getLoginKeyList action. Default: Use the name of the most recently created login key. | |
| responseFormatType | No | String | Format type of the response results 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; |
Example
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?