You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/cloud/pouta/launch-vm-from-web-gui.md
+33-20Lines changed: 33 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -211,50 +211,63 @@ Once the SSH keys and security groups are set, you can launch a new virtual mach
211
211
1. In the main page of the Pouta web interface, open the **Compute > Instances** view.
212
212
1. Click in **Launch Instance** on the top right. This opens a _launch instance_ screen where you define the properties of the new virtual machine.
213
213
214
-

214
+

215
215
216
216
**Figure** Launch the instance view
217
217
218
-
1. On the **Details** tab of the _launch instance_ view, first write the **Instance Name**.
218
+
1. On the **Details** tab of the _launch instance_ view, first write the **Instance Name** and select the number of instances you want to create ( _-x_ will be automatically added to the end of the name of the instance if you decide to set the **Count** > 1).
219
219
220
-
1.Select the **Flavour**, which is the "size" of the Virtual Machine that you will create. See [Virtual machine flavors and billing unit rates](vm-flavors-and-billing.md) for a complete list and descriptions.
220
+
1.Click **Next** and select your **Instance Boot Source**. Select "Image" in the drop down menu and click on the up arrow next to the available images.
221
221
222
-
1. In **Instance Count** you can specify the number of Virtual Machines to create. If in doubt, leave it to `1`.
222
+

223
223
224
-
1.**Instance Boot Source**. Select "Boot from image" in the drop down menu.
224
+
**Figure**Select the instance source
225
225
226
226
!!! Info "Cloud-native"
227
227
228
-
In case you want to be more cloud-native, you can select the "Boot from image (creates a new volume)" option. This option creates a new persistent volume for your instance. In the event you accidentally delete your instance or it enters an unrecoverable state, the file system of your instance will be saved in this volume. You can later use this volume to boot up a new instance with the same filesystem state as the previous instance.
228
+
In case you want to be more cloud-native, you can select the "Image" and set "Create a New Volume" to "Yes". This option creates a new persistent volume for your instance. In the event you accidentally delete your instance or it enters an unrecoverable state, the file system of your instance will be saved in this volume. You can later use this volume to boot up a new instance with the same filesystem state as the previous instance.
229
229
230
230
!!! Warning "Please note"
231
231
232
-
The "Boot from image (creates a new volume)" approach creates an additional volume which is billed normally as mentioned on our [pricing](https://research.csc.fi/billing-units) page.
232
+
The option "Create New Volume" set to "Yes" creates an additional volume which is billed normally as mentioned on our [pricing](https://research.csc.fi/billing-units) page.
233
233
234
+
If the flavour type has an ephemeral disk (for example, [I/O flavours](./vm-flavors-and-billing.md#io-flavors)), a new volume is only created for the root disk. [Ephemeral disks](./ephemeral-storage.md) are removed when the VM is deleted.
234
235
235
-
1.**Image Name**, this decides which Linux distribution to use. You can select the image that fits more your use case. The images provided by Pouta by default are regularly maintained up to date.
236
236
237
-
1.Under the **Access & Security** tab, you need to configure two options. First you need to choose the name of the *Key Pair* you have created in [**Setting up SSH keys**](#setting-up-ssh-keys). Secondly you need to select under the [**Security Groups**](#firewalls-and-security-groups)the security group previously created.
237
+
1.Select the **Flavour**, which is the "size" of the Virtual Machine that you will create, from the available flavours and by clicking the up arrow. See [Virtual machine flavors and billing unit rates](vm-flavors-and-billing.md) for a complete list and descriptions. You can also expand the flavour to check the impact on your quota.
238
238
239
-
!!! Warning "Key pairs cannot be added after creation"
240
-
A public key is only added to the VM if it has been specified in this step. After clicking on **Launch**, the VM will be created, and the configured key pairs cannot be changed. If no key pair is configured, the recommended solution is to delete the VM and start from scratch.
239
+

240
+
241
+
**Figure** Select the instance flavour
242
+
243
+
244
+
!!! Info "Warning quota usage"
245
+
246
+
Pay attention that you can have a warning sign indicating if your quota is sufficient to run a specific flavour. If your quota is not enough, you can send a request to our [Service Desk](mailto:servicedesk@csc.fi) by specifying the amount you want.
241
247
242
-

If you click the "+" button, the window will close unexpectedly and a small pop-up will appear:
250
+
1. The **Networks** section, make sure that your own network (your project name) is selected.
246
251
247
-

252
+

248
253
249
-
This is a known bug. Please refer to the [previous section](#setting-up-ssh-keys) on how to create your SSH keys.
254
+
1. In the next section [**Security Groups**](#firewalls-and-security-groups), you can assign the security group previously created. You can expand the security group to check the rules you set.
250
255
251
-
1. The **Networking** tab, make sure that your own network (your project name) is selected.
256
+

257
+
258
+
1. In [**Key Pair**](#setting-up-ssh-keys), you select the name of the _Key Pair_ you have created in the [**Setting up SSH keys section**](#setting-up-ssh-keys).
259
+
260
+

261
+
262
+
!!! Warning "Key pairs cannot be added after creation"
263
+
A public key is only added to the VM if it has been specified in this step.
264
+
After clicking on **Launch Instance**, the VM will be created, and the configured key pairs cannot be changed. If no key pair is configured, the recommended solution is to delete the VM and start from scratch.
252
265
253
-

266
+
1.**Configuration** section allows you to add a custom script to customize your instance after it has been launched.
254
267
255
-
1.Finally, **Advanced Options** tab allows you to select a [**Server Group**](#server-groups)
268
+
1.**Server Groups** tab allows you to select a [**Server Group**](#server-groups)
256
269
257
-
You can click **Launch** to start the Virtual Machine creation.
270
+
You can click **Launch Instance** to start the Virtual Machine creation.
0 commit comments