Using the web interface

Log in to the dashboard at

As a new user to the Catalyst Cloud your initial cloud project will come with a pre-configured private network and a router connected to the internet. If you have deleted this, or would like to create additional networks then please see Creating the required network elements for details on how to do that.

Otherwise, let’s proceed with building your first instance.

Uploading an SSH key

You can either import an existing public key or have OpenStack create a keypair for you. Here we document how to import the public key from an existing keypair:

Select “Import Key Pair”:


Enter your key pair name and paste your public key into the box:



The dashboard has two options, “Create Key Pair” and “Import Key Pair”. When you select “Create Key Pair”, OpenStack creates a keypair and saves the public key while providing the private key to you to download. When you select “Import Key Pair” the dashboard provides a form where you can upload a public key. This option is somewhat confusingly named as you are importing a public key only and not a keypair; it would be more correctly named “Import Public Key”. See the SSH Key Pairs section of the FAQ for more information.

Configure Instance Security Group

We will add a security group and a rule for our instance so that it can be accessed using SSH.

Navigate to the “Security Groups” tab of the “Access & Security” section and click “Create Security Group”:


Enter a name and description and click “Create Security Group”:


Now click on “Manage Rules” for the group you have created:


Click on “Add Rule”:


Enter 22 for the port number (this is the TCP port the SSH service listens on). You can use the default values for the remainder of the options. Click “Add”:



Note that by using the CIDR as a remote, you are allowing access from any IP to your compute instance on the port and protocol selected. This is often desirable when exposing a web server (eg: allow HTTP and HTTPs access from the Internet), but is insecure when exposing other protocols, such as SSH, Telnet and FTP. We strongly recommend you to limit the exposure of your compute instances and services to IP addresses or subnets that are trusted.

Booting an Instance

We are now ready to launch our first instance. Select launch instance from the instances list:


Enter an instance name, use the default instance count of one. Select “Image” as the boot source and “No” for create new volume. Select ubuntu-14.04-x86_64 from the image list. Then click “Next”:


Select the c1.c1r1 flavor from the list and click “Next”:


Select the private-net network from the list and click “Next”:


Select the first-instance-sg security group from the list and click “Next”:


Select the first-instance-key key pair from the list and click “Launch Instance”:


It will take a few seconds for your instance to build. You will see the Status, Task and Power State change during this process. When complete, the status will be “Active”. You now have a running instance, but there are a few more steps required before you can log in.

Allocate a Floating IP

To associate a Floating IP with your instance you need to navigate to the “Floating IPs” tab of the “Access & Security” section.

If an IP address has not yet been allocated, click on “Allocate IP to Project” to obtain a public IP. Then, select an IP that is not currently mapped and click on “Associate”:


Select the port you wish to be associated with the Floating IP. Ports are equivalent to virtual network interfaces of compute instances, and are named after the compute instance that owns them.

In this example, select the “first-instance” port and click “Associate”:


Connect to the new Instance

You can now connect to the SSH service using the floating public IP that you associated with your instance in the previous step. This address is visible in the Instances list, or under the Floating IPs tab in Access & Security.

$ ssh ubuntu@PUBLIC_IP

You should be able to SSH into, and interact with this instance as you would any Ubuntu server.