Page History

...

At the end of the project validity, the “User Admins” will receive communication from CINECA staff that the project as expired with the date by when the resources will be removed. It is “User Admins” responsibility to make copy of the necessary VMs or data before that date.

Access

Log in to the OpenStack dashboard

Go to the OpenStack dashboard at https://adacloud.hpc.cineca.it, select "CINECA HPC" as Authentication method, then insert your HPC-CINECA credentials to log in, together with the 2nd factor for authentication.

After the log in, on the top-right of the window is displayed your user name, while on the top-left. are listed in a menu all the Projects you are associated with.

Image Removed

Projects are organizational units in the cloud. Each user is a member of one or more projects. Within a Project, a user can create and manage instances, security groups, volumes, images, and more.

From the Project tab, you can view and manage the resources assigned in a particular project, including instances, images and volumes. Moreover you can select a period of interest and have the usage summary.

You can select one of the project you are associated with the menu on the top-left side of the window.

Log in to the virtual machine

After you have created your virtual machine ( see the following section) you can log in directly using:

- the default user and key ( if you have used a native default image for cloud)

- another username (if you have used your personal image with a custom user defined in it)

Suppose you have used the default Ubuntu cloud image, you can login as:

$ ssh -i MyKey.pem ubuntu@<floating IP address>

Creation of an instance of the virtual machine in your Project

In order to create your own virtual machine you have to perform all the following eight steps

Log in to the dashboard https://adacloud.hpc.cineca.it as described in the Access section.

Check and configure the Internal Network in the Project

In order to build and use virtual machine within a specific Project, it is mandatory the presence of the internal network, subnet and router.

Select the Project of interest and check the presence of such components click on tab Project → Network → Network Topology.

If it is present only the "external network", you must create network, subnet and router. Please, follow the instruction below:

Create a private network and subnet.

Click on: Project -> Network -> Network Topology -> Create Network.

Then set:

Tab Network:

Network name: <the name you want>

Enable Admin State: check

Create Subnet: check

Availability Zone Hints: set "nova"

MTU:set it blank. The default is 1450

Tab subnet:

Subnet name: <the name you want>

Network Address (eg. 192.168.0.0/24)

IP Version (IPv4)

Gateway IP (eg, the last address 192.168.0.254 for subnet 192.168.0.0/24)

Disable Gateway: disabled, uncheck

Tab Subnet Details:

Enable DHCP: enabled, check

Allocation Pools: leave blank

Host Routers: leave blank

Finally, click on "create"

Create a private router and set the gateway.

Click on: Project -> Network -> Routers -> Create Router.

Then set:

Router name: <the name you want>

Enable Admin State: check

External Network: select "externalNetwork"

Availability Zone Hints: leave "nova"

Finally, click on "create router".

Now, select the router just created and click on "Interfaces" and then on "Add interface"

subnet: select the subnet just created

IP address (write THE SAME IP ADDRESS of the gateway, in this example, it is 192.168.0.254)

Finally, click on "Submit".

...

Set up a keypairs

Keypairs are used to access virtual machines when:

the instance is launched using a default image for cloud (e.g. centos or ubuntu)
in the virtual machine is set a login with ssh -key

You can set up a keypair in two ways. From "Project → Compute → Key Pairs" menu, you can:

click on "Create Key Pair", to obtain a new key pair. The possible types are SSH key or x509.
click on "import Public Key" to import your key pair.

Quotas, Flavors and Images

Quotas

Each project is assigned a quota that defines the resources it can use.

When resource consuming operations such as virtual machine creation are performed, the request is validated against the maximum quota permitted for the current project (as set by the environment variables or Horizon dashboard).

The default project quota is:

Compute	Limit	Volume	Limit
Instances	10	Volume Storage	10
VCPUs	4	Volume Snapshots	10
RAM (GB)	30	Volume Storage (GB)	512

Network	Limit
Floating IPs	1
Security Groups	10
Security Group Rules	20
Networks	2
Ports	50
Routers	2

Flavours

A flavor defines the virtual machine size such as

Number of VCPUs
Amount of memory
Disk space (system disk, ephemeral disk, and swap)

A standard set of flavors allows predictable distribution of applications across multiple hypervisors.

Flavour Name	VCPUs	RAM GB	Disk GB	Public-available for all projects
fl.ada.xxs	1	7,5	10	yes
fl.ada.xs	2	15	30	yes
fl.ada.s	4	30	30	yes
fl.ada.m	8	60	30	yes
fl.ada.l	16	120	30	yes
fl.ada.xl	24	180	30	On-demand
fl.ada.xxl	48	360	30	On-demand
fl.ada.full	96	720	30	On-demand

Images

OpenStack images provide the source for booting a virtual machine. An image consists of an operating system, some optional additional packages and some flags to help OpenStack place these on the right hypervisor.

For more detailed information about OpenStack's image management, the OpenStack image creation documentation provides further references and links.

The complete list of provided images is available by click on the tab "Images" and then on "Public" tab on the right in the Openstack Dashbord.

In what follow there is the list of the default images provided for all projects.

IMPORTANT NOTE: It is not admitted building Windows virtual machine on ADA cloud, even if the user has its own windows licence.

Image Name	Image information	Default user	Password
CentOS-7-x86_64-GenericCloud-2009	CentOS-7-x86_64-GenericCloud-2009.qcow2, last modified 2020-11-12 Source: http://cloud.centos.org/centos/7/images/	centos	ssh access by key
CentOS-8-GenericCloud-8.4.2105-20210603.0.x86_64	CentOS-8-GenericCloud-8.4.2105-20210603.0.x86_64, last modified 2021-06-03 Source: https://cloud.centos.org/centos/8/	centos	ssh access by key
Ubuntu 18.04 LTS (Bionic Beaver)	Ubuntu server 18.04 (Bionic Beaver) LTS for cloud Source: https://cloud-images.ubuntu.com/	ubuntu	ssh access by key
Ubuntu Server 20.04 LTS (Focal Fossa)	focal-server-cloudimg-amd64.img, last modified 2021-07-20 Source: https://cloud-images.ubuntu.com/	ubuntu	ssh access by key
Ubuntu Server 21.04 (Hirsute Hippo)	hirsute-server-cloudimg-amd64.img, last modified 2021-07-20 Source: https://cloud-images.ubuntu.com/	ubuntu	ssh access by key

Access

Log in to the OpenStack dashboard

Go to the OpenStack dashboard at https://adacloud.hpc.cineca.it, select "CINECA HPC" as Authentication method, then insert your HPC-CINECA credentials to log in, together with the 2nd factor for authentication.

After the log in, on the top-right of the window is displayed your user name, while on the top-left. are listed in a menu all the Projects you are associated with.

Image Added

Projects are organizational units in the cloud. Each user is a member of one or more projects. Within a Project, a user can create and manage instances, security groups, volumes, images, and more.

From the Project tab, you can view and manage the resources assigned in a particular project, including instances, images and volumes. Moreover you can select a period of interest and have the usage summary.

You can select one of the project you are associated with the menu on the top-left side of the window.

Log in to the virtual machine

After you have created your virtual machine ( see the following section) you can log in directly using:

- the default user and key ( if you have used a native default image for cloud)

- another username (if you have used your personal image with a custom user defined in it)

Suppose you have used the default Ubuntu cloud image, you can login as:

$ ssh -i MyKey.pem ubuntu@<floating IP address>

Creation of an instance of the virtual machine in your Project

In order to create your own virtual machine you have to perform all the following eight steps

Log in to the dashboard https://adacloud.hpc.cineca.it as described in the Access section.
Check and configure the Internal Network in the Project
In order to build and use virtual machine within a specific Project, it is mandatory the presence of the internal network, subnet and router.
Select the Project of interest and check the presence of such components click on tab Project → Network → Network Topology.
If it is present only the "external network", you must create network, subnet and router. Please, follow the instruction below:
- Create a private network and subnet.
Click on: Project -> Network -> Network Topology -> Create Network.
Then set:
- Tab Network:
Network name: <the name you want>
Enable Admin State: check
Create Subnet: check
Availability Zone Hints: set "nova"
MTU:set it blank. The default is 1450
- Tab subnet:
Subnet name: <the name you want>
Network Address (eg. 192.168.0.0/24)
IP Version (IPv4)
Gateway IP (eg, the last address 192.168.0.254 for subnet 192.168.0.0/24)
Disable Gateway: disabled, uncheck
- Tab Subnet Details:
Enable DHCP: enabled, check
Allocation Pools: leave blank
Host Routers: leave blank
Finally, click on "create"
- Create a private router and set the gateway.
Click on: Project -> Network -> Routers -> Create Router.
Then set:
Router name: <the name you want>
Enable Admin State: check
External Network: select "externalNetwork"
Availability Zone Hints: leave "nova"
Finally, click on "create router".
Now, select the router just created and click on "Interfaces" and then on "Add interface"
subnet: select the subnet just created
IP address (write THE SAME IP ADDRESS of the gateway, in this example, it is 192.168.0.254)
Finally, click on "Submit".
Verify that the Status of router is “ACTIVE” and the Admin state is “UP”.
Set up a keypairs
Keypairs are used to access virtual machines when:
1. the instance is launched using a default image for cloud (e.g. centos or ubuntu)
2. in the virtual machine is set a login with ssh -key
You can set up a keypair in two ways. From "Project → Compute → Key Pairs" menu, you can:
- click on "Create Key Pair", to obtain a new key pair. The possible types are SSH key or x509.
- click on "import Public Key" to import your key pair.
Remember to modify the permission of the key file to 600 in order to avoid errors when you use it to login to your virtual machine.
Set the security rules, that will be the firewall of your virtual machine
The firewall of the virtual machine must be defined using the OpenStack Security Groups and Security Rules.
Inside the virtual machine, the firewall must be disabled.
A security rule defines which traffic is allowed to instances assigned to the security group.
A security group is a group of security rules that can be assigned to an instance.
The security groups and security rules can be created click on "Project → Network → Security Groups ".
Common default rules are:
- SSH (port 22)
- ICMP (allow to "ping" a server)
- HTTP (port 80)
- HTTPS (port 443)
Note: It is always possible to modify, add and remove security groups in a virtual machine after its creation.
- If you modify a security group, adding or removing rules, and the security group is already associated to the virtual machine, the changes will be available in real time
- If you want to add or remove a security group from a virtual machine, click on "Project → Compute → Instances", select the virtual machine and from the menu on the right, click on "Edit Security Group". So, add or remove the security groups to the instance.
Launch an instance of Linux virtual machine
Once your key pair and your security group are defined, proceed building the virtual machine.
- Click on "Project → Compute → Instances"
- Click on "Launch instance" button
- In the "Details" box, enter:
  - the instance name
  - the instance number (count)
- In the "Source" box, enter:
  - the boot source for the instance. It can be an image, a bootable volume or a bootable volume snapshot.
    - Images: we provide some default images (centos, ubuntu, etc.). For these default images, it is set a default user can login into the virtual machine using a key pair. Such a user can execute commands as root. The password of the user root is embedded. If you want to use your personal image, you can create it in the cloud environment click on "Project → Compute → Images", the "Create Image" and upload it.
    - Note If you want to create a bootable volume from your instance, select "yes" in "Create New Volume" and select the size of such volume.
- In the "Flavor" box, select the flavor you want to use, accordingly with the resources you have.
  - - NB: if you select to create a volume from your instance, the root disc of the virtual machine will have the size of the volume, not the size set in the flavor
- In the "Networks" box, enter the network internal to your project on which connect the virtual machine
- In the "Security Groups" box, select the security groups you want. Remember that you can always modify them after the virtual machine creation.
- In the "Key Pair" box, select the key pair you want to use for ssh login.
Follow the boot process
The boot process can be followed on the instances screen. Once the VM is in state ACTIVE, you will be able to open the console and follow the boot process.
To follow the installation, you can access the graphical console using the browser once the VM is in BUILD state.
The console is accessed by selecting the "Instance Details" for the machine and then click on the tab "Console".
Associate a Floating IP (FIP) to the virtual machine
Where floating IPs are configured in a deployment, each project will have a limited number of floating IPs controlled by a quota. However these need to be allocated to the project from the central pool prior to their use.

To allocate a floating IP to a project, click on "Project → Network → Floating IPs", then click on the button "Allocate IP to project" on the right side of the dashboard page. Once allocated, a floating IP can be associated with running istances. Just click on "Associate" action on the right of the page. In the popup, select your virtual machine by the menu in "Port to be associated".
The inverse action, Dissociate Floating IP, is available from the "Instances" page.
Login to the virtual machine using ssh
After the association of a Floating IP to your virtual machine, you can login using the default user and key ( if you have used a native default image for cloud), or using another username (if you have used your personal image with a custom user defined in it). Suppose you have used the default ubuntu cloud image, you can login as:
```
$ ssh -i MyKey.pem ubuntu@<floating IP address> 
```

...

Set the security rules, that will be the firewall of your virtual machine

The firewall of the virtual machine must be defined using the OpenStack Security Groups and Security Rules.

Inside the virtual machine, the firewall must be disabled.

A security rule defines which traffic is allowed to instances assigned to the security group.

A security group is a group of security rules that can be assigned to an instance.

The security groups and security rules can be created click on "Project → Network → Security Groups ".

Common default rules are:

SSH (port 22)
ICMP (allow to "ping" a server)
HTTP (port 80)
HTTPS (port 443)

Note: It is always possible to modify, add and remove security groups in a virtual machine after its creation.

...

Launch an instance of Linux virtual machine

Once your key pair and your security group are defined, proceed building the virtual machine.

Click on "Project → Compute → Instances"
Click on "Launch instance" button
In the "Details" box, enter:
- the instance name
- the instance number (count)
In the "Source" box, enter:
- the boot source for the instance. It can be an image, a bootable volume or a bootable volume snapshot.
  - Images: we provide some default images (centos, ubuntu, etc.). For these default images, it is set a default user can login into the virtual machine using a key pair. Such a user can execute commands as root. The password of the user root is embedded. If you want to use your personal image, you can create it in the cloud environment click on "Project → Compute → Images", the "Create Image" and upload it.
  - Note If you want to create a bootable volume from your instance, select "yes" in "Create New Volume" and select the size of such volume.
In the "Flavor" box, select the flavor you want to use, accordingly with the resources you have.
- - NB: if you select to create a volume from your instance, the root disc of the virtual machine will have the size of the volume, not the size set in the flavor
In the "Networks" box, enter the network internal to your project on which connect the virtual machine
In the "Security Groups" box, select the security groups you want. Remember that you can always modify them after the virtual machine creation.
In the "Key Pair" box, select the key pair you want to use for ssh login.

Follow the boot process

The boot process can be followed on the instances screen. Once the VM is in state ACTIVE, you will be able to open the console and follow the boot process.

To follow the installation, you can access the graphical console using the browser once the VM is in BUILD state.

The console is accessed by selecting the "Instance Details" for the machine and then click on the tab "Console".

Associate a Floating IP (FIP) to the virtual machine

...

Login to the virtual machine using ssh

After the association of a Floating IP to your virtual machine, you can login using the default user and key ( if you have used a native default image for cloud), or using another username (if you have used your personal image with a custom user defined in it). Suppose you have used the default ubuntu cloud image, you can login as:

$ ssh -i MyKey.pem ubuntu@<floating IP address>