Closed jmunroe closed 2 months ago
Hey @pending and @jmunroe! 👋 I noticed there is still pending information about the new hub deployment. Can you please help us fill it in?
The information pieces still missing, are:
- community representative handle
- technical support contacts listed
- hub authentication type
- first hub administrators
- extra features you would like to enable
- other relevant information to the features above
Details about each of them can be found in the top comment. But if you have questions about any of them, please ping the 2i2c/engineering
team and they will help you.
After the form in the top comment is filled in, an engineer will be assigned and will start deploying the new hub 🚀. Thank you!
I appreciate the @consideRatio breakdown in https://github.com/2i2c-org/meta/issues/804 of functionality. To make this request more specific, I think this new binder.hhmi.2i2c.cloud
should enable
The existing hhmi.2i2c.cloud
should have
And for completeness, the hub spyglass.hhmi.2i2c.cloud
recently deployed has
Does specifying hubs with this list of requested functionality help give flexibility to @2i2c-org/engineering ?
This can be delay in favour of the catalyst hubs. @jmunroe shared that perspective on slack.
I spoke to @jmunroe and it's time to pick this up again.
I have reformatted this to use the newer format for hub requests.
I tried to deploy this in https://github.com/2i2c-org/infrastructure/pull/4320 but authentication to the image registry is failing. I tried GAR instead of quay.io because it is a GCP cluster. I also tried implementing https://github.com/2i2c-org/binderhub-service/issues/113 incase that is specific to GAR binders (the binderhub-ui-demo hub is also on GCP), but that still didn't work.
We should timebox this and if not reasonable solution can be found, I'll just use quay.io instead.
We should timebox this and if not reasonable solution can be found, I'll just use quay.io instead.
Great call, @sgibson91!
Just used quay.io instead
A part of https://github.com/2i2c-org/infrastructure/issues/4109.
Phase 2: Cluster
Use the existing hhmi cluster.
Phase 3: Hub Setup
Hub 1: binder
Phase 3.1: Initial setup (READY)
Phase 3.2: Object storage access (READY)
Phase 3.3: Profile List (READY)
N/A, as BinderHub UI will be used
Phase 3.31: Resource configuration (READY)
No profile list, properties set under
singleuser
Phase 3.4: Authentication tuning (READY)
Phase 3.5: Profile List finetuning (NA)
NA, as BinderHub UI will be used
Phase 3.6: BinderHub config (NOT READY)
^binder-examples/.*|LorenFrankLab/.*$