CRESCO: System Access
1. Access to frontend nodes via SSH
Computing resources in ENEAGRID are distributed over six ENEA centres: Portici, Frascati, Casaccia, Brindisi, Trisaia and Bologna. In particular, the clusters installed at Portici, Frascati and Casaccia, represent the main computing facilities, while the centres of Trisaia and Bologna host AFS storage resources.
Frontend nodes serve as control servers to launch applications via LSF or SLURM, to edit the user's own launch scripts, to compile codes and - as is the case for dedicated frontends (see below) - to make short test runs. All computing nodes can be reached only via LSF or SLURM. For a short tutorial on the basic commands to submit batch jobs go HERE for LSF or go HERE for SLURM.
The section Batch Jobs / LSF of the present document contains specific information on CRESCO.
The section Batch Jobs / SLURM of the present document contains specific information on CRESCO.
Please find below the list of frontend nodes (the domain suffix ".portici.enea.it" is omitted, e.g. the hostname of the first frontend node of CRESCO4 is cresco4x001.portici.enea.it):
The super-frontend cresco-in.portici.enea.it is a bridge towards physical cluster frontends. This node is a virtual machine without computing resourses. It should not be used as a physical frontend.
Frontend nodes allowing interactive runs are the only ones that users should use to perform (even parallel) test runs. On these nodes we permit test runs consuming even considerable fractions of the node computing resources. Test runs performed on other frontends are killed by system admninistrators without notice. Remind that test runs can be useful to test compilation, optimization, debugging and so forth. Test runs should be always performed before submitting a real job to the LSF scheduler.
Frontend nodes allowing interactive runs have a different memory management, that allows a more intensive use of the node resources with respect to standard frontend nodes. This is the reason why test runs are only permitted on the above-specified frontend nodes..
2. Access via the ENEAGRID web interface FARO
Users can access all clusters via the FARO web interface, by connecting on their browser to the website