Creating an instance with a custom sized root disk in Horizon

This doc walks you through using Horizon to create an instance with a custom-sized root disk. This root disk is backed from a volume instead of a pre-defined ephemeral storage component. The con is that it counts against your storage quota. The pros are that it lets you create any size root disk for an instance that you need (limited only by ext4 or xfs filesystem limits) and that actions such as shelving and unshelving happen VERY quickly unless with fixed root disks.

This doc assumes you’ve already logged in to Horizon, set the correct allocation, created ssh keys, security groups/rules, and network infrastructure. If you need instructions for creating those, please refer to https://iujetstream.atlassian.net/wiki/spaces/JWT/pages/44826638/Using+the+OpenStack+Horizon+GUI+Interface

 

Launching an instance - Step 1

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.

 

Launching an instance - Step 2

  • On the Source screen, make sure the "Select Boot Source" option is "Image" – Please note that it may take 30-60 seconds for that option to appear and to fully populate that list as it pulls the entire image catalog listing anew each time!

  • Change “Create New Volume” to Yes

  • The setting for “Delete Volume on Instance Delete” can be set to Yes or No. We recommend “Yes”.

  • Type JS-API-Featured in the "Available" box to find the Jetstream API Featured images. You can also boot one of the images shown in the list if you'd rather do that, but we only guarantee the featured images will work for anyone. 

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

    • NOTE: If 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.

 

Launching an instance - Step 3

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

 

Launching an instance - Step 4

  • 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

 

Launching an instance - Step 5

  • On the Security Groups screen, select the security group 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.

 

Launching an instance - Step 6

  • 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"

 

Add a public IP (floating IP) - Step 1

  • Your instance should now show up in your instances list. 

  • Once it has entered the running state, click the dropdown at the far right and select "Associate Floating IP"

 

Add a public IP (floating IP) - Step 2

  • If you have an IP allocated, you'll see it in the IP Address list. If you do not, click the sign to allocate a new IP address 

 

Add a public IP (floating IP) - Step 3

  • Make sure "Public" is selected under Pool and click Allocate IP



 

Add a public IP (floating IP) - Step 4

  • 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

 

Test the connection

  • Please note that sometimes it takes a few seconds or even a little more for the association to become active.

  • Try pinging your host: ping -c 5 ip_address

 

Try ssh'ing to your instance

  • 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 host with SSH – the example from a terminal-based ssh-client as on Linux or a Mac would be 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