Skip to content

Commit 9526260

Browse files
authored
Merge pull request #2634 from CSCfi/new-pouta-vmlauncher
New Pouta instance launcher
2 parents a22e660 + 014fa27 commit 9526260

13 files changed

+38
-21
lines changed
-32 KB
Binary file not shown.
-34.6 KB
Binary file not shown.
13 KB
Loading
120 KB
Loading
86.4 KB
Loading
66.5 KB
Loading
66 KB
Loading
111 KB
Loading
63.7 KB
Loading

docs/cloud/pouta/launch-vm-from-web-gui.md

Lines changed: 33 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -211,50 +211,63 @@ Once the SSH keys and security groups are set, you can launch a new virtual mach
211211
1. In the main page of the Pouta web interface, open the **Compute > Instances** view.
212212
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.
213213

214-
![Launch the instance view](../../img/pouta-launch-instance.png 'Launch cPouta instance')
214+
![Launch the instance view](../img/pouta-launch-instance.png 'Launch cPouta instance')
215215

216216
**Figure** Launch the instance view
217217

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).
219219

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.
221221

222-
1. In **Instance Count** you can specify the number of Virtual Machines to create. If in doubt, leave it to `1`.
222+
![Select the instance source](../img/pouta-launch-instance-source.png 'Select the instance source')
223223

224-
1. **Instance Boot Source**Select "Boot from image" in the drop down menu.
224+
**Figure** Select the instance source
225225

226226
!!! Info "Cloud-native"
227227

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.
229229

230230
!!! Warning "Please note"
231231

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.
233233

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.
234235

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.
236236

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.
238238

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+
![Select the instance flavour](../img/pouta-launch-instance-flavor.png 'Select the instance flavour')
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.
241247

242-
![Launch the instance access view](../img/launch_instance_access_security.png 'Launch cPouta instance network')
248+
![Flavour warning](../img/pouta-launch-instance-flavor-warning.png 'Flavour warning')
243249

244-
!!! Warning
245-
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.
246251

247-
![Error plus button](../img/danger_keypairs.png 'Danger key pairs')
252+
![Launch the instance network](../img/pouta-launch-instance-networks.png 'Launch cPouta instance network')
248253

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.
250255

251-
1. The **Networking** tab, make sure that your own network (your project name) is selected.
256+
![Launch the instance security group](../img/pouta-launch-instance-security-groups.png 'Launch the instance security group')
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+
![Launch the instance key-pairs](../img/pouta-launch-instance-key-pairs.png 'Launche the instance key-pairs')
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.
252265

253-
![Launch the instance network view](../img/launch_instance_network.png 'Launch cPouta instance network')
266+
1. **Configuration** section allows you to add a custom script to customize your instance after it has been launched.
254267

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)
256269

257-
You can click **Launch** to start the Virtual Machine creation.
270+
You can click **Launch Instance** to start the Virtual Machine creation.
258271

259272
## Post creation step
260273

0 commit comments

Comments
 (0)