[New Hub] NASA Cryo Community -- Cryosphere Community Hub

[colliand]

Hub Description

Tasha Snow and Matt Siegfried of the Colorado School of Mines worked with @fperez and @colliand and members of the cryosphere research community on two NASA proposals over Summer 2022. Both of these proposals were recently funded. These projects will support the use of open science workflows, broaden participation in cryo research, and improve community dynamics. 2i2c will deploy a dask hub for use during a series of events during the Year of Open Science (2023) and beyond.

The main purpose of this issue is to gather the technical details necessary for 2i2c's engineering team to set up the hub.

Future events/milestones/workshops/talks in this project (copied from Google doc running notes)

• Dask aware hub by mid-October - training notebooks and recorded hub training by then?
• October 24-28: Joanna giving 15 min talk to the ICESat-2 Science Team in Austin - invite users onto the hub at this time?
• January 8-12: Tasha giving 20-30 min talk to American Meteorological Society in Denver - no user additions
• March: NASA/NSF FOGSS workshop (in person), 100 Greenland Ice Sheet researchers, two-hour workshop
• April: ICESat-2 Science Team meeting (in person), 100 IS2ST researchers, half-day workshop
• June or Sept: ICESat-2 Hackweek (hybrid), 80 participants, support of 1-week-long workshop
• Summer: SnowEx Hackweek (Hub only)
• September: NASA/NSF WAIS Workshop (hybrid), 120 Antarctic researchers, two-hour workshop
• December 2023: AGU Fall Meeting (in-person), 250 participants, half-day workshop and participation in Year of Open + Science events and presentations
• April 2024-Oct 2025: ICESat-2 Science Team meetings only

Community Representative(s)

• @tsnow03
• @JessicaS11 (potentially?)
• @dfelikson

Others who participated in last week's kickoff event and expressed interest in this hub and the surrounding project inlcude:

• @jdmillstein
• @wsauthoff
• @dfelikson
• @jmunroe

Important dates

• Target start date: 2022-10-07
• Required start date: 2022-10-14
• Any important dates for usage:

Hub Authentication Type

GitHub Authentication (e.g., @mygithubhandle)

Hub logo information

• URL to Hub Image: {{ URL HERE }}
• URL for Image Link: {{ URL HERE }}

Can @tsnow03 or @jessicaS11 please share a URL pointing at an image to be used on the splash page that users land on when they arrive to the hub login page? For example, here is the leap hub's landing page.

Hub user image

• Repository for user image: { REPO LINK IF IT EXISTS }
• User image registry: { REGISTRY IF ONE ALREADY EXISTS }
• User image tag and name: { NAME AND TAG IF IT EXISTS }

What software environment image should be used for the NASA Cryo community hub? In our kickoff, we discussed the idea to launch with a hub image that was used for the SnowEX hackweek. Another possibility would be to use (parts or all of) the JMTE hub used heavily by @fperez and collaborators.

Extra features you'd like to enable

• [ ] scalable dask cluster
• [ ] small, medium, large hardware configurations?

What data centre should be used? The hub should be built on the same data centre where large cryosphere data is stored.

Other relevant information

No response

Hub URL

..2i2c.cloud ### Hub Type _No response_ ### Tasks to deploy the hub - [x] Engineer who will deploy the hub is assigned - [x] Deploy information filled in above - [x] Initial Hub deployment PR: - [x] Administrators able to log on - [x] Community Representative satisfied with hub environment - [x] Hub now in steady-state

[sgibson91]

I'm signing off for the night now, but will pick this back up in the morning if you can add me to the org as an admin.

[tsnow03]

Thanks @sgibson91. Apologies I had to step away for a couple meetings. I've sent you an invite to our org.

> In this case, they should go to the configuration page for this app within their GitHub organization and explicitly grant it access.

I was unable to find any AuthO apps or Github Apps to grant permissions to in the Developer Settings or the third-party access on our org so I hit a dead end. I am guessing I am looking in the wrong place for this app?

[JessicaS11]

@tsnow03 @sgibson91 Not sure about others, but I was able to start up a hub (non-staging) as of about 20 minutes ago...

[sgibson91]

Not sure about others, but I was able to start up a hub (non-staging) as of about 20 minutes ago...

Yes, I reset the OAuth app permissions for the org last night from my phone, so this should be working now.

I was unable to find any AuthO apps or Github Apps to grant permissions to in the Developer Settings or the third-party access on our org so I hit a dead end. I am guessing I am looking in the wrong place for this app?

I eventually found this under "OAuth application policy", but I think this is a recent change and GitHub's current documentation seems outdated

However, I don't think it would have shown up there if you didn't click "Grant" next to the org name, before authorising the app at the first login. For example, if I wanted to grant the app access to the binderhub-test-org org in the screenshot below, I need to first click "Grant", then "Authorise".

The apps might have shown up there if someone who isn't an admin had clicked "Request" instead (as you can see the "Request" button is present for orgs I don't own), but I think all the admins would have also received a notification if that had happened and you wouldn't have needed to go hunting in the settings.

(I'm taking all these screenshots so I can improve docs 😄 )

[sgibson91]

I've also updated the domains so the hubs are now accessible at, respectively:

• https://staging.hub.cryointhecloud.com
• https://hub.cryointhecloud.com

[tsnow03]

Everything is working beautifully! Thank you so much! And our users are only seeing the small and medium instances while advanced team are seeing all of them.

Thank you for the clarification on the instructions! I’m keeping notes on places that were super streamlined and parts that were more ambiguous so we can trade notes at any point once we get into the swing of this a little further.

[damianavila]

Given we have confirmation from the community representative that things are working as expected, I am going to close this one! Feel free to send any follow-up through our support channel at support@2i2c.org.

Thanks!