ESAP—Jupyter integration discussion

lundi 26 avr. 2021, 16:00 → 17:00 Europe/Paris

Zoom

Escape ZoomRoom is inviting you to a scheduled Zoom meeting.

Meeting ID: 863 5651 9787
Passcode: (see e-mail)
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
Passcode: 814874

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

16:00 → 17:00 Discussion

Rohini's Slides

Stelios' Slides

• Binder (and, specifically, BinderHub) seem like promising technologies.
  • Deploying to MyBinder may be a useful test system, but ultimately we need to be able to support custom infrastructure. Brief word from infrastructure providers was that deploying Binderhub is a plausible thing to ask for.
• Stelios is involved with WP3+WP5 metadata activities and will keep this group in the loop as far as it's relevant.
• For an initial “MVP”, compute facilities can be hard-coded into the ESAP configuration database. Making this dynamic would be nice in the long term, but is not essential for now.
  • Currently, they are hard coded into the UI, which is really not ideal.
  • We need to figure out what (meta)data about them to include in that configuration database.
• We agreed that a minimum viable product could punt on the idea of moving compute to the data for now. We should certainly return to this later, though.
• We discussed (somewhat inconclusively) whether ESAP should exchange quries or query results with the JupyterHub system when it needs to transfer data.
  • This relates to the old “shopping cart” idea, which needs to be written up properly.
  • Probably just exchanging queries is simpler, which is ideal for the MVP.
  • It is quite limiting on the system though:
    • Couldn't upload data to ESAP using and then pass it on for analysis.
    • Hard to imagine a workflow where you are round-tripping catalogues through JupyterHub to winnow them down.
• Need to find a place for holding/managing documents. Action on John.