WP5 Monthly meeting 19 April 2021

Europe/Paris
Description

Meeting with all partners involved in WP5/ESAP

You are invited to attend a videocon taking place in virtual meeting room:


Join Zoom Meeting
https://astron.zoom.us/j/97308347310?pwd=Q0xCdkQ3R2lESEtQMjcybnpQZXRzZz09

Meeting ID: 973 0834 7310
Password: Will be provided via email*

One tap mobile
+31202410288,,97308347310# Netherlands
+31207940854,,97308347310# Netherlands

    • 11:00 11:03
      1. Roll call 3m

      ASTRON: John Swinbank, Yan Grange

      CERN: -

      CNRS-LAPP: Marie Paturel

      CSIC: Susana Sánchez

      CTAO: Gareth Hughes, Matthias Fuessling

      EGO: -

      FAIR: Raffaele Grosso

      FAU: Jutta Schnabel

      IFAE: -

      INAF: Sara Bertocco, Stefano Russo

      INFN: Marcelo Vilaça

      JIVE: Aard Keimpema, Harro Verkouter

      KIS: -

      Nikhef: Valentin Pestel

      Open University: Hugh Dickinson

      RUG: Maisam M. Dadkan

      SKAO: James Collinson, Rosie Bolton

      UCM: Daniel Nieto, Jose Luis Contreras

      U. Edinburgh: Dave Morris

    • 11:03 11:05
      2. Last meeting minutes 2m

      Minutes of last meeting can be found at the previous meeting.
      Overview of meetings: https://indico.in2p3.fr/category/906/

      No discussion.

    • 11:05 11:20
      3. Announcements, news and general updates 15m

      Provide your information by adding minutes to the sub-contribution. You will need to have an indico account to do this.
      Note: Please also mention in your updates if you are going to or were at an event to talk about ESAP.

      • ASTRON 1m
        • We're hiring! This position will be (at least partly) working on ESCAPE, so please distribute it to your networks.
        • Slides from Nico's 29 March tech talk on ESAP Architecture are now available from IN2P3 GitLab.
        • Interesting discussions at the WP4 Tech Forum:
          • Nico gave a version of the same material on ESAP Architecture.
          • Stelios discussed the current status of ESAP IDA and links to WP4.
          • A lot of discussion about the nature/mission of ESAP, and how it relates to WP4/VO efforts. An important goal for us to write this down in concrete form over the next weeks/months: we need a “touchstone” that everybody can refer to, rather than just swirling discussion.
        • Good results from the WP2-WP5 workshop, which Yan will talk about below.
          • In particular, be aware of the DAC21 effort, and volunteer to join the task force which Yan will tell you about in a moment(!)
        • ASTRON GitLab down for security update this morning (sorry Gareth!)
      • CERN 1m
      • CNRS-LAPP 1m
        • Quite a few problems last month
        • Switching from a demo version of the deployment (minikube) to a more classic version (kubeadm)
        • Works on private servers, passage on the LAPP machines planned this week
      • CSIC 1m

        In the last month, we presented our use case in the WP2+WP5 meeting on the 6th April. We also attended to the ESCAPE ESAP overview tech talk.  One of our group members  is leaving, so we are re-arranging the tasks within the group.

      • CTAO 1m

        WP2-5 Meeting use cases presented.

        Some work on DIRAC branch (astron git down?)
        esap-api-dirac / dev-dirac

        Development Guide with Nico:
        https://git.astron.nl/astron-sdc/esap-api-gateway/-/wikis/running-in-local-development

         

      • EGO 1m
      • FAIR 1m

        Working together with RUG to integrate several Jupyter notebooks (CbmRoot one in our case) in a single Jupyterhub.

      • FAU 1m
        • WP3+WP5 coordination
          • next common call: Friday, 23rd April, 15:00 CEST (indico, zoom)
          • for issues to the agenda, please sent an email to jutta.schnabel@fau.de
            • currently: update on common projects (and tracking)
          • on metadata see specific point below
      • IFAE 1m
      • INAF 1m
      • JIVE 1m
      • KIS 1m
      • Nikhef 1m
      • RUG 1m
        • The Rucio client is working in our use-case to interact with CERN data lake.
        • We are working together with GSI/FAIR to integrate our Jupyter notebooks use cases in a single Jupyterhub.
      • SKAO 1m
      • UCM 1m

        We have still not started the integration of our use case in ESAP, but are studying the use case.

        D. Nieto which was the only person hired by the project is on tenure track right now, but he will continue collaborating with the project.

        We are also hiring, we have publicized a postdoc position that starts in October-November. We have a found good candidate who is interested and has accepted it.

         

      • UEDIN 1m
    • 11:20 11:30
      4. Metadata Task Force 10m
      Orateur: Jutta Schnabel (FAU Erlangen (ECAP))
    • 11:30 11:40
      5. JupyterHub/IDA WG update 10m
      Orateur: John Swinbank (ASTRON)
      • Resumed (modified) IDA WG meetings.
      • Goal is to move rapidly towards a concrete architecture for ESAP/Jupyter integration.
      • Meeting at 16:00 Amsterdam on Mondays; all welcome.
      • But note that this is intended to be a working group, with technical deliverables!
        • If you show up, you will probably get assigned action items.
        • If you are hoping to integrate your Jupyter system with ESAP at some point in the future, but aren't interested in defining and the interface and working on the code to make that happen, then probably best to hang back for a while — we'll let you know when we have code you can try out.
    • 11:40 11:50
      6. WP2-WP5 workshop summary 10m
      Orateur: Yan Grange (ASTRON, the Netherlands Institute for Radio Astronomy)
    • 11:50 11:55
      8. Round table 5m
    • 11:55 12:05
      9. Next meeting - Monday 17 May at 11:00 CEST 10m

      Also WP3+WP5 coordination meeting, 23 April, 15:00 CEST, https://indico.in2p3.fr/event/24035/

      Next tech talk currently scheduled for 7 June (Edinburgh); please contact John if you would like to speak before then.

      Hugh Dickonson's previous tech talk on Integrating ESAP wiht Zooniverse. Note that you'll need our regular meeting password (mail John Swinbank if you don't have it).