Launching an instance¶

With the network, security group, and ssh keys setup, you should be ready to launch an instance.
On the left side bar, click on Project → Compute → Instances
Click Launch Instance
Give your instance a descriptive name. You can take the defaults for the rest of the items.
Click Next.

On the Source screen, make sure the Select Boot Source option is Image

Please note that it may take several seconds for all the image options to appear and to fully populate that list as horizon pulls the entire image catalog listing over again each time!
Type Featured in the Available box to find the Jetstream Featured images. You can also boot any of community or public visibility images shown in the list if you’d rather do that, but Jetstream staff have only tested or will support the featured images.
Find the image you want to use and click the arrow to the right of its name. You’ll see it show up under Allocated towards the top of the dialog box.
Click Next.

Image Visbility

If you are deploying a non-public image that has been shared to your project from another project, you will need to choose the correct VISIBILITY filter option in the dropdown menu as the list defaults to only public or your own private images.

Some users may find the pre-defined default ephemeral-storage-based root disks do not provide sufficient flexibility.
For these cases, users may create a custom-sized volume from which to boot.
- ADVANTAGES: volume-backed instances allow users to create any size root disk for an instance that they need (limited only by ext4 or xfs filesystem limits). Additionally, actions such as shelving and unshelving happen VERY quickly relative to fixed ephemeral root disks.
- DISADVANTAGES: –> Volume-backed instances count against the project’s storage quota. <–
As above:
- On the Source screen, make sure the Select Boot Source option is Image
- Type Featured in the Available box to find the Jetstream Featured images.
- Find the image you want to use and click the arrow to the right of its name. You’ll see it show up under Allocated towards the top of the dialog box.
NEW: Change Create New Volume to Yes
- The setting for Delete Volume on Instance Delete can be set to Yes or No. We recommend Yes.
Click Next.

On the Flavor screen, select the size VM you want to use and click the arrow to the right of its description.
Like the previous screen, you’ll see it move up into the Allocated area towards the top of the box.
Click Next.

Flavor Compatibility

Please choose a flavor compatible with the selected image size and resource requirements.

On the Networks screen, find the network you created earlier and click the arrow to the right of its description. Like the previous screen, you’ll see it move up into the Allocated area towards the top of the box.
Click Next.
Click Next again to skip the Network Ports screen and proceed to Security Groups

On the Security Groups screen, select the one or more of the security groups you created earlier and click the arrow to the right of its description. Like the previous screen, you’ll see it move up into the Allocated area towards the top of the box.
Click Next.

On the Key Pair screen, if the key pair you created earlier is NOT in the Allocated section, click the arrow to the right of its description. Like the previous screen, you’ll see it move up into the Allocated area towards the top of the box.
At this point you can click Launch Instance to deploy your instance.

Your instance should now show up in your instances list.
Once it has entered the running state, click the Action dropdown at the far right and select Associate Floating IP

If you have previously allocated an IP address, you’ll see it in the IP Address list.
If you do not, click the + sign to allocate a new IP address from the Public pool

Note your new IP address and make sure it’s the one you want to associate with the instance
Note that the correct instance is selected under Port to be associated
If all is well, click Associate

Please note that sometimes it takes a few seconds for the association to become active, depending on system load.
Though this is normally quick, you can try pinging your new host from a remote machine: ping -c 5 ip_address

If you chose a CentOS-based instance, your default user is centos
If you chose an Ubuntu-based instance, your default user is ubuntu
Access your new host with ssh from a remote machine
- Example from a terminal-based ssh-client as on Linux or a Mac:
  ssh centos@your_ip_number or
  ssh ubuntu@your_ip_number
Note that the first time you connect you’ll get a request to verify that you’re getting a new host key and making sure you want to connect