This page teaches how to create a
Virtual Machine (VM) running Linux, by importing an appliance from the
Apps option of the
This walk-through guide provides an introduction to the concepts of the HPC Cloud. If you are going to use a VM running Linux for your research, the steps described in this guide will produce a basic VM that you can use to install the software that you may need and where to process your data later on. If your goal is to use a VM running Windows, this chapter still gives you a good introduction and you are recommended to start here.
More advanced and specialized topics are discussed separately.
If you are not yet acquainted with terms such us
image, please visit the introduction to the HPC Cloud documentation page
You use the HPC Cloud interface to build
You build them by first describing all their parts. This description is called a
template. You instantiate a template to make a VM out of it.
Storage drives (like hard disks) are
images. They do not physically exist, but rather, they only exist as files in a backing file server.
To make starting a virtual machine easier, we provide the Apps option, which has appliances readily available for you to pick and use.
The HPC Cloud User Interface (UI) is the web site where you manage your VMs.
You can reach the UI at the following URL: https://ui.hpccloud.surfsara.nl
After you are granted access to the HPC Cloud, you will receive a username and a password for this UI.
If you would like an explanation about the options you can see on the UI, please visit the User Interface documentation page.
To start building a virtual machine, go to the UI and log in with the username and password you received.
… that the username and password are not for the VM you are going to create. You can set users and passwords later on, once you have created a VM.
We are going to work with a pre-made
image that is available in the
Appsoption contains a collection of so-called appliances maintained by the HPC Cloud team. It is a handy way to import, from within the UI, useful images that are ready to use. More information about the appliances configuration is available. There is also an OpenNebula marketplace, publicly available on the OpenNebula website, and anybody can contribute their appliances to it.
Import the appliance by following these steps:
From the user
view, choose the
Storage tab on the left menu of the screen and then Apps (in the screen shot, it has been highlighted in red).
Look for the Ubuntu 16.04 Server appliance in the list and click on it.
This will show details about
template and other attributes (including a textual description) that conform the appliance. Please, read the
The description mentions the user account you will need to use when logging in (through ssh). We will do this in a later step.
Read the extended information related to the partition size. You will have the option to resize the OS image when instantiating the template, do not pick a size smaller than the mentioned partition size (though leaving it at the default setting works).
Click on the OpenNebula button at the top of the screen. A dialogue will pop up, asking you for a few details.
The first options are the name of the
image and the
template. You can change the names to something more descriptive to you. Once you have many
template objects, it will pay off to have good descriptive names of what each of them is.
The next setting is the datastore for images. Make sure that you select local images ssd.
Finally, click Download. This will start importing the appliance from the AppMarket. When the import is successful, it will create an
image and a
You can verify that the process is complete by inspecting the VMs sections in the Templates tab and the Images section in the Storage tab of the UI. You should see your new
If you remember from the description of the virtual machine, there is no password for the root user. You have to add an SSH key to your user profile in order to be able to log in as root in your VM.
First, you need to create an SSH key in your own computer. This process is described in a different article. This SSH key enables you to log in to your virtual machine with
After you have created an SSH key, go to your user profile by selecting the buddy icon on the top-right of the screen, then select Settings. A dialogue pops up. In the dialogue, go to the Info page; then locate the section Public SSH Key, and click on the blue edit icon. You should now see an empty text area.
Find the file in your computer containing the public key you created (it is usually called
id_rsa.pub and it is usually found in the
.ssh directory in your
$HOMEdirectory). Open the file, then copy the contents of the file (its contents are your public key) and paste it into the text area of the UI.
You can just close this dialogue now. Your public key is automatically stored in your profile.
When you import an appliance from the Apps option, the disk image is normally non-persistent. This means, in short, that your changes are lost when you shut your VM down. Before starting your VM, always check whether Image Persistence is set to the desired mode (yes or no).
template is a description of a virtual machine. The
template we have been editing in this guide is now ready to create a virtual machine from it.
Go to the VMs option of the Instances section of the UI. This displays an overview of all running VMs. If this is your first virtual machine, this list will be empty.
Start your virtual machine using the following steps:
template you created before from the presented list. This opens a dialogue with options where you will define the resources to be allocated to VM.
The first box in the dialogue is to give your virtual machine a name. Ideally, give your VM a name consisting only of lowercase letters, hyphens (‘-‘) and digits, but no other characters or spaces. Virtual machine names will be truncated in DNS to 32 characters. So use names no longer than 32 characters.
The number of instances is 1, which is fine for now.
Click on the Create button at the top of the screen.
Your VM will appear in the list of virtual machines. At first, it will have the state PENDING. That state means that the cloud system is looking for a place where your virtual machine can actually run.
When the required capacity becomes available, your virtual machine will go through a few other states, and eventually, it will appear as RUNNING. Refresh the VM status by clicking on the two arrows chasing each other next to “+” button.
The operating system on the machine will go through the boot process.
After you have added your public key to your user profile, you should be able to log in on your virtual machine as user ubuntu, allowing you to perform maintenance tasks on your virtual machine by using
You will need to find the IP address of your virtual machine, first. The IP address of your virtual machine is shown on in the IPs column from the virtual machines list, under the Virtual Resources tab of the UI.
If you use Linux or Mac OSX open a terminal (if you are using Windows then open a GitBash terminal) and type:
where you should replace mmm and nnn to match the IP address of your virtual machine.
Note: In this case ‘ubuntu’ is the username but it could be a different one, e.g. ‘admincentos’ for VMs created from Centos Apps images. This is mentioned in the App description.
Note: You may have to specify which of your (multiple) public keys you want to use to connect to your VM. The
sshcommand can take an argument of the following form for that:
In the screen shot below, the IP address is 220.127.116.11. And suppose the public key we want to use from our laptop is ~/.ssh/id_rsa.pub. Then, the correct command in this case would be:
ssh -i ~/.ssh/id_rsa firstname.lastname@example.org
Note for Windows:
If you are using Putty, then use the IP of your virtual machine as host, ubuntu as username, and click Connect (see instructions here).
If there were no errors, and if your firewalls allow making remote connections, you should now be logged in on your virtual machine, as user ubuntu.
Note: Operating as user root
Many tasks in Linux require your becoming user root. The recommended way of operating as root in Ubuntu is to run your commands prefixed by
sudo. For example, to install a common text editor, you would run:
sudo apt-get install vim.
However, if what you would like is to become root in a terminal so that you do not have to bother with the
sudoprefix, then you can do that like this:
sudo su -. From then on, everything you run in that terminal will take place as the root user.
If you want to terminate your VM and stop consuming your quotas, perform the following steps:
Tick the box to the left on the row of your VM and click Terminate (upper right corner of the screen, under the dust bin drop-down button).
Refresh the Virtual Machines list (by clicking on the two arrows chasing each other next to + button) until your VM is gone.
That was the shutdown. Once the operation is finished, your VM will be removed from the display and its resources freed. You can start a new VM from your existing
image any time.