[New Hub] [Phase 3] Hub Setup - disasters.2i2c.cloud

[jnywong]

Context

https://2i2c.freshdesk.com/a/tickets/2918

This hub deployment request is part of 2i2c's ongoing NASA VEDA project. The Disasters hub will be launched with configuration and image based on the VEDAHub. The hub should be deployed in the NASA SMD cluster where 2i2c is currently operating the NASA VEDA hub.

Please replicate the current VEDAHub infrastructure

How many hubs will be deployed?

1

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

nasa-veda

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: Disasters (NOT READY)

Phase 3.1: Initial setup

Question	Answer	Notes
Name of the hub	disasters
Dask gateway?	Yes
Splash image URL	https://github.com/NASA-IMPACT/veda-config-disasters/blob/221dbcee3ba0411eb6306008bb5f44714276ba28/overrides/components/header-brand/NASA_DISASTERS_LOGO_WHITE_TYPE-mapping-portal_small.png
Homepage URL	https://disasters-nasa.hub.arcgis.com/
Funded by?	NASA	https://www.earthdata.nasa.gov/esds
Authentication Mechanism	GitHub
Admin Users (GitHub handles or emails, depending on Mechanism)	@slesaad, @freitagb

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?	Yes
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.

Note

Replicate VEDA profile list – including fancy profiles

Question	Answer	Notes
Pangeo Notebook?	Yes
RStudio (with Rocker)?	Yes
Allow users to specify any image they want to use?	Yes	If Yes, enable unlisted_choice.
Max RAM option allowed
GPU enabled?	Yes
Default Interface	JupyterLab
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	GitHub
GitHub Teams based access?	Yes
List of GitHub Teams to be granted access (if required)	TBC

Phase 3.5: Profile List finetuning

Question	Answer	Notes
Custom image to be specified?	Yes	QGIS Linux Desktop (copy VEDA)

[yuvipanda]

I've replied on freshdesk asking for accounts to be created for folks.