[New Hub] [Phase 3] Hub Setup - advanced

[yuvipanda]

Context

No response

How many hubs will be deployed?

1

Which cluster will the hub(s) be deployed on?

temple

Hub Setup Information

For each hub to be deployed, copy the tables below and fill them in.
The tables must be complete for each hub to be considered READY to be
deployed. For a staging/prod pair, a statement such as "Same as staging
but for production" will suffice for the prod hub's specification. Use
the Notes column to provide any contextual information.

Available runbooks:

• https://infrastructure.2i2c.org/hub-deployment-guide/runbooks/phase3/

Hub 1: advanced (READY)

Phase 3.1: Initial setup

Question	Answer	Notes
Name of the hub	advanced
Dask gateway?	no
Splash image URL	copy from existing temple config
Homepage URL	copy from existing temple config
Funded by?	copy from existing temple config
Authentication Mechanism	CILogon
Admin Users (GitHub handles or emails, depending on Mechanism)	copy from existing temple hub

At the end of this phase, both 2i2c engineers and the admin users mentioned can login to the hub.

Phase 3.2: Object storage access

Question	Answer	Notes
Scratch bucket enabled?	No
Persistent bucket enabled?	No
Requester pays requests to external buckets allowed?	No

At the end of this phase, both 2i2c engineers and the admin users mentioned can access any object storage setup.

Phase 3.3: Profile List

These are the standard profile list options to start with. They can be customized later.
Use the Notes column to provide extra information, such as specific image tags to use, or deployer generate resource-allocation choices command to use for RAM, etc.

Question	Answer	Notes
Pangeo Notebook?	No
RStudio (with Rocker)?	No
Allow users to specify any image they want to use?	No	If Yes, enable unlisted_choice.
Max RAM option allowed	4 options with r5.xlarge (use the generator script)
GPU enabled?	No
Default Interface	Lab
Allow multiple concurrent servers per user?	Yes	If yes, enable allowNamedServers.

At the end of this phase, the admin users mentioned should be able to start a server with their desired environment(s).

Phase 3.4: Authentication tuning

Question	Answer	Notes
Authentication Mechanism	CILogon	Copy from existing template
GitHub Teams based access?	No
List of GitHub Teams to be granted access (if required)

Phase 3.5: Profile List finetuning

Question	Answer	Notes
Custom image to be specified?	Yes	laserchemist/datascience:v13 (should be default and only)

[yuvipanda]

We may change out the URL eventually.

[aprilmj]

I assigned the other two (seemingly straightforward) cards to @agoose77 solo, but on the surface this one looked like it might need pairing with @GeorgianaElena and be larger. I'd ask Angus to review and confirm whether all 3 cards are doable within this sprint.

I'd also like a little time from @jmunroe, when he's able, to make sure we're tracking this work correctly as an Advanced tier rollout - I don't think Yuvi and I have correctly structured the cards.

FYI @yuvipanda

[yuvipanda]

I think this is a fairly straightforward hub, so hopefully @agoose77 doesn't need explicit help from @GeorgianaElena