Aurora setup for ATLAS

Thursday 1 Sep 2016, 10:00 → 11:10 Europe/Stockholm

Skype

1 September 2016, 10:00 - 10:45

Present: Florido, Torsten, Caterina, Jonas, Oxana

* The agreement document is reviewed and corrected by Jonas, who welcomes everybody to check and comment. Caterina already provided some comments. There is a general feeling that it should be simplified and made easier to read. Florido proposes to re-arrange it into 3 sections: 1) ATLAS use cases, prioritized; 2) roles and tasks; 3) response times.

* Jonas studied STORM, which appears to have a simple installation procedure and offers locally mountable storage, according to the documentation. It can be used for local transfers from LUND_LOCALGROUPDISK dCache pool to Aurora, or perhaps even a new ATLAS Tier3 can be set up in Lund (Oxana thinks the latter will take more time, and will need a permanent support staff). A simpler alternative is to follow example of many other sites and synchronise files from the dCache pool to Aurora by custom-made scripts. Another option is to access the files on the dCache pool via xrootd directly, needs to be tested. Florido will look into STORM.

* OS incompatibility issues: Florido had no time to test Singularity yet. Jonas contacted HPC2N experts, who explained that they simply copy the entire SL5 and SL6 file trees onto their Ubuntu, and created a complex system of modules. This is not seen as a simple arrangement to maintain, and Singularity offers a similar but more elegant approach, thus it is preferred by both Jonas and Florido.

* Caterina got instructions from Edgar, will try to run it herself first, before forwarding to Florido.


Action points:
* Everybody check the agreement document
* Florido studies STORM
* Florido and Jonas test Singularity
* Caterina forwards Edgar's instructions to Florido

10:00 → 10:10 Responsibilities and duties

10:10 → 10:25 New software packages (MC)

10:25 → 10:40 CentOS7 compatibility

10:40 → 11:00 Storage solution