EPOS-ORFEUS CC teleconference

Tuesday 26 Jun 2018, 10:00 → 11:00 Europe/Amsterdam

This is a regular meeting of the EPOS-ORFEUS Competence Centre of the EOSC-hub project. CC webpage: https://confluence.egi.eu/display/EOSC/T8.5+EPOS-ORFEUS Link to connect: https://global.gotomeeting.com/join/730290381

EPOS-ORFEUS CC teleconference, June 26, 2018.

Notes by Gergely Sipos:

User-defined products (Luca):
    - Want to try the Kubernetes setup of EOSC-hub. For this they need access to a pre-configured environment
        * Jupyter notebook provided for the users (Ops-Spy)
        * Run the user code close to data
        * Can the EGI Jupyter service relevant?
        --> Gergely to connect them with Enol
    - How to access data in this environment? (i.e. connect the data staging service)
Data staging (Massimo and Nikos):
    - All server is now in virtual server OR in docker container
    - Not to use EUDAT B2STAGE, use iRODS channels over HTTP endpoints
    - PID prefix is already generated
    - Centrally managed FTS3 instance by CERN and RAL: Gergely forwarded information about this to the CC email list. Please review and comment on it
            * How configurable the central instance would be? E.g. we need to select location and coordinates for endpoints
    - Based on the current knowlede the CC prefers to use their own iROD server for now, and consider moving to a centrally provided service later
What repository to use to store and share code? --> Gergely to check if there is an EOSC(-hub) GitHub or similar repo.
    * alternatively use the AIDA repo?
AAI (Javier):
    - working with the B2ACCESS production service at Juelich. Now paperwork needs to be signed
    - In the development server the user approval workflow was tested. This is not connected with EduGAIN yet - that's a todo
    - Their B2ACCESS config issues a custom token that considers also earth-science standards. The CC is yet to test how such tokens can be accepted/translated for the EOSC-hub services they want to use
Support for motion community (Javier)
    - Extra activity that will look nice in the impact reports
DI4R:
    - Unfortunate clash with the EPOS community meeting.
    - Please record community meetings ASAP here: https://wiki.eosc-hub.eu/display/EOSC/Events (so we can avoid clashes in the future)
Consortium (Gergely):
    - SURFsara is expected to contribute to the compute activities - Luca and Sara to discuss the details
    - Consortium agreement: Gergely to ask timeline for signing
    - Financial reporting of the first 6 month is ongoing. Gergely as WP leader will receive and match the reports with expectations. Will get back to you in case of mismatch