Launching a basic Linux instance with a public IP using the dashboard
This howto will show you how to launch a basic Linux instance with a public IP. It is probably the option requiring the least amount of work to quickly get an instance up and running.
We assume you have already uploaded a public ssh key. If you haven't done so, see our guide on managing key pairs.
First, click on the "Instances" menu item in the dashboard menu, then on the button. The mandatory steps are marked with asterisks. We will go through the steps in order.
In this step you can fill out a name for your instance. The count field indicates how many instances with the same settings you wish to launch. Leave the setting at 1 to launch a single instance.
Select Image as the boot source, then choose e.g. "Ubuntu 16.04 (xenial)" as the image to boot. Setting "Delete Volume on Instance Delete" to Yes makes sure the volume is automatically deleted when you delete the instance. The volume size setting determines the size of your root volume. Here we've set it to 10 GB. Be aware that certain images might have a higher requirement on disk space.
Choose an instance flavor. The Flavor determines how powerful your instance is going to be. Here we've chosen a g1.small flavor with 1 VCPU and 4 GB of RAM.
Here you can choose to put the instance on the public network. Choosing the public network ensures the instance is automatically assigned a public IP. Be aware, though, that running all your instances on a public network exposes them to higher risk. For production systems it is therefore recommended to run only the services that need to be accessed from the Internet on a public network.
Here you can choose the public key you've previously uploaded or generated using the dashboard.
Launching the instance
You are now ready to launch the instance. Click the button. After clicking the button OpenStack will copy the chosen operating system image to your volume and spawn your instance. When the status has changed from Build to Running then the instance is ready.
Modifying the default security group to allow SSH login
Since we didn't do the Security Groups step your instance will be placed in the default security group. A security group is sort of like a firewall where you can define rules
for which traffic to allow to or from the instance. Note that you will
have to explicitly allow ingress traffic on port 22 to be able to ssh in
to your instance.
Click on the "Security Groups" menu item under the Network sub menu, then on the button for the default security group. You will see a list of the security rules. We will need to add a rule to allow incoming traffic on TCP port 22, which is the standard SSH port. Click on the button and fill out the form. Enter the network address to allow SSH from in CIDR notation. Here we've opted to allow SSH from any IP address.
Logging in to your instance
You should now be able to log in to your instance using ssh.
Note that the username you log in to depends on the image you've chosen. If you're using one of the images provided by us the username is the same as the operating system in lower case letters. In this guide we've chosen an Ubuntu image. The username is therefore ubuntu. For Debian the username is debian. And so on.