Page History

This page is for all the users that already have assigned CINECA HPC cloud resources (reachable at the url https://cloud.hpc.cineca.it ) and

expressed their willingness to migrate to the new ADA cloud CINECA HPC infrastructure. 

The new ADA cloud CINECA HPC infrastructure is based on OpenStack Wallaby version, and the Horizon dashboard is reachable at the url https://adacloud.hpc.cineca.it . 

All the migrated projects will have a new name, and you will receive an email when your new migrated project will be created into the UserDB portal https://userdb.hpc.cineca.it .

By login into the UserDB portal, you will find your new project listed among your projects.

Afted one day from the notification email, you will be able to login into the OpenStack dashboard  https://adacloud.hpc.cineca.it e start the setup of the cloud environment. 

Please, note that:

...

Migration of the OpenStack objects: virtual machines (VM), cinder volumes and images. 

All the OpenStack objects will be transferred as cinder volumes:

...

are not used to manage linux environment.

Add/delete a user in your virtual machine

In order to add the user and set his/her password  use following commands

sudo /usr/sbin/adduser <username> 

sudo chage -d 0 <username>

After you need to modify the file /etc/ssh/sshd_config, enabling the PasswordAuthentication and then restart and check the SSH deamon:

Ubuntu: 

sudo systemctl restart sshd.service

sudo systemctl status sshd.service

CentOS:

sudo systemctl restart sshd.service

sudo systemctl status sshd.service

In order to delete a user and his/her HOME directory just execute the command:

deluser --remove-home <username>

Grant a user root privileges in your virtual machine

• It is possible to grant a user with root privileges using O the command adduser instead of useradd when the new user is created: 

  sudo /urs/sbin/adduser <username> sudo

  Otherwise you can add the following line in the section #User privilege specification of  the file /etc/sudoers:

• <username> ALL=(ALL:ALL) ALL

How to mount remote filesystem with FUSE (Filesystem in USEr space) on CentOS or Ubuntu

• On CentOS:  - You will need to install a few packages that are not available in the standard CentOS repository. So, you must enable the EPEL repo:

  yum install epel-release -y 

  - Install FUSE (Filesystem in USEr space) and SSHFS packages 

  yum install fuse sshfs
  - Load the FUSE module

  modprobe fuse

  - Confirm that the FUSE module is loaded 

  lsmod | grep fuse
  fuse                  84368    2

• 
  - Optionally, make sure the FUSE module is loaded upon a reboot 

  echo "modprobe fuse" >> /etc/rc.local 

• - Using SSHFS. Once the FUSE module is loaded, you can mount your remote partition using SSHFS:

  sshfs user@remote_host:/remote_directory  /local_mount_partition

  If you have configured the login via ssh key authorization, you can use the following command:

  sshfs user@remote_host:/remote_directory  /local_mount_partition -o IdentityFile=<absolute-path-with-key>

  
  

  Note: If appear the following error 

  fuse: bad mount point `/local_mount_partition': Transport endpoint is not connected

  execute:      sudo fusermount -u /local_mount_partition

On Ubuntu:  - First you have to install FUSE and SSHFS packages with the apt-get comand:

apt-get install fuse 

apt-get install sshfs

Once the FUSE module is loaded, you can mount your remote partition using SSHFS:

sshfs user@remote_host:/remote_directory  /local_mount_partition

If you have configured the login via ssh key authorization, you can use the following command:

sshfs user@remote_host:/remote_directory  /local_mount_partition -o IdentityFile=<absolute-path-with-key>

Note: If appear the following error 

fuse: bad mount point `/local_mount_partition': Transport endpoint is not connected

execute :  sudo fusermount -u /local_mount_partition

How to use and configure Docker in your virtual machine

To use Docker in your virtual machine please set the MTU value at 1400 in the file  /etc/docker/daemon.json.  More in particular edit the file /etc/docker/daemon.json and then set

• • • {

      "mtu" : 1400

      }

...

For each project, all the objects that you want migrate, listed in the email that you wrote us in June, will be hot-mirrored, so that no long downtime will occurred.

In other terms, we will activate the mirroring of VM and volumes while they are up&running in the old infrastructure. 

At the end of  the mirroring phase, we will ask you to shut down your VMs and detach the volumes in order to finalize the mirroring. 

To shut down your VMs in a secure way, please:

• login into your VM
• stop the users services (if present)
• umount external volume (both cinder volume and or volumes exported via NFS or FUSE)
• check the /etc/fstab file: if it is set the automatic mount of the external volumes, please comment such lines. Take care to not comment the mount of the root disk.
• shut down the VM.  The VM must be shutoffed during the final phase of the migration process.

At the end of the migration, for each VM, volume and image, you will receive an email  with

• the name of the object (VM, volume or image)
• a "transfer id" 
• a "authorization key"

For each object, please, select the project on which such object has to be stored,

Click on "Project → Volumes → Volumes" and then click on the button "Accept Transfer" on the right of the page. Insert the "transfer id" and "transfer key" provided in the email.

At the end of the transfer, you will have everything listed in the "Volumes" page.

Restart the VM just transferred

To restart a just transferred VM in the new infrastructure, select the corresponding volume, click on "Edit" button at the right side of the page and check "Bootable".

Starting from this bootable volume you can launch your instance VM.

• Boot source: When you launch the new istance, select "Volume" as boot source, then select the bootable volume just transferred and remember to select "NO" as option of "Delete Volume on Instance Delete".
• Flavor: Choose the flavor amog those defined on ADA How to: Quotas, Flavors and Images for each project#Flavors. Take care that the name and quota are different respect to those defined on the old infrastructure. 
• Keypair: since the VM has been migrated, the old way to login is again available. If you want, you can add a new keypair to login in the VM. 
• Associate a new Floating IP: After the creation of the virtual machine, a new floating IP must be associated. If there is an hostname - floating IP association, or a NFS export to reconfigure, please reply to the email in which you asked the migration, and communicate the operation you want and the new floating IP.
Attach external cinder volume: Remember to attach the external volume to the VM, if needed. 

For any questions please write to superc@cineca.it .