Launch Instance

Prerequisites

In this section you will learn how to deploy one or more VM instances, supported by the “Launch Instance Wizard “, where you will be asked for the necessary information. In addition you can create the necessary prerequisites e.g. create a network, or create an SSH key for later access to the VM.

Tip

We recommend that you configure a Router with Network (see Setup Network Topology) and SSH Keys (see Create SSH Key Pair) in advance if possible.

Start Wizard

Now switch in navigation to “Network > Network Topology”, click the “Launch Instance” button and enter the needed information. With “Next” you get to the next input mask. Once all “mandatory information” is entered the button “Launch Instance” is activated (blue) and you can deploy the VM(s) “launch”.”

../_images/launch-vm0.png

Details

  • Now enter the missing information in the input mask Details:
    • “Instance Name” - the name of the instance and, if applicable, a description in the field “Description”
    • “Availability Zone” - select where the instance should be deployed
    • “Count” - Number of instances that have the same settings to be deployed.
    • now click on “Next”
../_images/launch-vm1.png

Note

OpenStack offers several options for selecting the Boot Source, which must be taken into account in the Flavor step when selecting the Flavor type.

The most common options are

Boot Source Create New Volume ** compatible flavor types ** Comment
Image Yes All “Zero-Disk” Flavor’s (g*) e.g. g1.2c4m, Total Disk = 0 A new Boot Volume will be created, where you can specify the Size (GB) of it.
Image No All “Standard” Flavors (e* & m*) e.g. e1.micro, Total Disk = 20GB Flavor must have a Root Disk included see Flavor List Column “Root Disk” >0 GB

See also

Differences between the flavor types in Table

Source

In the following example, a zero-disk flavor is used to create a volume.

“Now select the image with the corresponding operating system”.

  • Enter the missing information in the input mask Source:
    • “Select Boot Source”: “Image”
    • “Create New Volume”: “Yes”
    • ”Volume Size GB”: please enter the desired size for your Root-Volume
    • “Delete Volume on Instance Delete”: “No “ Important [1]
    • Use the arrow to select the desired “Image” from the list
    • now click on “Next”
../_images/launch-vm2.png

The selected image is displayed.

../_images/launch-vm2a.png

Flavor

Next, select the appropriate configuration (vCPU, RAM) for your VM in the Flavor input mask by selecting a Flavor:
  • You can use the filter to display the list more clearly
  • to select click e.g. on the line “g1.2c4m” on the right the arrow up
../_images/launch-vm3.png
now the selected flavor appears at the top of the Allocated section. Use the Down arrow to undo the selection and select another Flavor.
  • By selecting the Flavor all necessary information for deploying the VM is already given and you can click “Lauch Instance” to complete the process.
  • If you want to make optional further settings, e.g. create or select a SSH Key Pair then click directly on this point in the navigation, or with “Next” up to the desired input mask.
../_images/launch-vm3a.png

Note

Behind the arrow Details you will find a lot of information about the respective Flavor, e.g. effects on your Quota Limit, Disk QoS or VIF QoS.

Networks

  • If you have already created a network as recommended, it will be automatically selected here (Allocated). If you have multiple networks, please select the network in which your VM should be deployed.
    • now click on “Next”
../_images/launch-vm4.png

Network Ports

  • Optionally you can connect your VM to ports here, if you created it before.
    • now click on “Next”
../_images/launch-vm5.png

Security Groups

  • By default your VM is assigned in the “Default Security Group”. Optionally you can assign your VM to another Security Group if you created it before. You can also change the Security Group later.
    • now click on “Next”
../_images/launch-vm6.png

Key Pair

  • If you have already created a “ssh Key Pair” before, you can select it here, import an existing Key Pair or create a new one (see Create SSH Key Pair)
    • now click on “Next”
../_images/launch-vm7.png

Configuration

  • Optionally, you could store configurations here, which should be executed after starting your VM. This requires a deep understanding of the system, which is not covered here.
    • now click on “Next”
../_images/launch-vm8.png

Server Groups

  • Optionally you could assign your VM to a previously created “Server Group”, which can be helpful for larger installations. This requires a deep understanding of the system, which is not covered here.
    • now click on “Next”
../_images/launch-vm9.png

Scheduler Hints

  • With this option the “scheduler process”, which the VM deploys, could be given additional “hints” (e.g. CPU type), which should be considered if possible. This requires a deep understanding of the system, which is not covered here.
    • now click on “Next”
../_images/launch-vm10.png

Metadata

  • This option could be used to add data to the “meta data”, the VM instance. This requires a deep understanding of the system, which is not covered here.
    • now click on “Next”
../_images/launch-vm11.png

If you have entered all necessary information, the button “Lauch Instance” should now be activated and you can now click it to deploy the VM. If any information is missing, this is indicated by an *(asterisk) on the left in the corresponding section.

You can now see the status of your VM in the navigation under “Compute > Instances”.

../_images/instances1.png

Footnotes

[1]For example, if you need to temporarily delete the corresponding Instance for a re-sizing of the Root volume, the volume will remain and you can use it again after the volume re-size to create a new instance (VM). Otherwise, the associated root volume will also be deleted without warning when the instance is deleted!