JupyterHub HPC Meeting - January 2023

• Date: 2023-01-04

• Time: 8:30 AM PST

  • Your timezone: https://arewemeetingyet.com/Los Angeles/2023-01-24/08:30/JupyterHub-HPC

• Where you can find these and past meeting notes: https://jupyterhub-team-compass.readthedocs.io/en/latest/meetings/hpc/

• Calendar for future meetings: https://jupyterhub-team-compass.readthedocs.io/en/latest/meetings/

Welcome to the Meeting

Hello! If you are joining the team video meeting, sign in below so we know who was here. Roll call:

• name / institution / GitHub handle

• Michael Milligan / MSI @ U of MN / @mbmilligan

• Ryan Lovett / UC Berkeley / @ryanlovett

• Shane Canon / LBNL / @scanon

Quick updates

60 second updates on things you have been up to, questions you have, or developments you think people should know about. This is also a chance to suggest a future presentation if you’ve got work currently in progress you might want to share. Please add yourself, and if you do not have an update to share, you can pass.

• Name: Your report or celebration

• Ryan - may have path forward for portwrap/batchspawner integration, hope to start testing now

Reports and celebrations

This is a place to make announcements (without a need for discussion). This is also a great place to give shout-outs to contributors! We’ll read through these at the beginning of the meeting.

• Name: Your report or celebration

Agenda items

Let’s collect all potential agenda items here before the start of the meeting. We will then attempt to create a coherent agenda that fits in the 60m meeting slot. If there are similar items try and group them together.

• All: Standing project items:

  • Batchspawner check-in: Issues and PRs

    • Still to-do from previous months:

      • PR updating test matrix - jupyterhub/batchspawner#252

      • Docs fixing (not overriding master templates)

    • Merge fix for JupyterHub 3 compatibility in singleuser?

      • e.g. jupyterhub/batchspawner#247

      • Ryan is running this in production w/Hub 3 for a while

  • Wrapspawner check-in: Issues and PRs

    • Quiet

• Advertising

  • Should HPC be its own subproject or some kind of more official interest group?

  • Broadening beyond Hub is happening

• Workshop/conference news:

  • JupyterCon 2023

    • Cite des Sciences, Paris

    • May 10-12

    • https://www.jupytercon.com/

    • CfP ended December 20

  • PEARC 2023 CfP is out

    • papers/short papers due March/April

• Abandoned things to revive/decide fate of?

  • jupyterhub/research-facilities

  • jupyterhub/jupyterhub-deploy-hpc

  • Jupyter (not just hub) in HPC subproject?

    • Rollin will look at this in January for Feb meeting

• Request for assistance/guidance on jupyterhub-singleuser/portwrap integration (ryanlovett)

  • Mike and Ryan will talk offline

  • portwrap is a CLI with command you want put in a namespace

  • somewhere in the config instead of invoking jupyter, you could just run portwrap

    • But it wants to run jupyterhub-singleuser

    • How to configure the actual command that jupyterhub-singleuser invokes

  • Ryan now thinks he has a way forward

• Announcements from the jupyterhub-announcement service can appear in JupyterLab too:

  • rcthomas/jupyterhub-announcement

  • Josh0823/nersc-refresh-announcements

• Ryan: stopping a spawned server, jupyterhub/jupyterhub#2975

  • Michael - looking at user.py in Hub 2 vs Hub 3 seems like there may be different behavior, which would explain why this group has different experiences here

Links Shared