createLaunchConfiguration
- Print
- PDF
createLaunchConfiguration
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Can be used in a VPC environment.
Summary
Create Launch Configurations.
Request
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. | |
serverProductCode | No | String | Server product code You can decide the server specifications when creating a server with scale-out. serverProductCode can be obtained 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). | |
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 body
Example
Request example
GET {API_URL}/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?