D4Science Infrastructure

I managed to fix the gluster file system explicitly starting again the volumes. After that, the VMs did not start correctly. As I was in a rush, I rebuild from scratch the most important VMs.
Then, today, I investigated what's happened: there's a bug in the cloud-init service, that resets the interface configuration to DHCP. As we do not have a password to access from the console, the only way to fix the problem is to cold mount the VM disks and fix both the network configuration and cloud-init.

Now all the VMs are operative again. I wrote all the troubleshooting steps needed to restart glusgter, here: https://support.d4science.org/projects/aginfraplut/wiki/Gluster_management and the ones needed to fix the VMs here: https://support.d4science.org/projects/aginfraplut/wiki/Virtual_Machines_Management

I still have to add a task to the base playbook to fix the cloud-init behaviour on the newly created VMs.