search

2i2c-org / infrastructure

Infrastructure for configuring and deploying our community JupyterHubs.
https://infrastructure.2i2c.org
BSD 3-Clause "New" or "Revised" License
105 stars 64 forks source link

[New Hub] [Phase 3] Hub Setup - queens.2i2c.cloud #4824

Closed jmunroe closed 1 month ago

jmunroe commented 1 month ago

Context

Depends on

Due date for hub deployment: Sep 30, 2024

How many hubs will be deployed?

2

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

queensu

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:

Hub 1: staging (READY)

Phase 3.1: Initial setup

Question Answer Notes
Name of the hub staging
Dask gateway? No
Splash image URL Queens logo
Homepage URL
Funded by?
Authentication Mechanism CILogon for @queensu.ca email
Admin Users (GitHub handles or emails, depending on Mechanism)

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? Yes If Yes, enable unlisted_choice.
Max RAM option allowed
GPU enabled? No
Default Interface JupyterLab
Allow multiple concurrent servers per user? No 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
GitHub Teams based access? NA
List of GitHub Teams to be granted access (if required)

Phase 3.5: Profile List finetuning

Question Answer Notes
Custom image to be specified?

Hub 2: prod (READY)

Same config as staging

sgibson91 commented 1 month ago

@jmunroe We don't support Auth with Azure identity, they can have CILogon if their uni is registered or GitHub. Otherwise no.

sgibson91 commented 1 month ago

There are no admins other than 2i2c currently. These can be added through future support tickets.