Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore deploying a single hub with individual groups #184

Open
kabilar opened this issue Aug 1, 2024 · 2 comments
Open

Explore deploying a single hub with individual groups #184

kabilar opened this issue Aug 1, 2024 · 2 comments
Milestone

Comments

@kabilar
Copy link
Member

kabilar commented Aug 1, 2024

  1. For the DANDI, LINC, and BICAN projects we are running 3 separate JupyterHubs.
  2. Running a separate hub for each project potentially increases the total base costs compared to running a single hub with separate groups.
  3. Let's explore what it would take to run all projects on the same hub, but separate the profiles (and potentially billing) using groups.
@kabilar kabilar added this to the phase2 milestone Aug 1, 2024
@asmacdo
Copy link
Member

asmacdo commented Aug 3, 2024

I agree that the base cost of running all three as a single hub would be a bit less expensive, maybe $10/day/hub or so base cost.

Here's the challenges I anticipate:

  • cleanly separating the costs: If the math can be a little bit fuzzy, not so much of an issue.
  • custom auth: I am not sure if groups can have a separate auth mechanism, which will be especially challenging to have custom auth endpoint for dandihub and linc, but GitHub org based for bican.

@kabilar
Copy link
Member Author

kabilar commented Aug 3, 2024

Thanks for breaking it down, Austin. Let's discuss more over the next few weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants