ESAP—Jupyter integration discussion

lundi 31 mai 2021, 16:00 → 17:00 Europe/Paris

Zoom

Escape ZoomRoom is inviting you to a scheduled Zoom meeting.

Meeting ID: 863 5651 9787 (https://astron.zoom.us/j/86356519787)
Passcode: (see e-mail, or ask in Rocket Chat #esap-interactive-analysis)
One tap mobile
+31207940854,,86356519787# Netherlands
+31207946519,,86356519787# Netherlands

Dial by your location
        +31 20 794 0854 Netherlands
        +31 20 794 6519 Netherlands
        +31 20 794 6520 Netherlands
        +31 20 794 7345 Netherlands
        +31 707 006 526 Netherlands
        +31 20 241 0288 Netherlands
Meeting ID: 863 5651 9787
Find your local number: https://astron.zoom.us/u/kbXjhufxPF

Join by SIP
86356519787@zoomcrc.com

Join by H.323
162.255.37.11 (US West)
162.255.36.11 (US East)
115.114.131.7 (India Mumbai)
115.114.115.7 (India Hyderabad)
213.19.144.110 (Amsterdam Netherlands)
213.244.140.110 (Germany)
103.122.166.55 (Australia Sydney)
103.122.167.55 (Australia Melbourne)
149.137.40.110 (Singapore)
64.211.144.160 (Brazil)
69.174.57.160 (Canada Toronto)
65.39.152.160 (Canada Vancouver)
207.226.132.110 (Japan Tokyo)
149.137.24.110 (Japan Osaka)
Meeting ID: 863 5651 9787

Join by Skype for Business
https://astron.zoom.us/skype/86356519787

1 Discussion

esap-queries.pdf

ESAP DB on Demand

• Pierre presented his ideas for an ESAP “managed DB” service (see slides attached).
• This service would provide an alternative and explicit model for managing user data within the context of ESAP. As such, it has the advantage of moving it closer to being a “platform”, in the conventional sense.
• This could form the basis of an alternative implementation of the shopping basket, which uses per-user database tables rather than JSON blobs.
• It provides an explicit model for uploading data to the ESAP-DB from the user's notebook.
• Concerns were raised about how this service could be integrated with the existing design of the ESAP system.
• We noted that the group is not resourced to undertake new and ambitious development projects: we should not sign up to new work unless we are confident that we can deliver it.
• We also noted that our work should be clearly motivated by use cases advanced by the ESFRIs and other stakeholders.
• Nevertheless, we agreed that this model was conceptually appealing, and that it is worthwhile for Pierre to spend some time developing his ideas and thinking about how they could be integrated into ESAP.
• Action on Pierre to dive into the existing ESAP code, do some experimenting, and come back with a concrete proposal to this group at a future meeting.

Report from Metadata Task Force

• Work continues, but no major results to report at this time.

Managing Issues Across Multiple Projects

• We agreed that it is appropriate to use the issue tracker at https://git.astron.nl/groups/astron-sdc/escape-wp5/-/issues for tracking ESAP or general WP5 work.
• This should be preferred to trackers that are tied specifically to the GUI or the API Gateway, as it's hard to use them to get an overview of the project.
• Action on John & Nico to understand how to relate these GitLab trackers to ASTRON's Jira system.

Next Meeting

• (If ready,) discuss Pierre's ESAP DB plan.
• Continue working through ESAP vision document.