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

[EPIC] [DevelopmentSeed partnership] Integrate jupyterhub-home-nfs helm chart into 2i2c infrastructure #4647

Closed
8 tasks done
yuvipanda opened this issue Aug 21, 2024 · 9 comments
Assignees

Comments

@yuvipanda
Copy link
Member

yuvipanda commented Aug 21, 2024

This issue is being refined by @sgibson91

Original issue body

@sunu is working on NASA-IMPACT/veda-jupyterhub#41, where he'll create a helm chart named jupyterhub-home-nfs (or something like that) to provide home directories with per-user quotas on JupyterHub.

This issue tracks @sgibson91 working with @sunu, @batpad and me in helping integrate this into our infrastructure repository and practices. We will meet soon to figure out what next steps are, and who is responsible for what.

Context

A new helm chart is being developed by the devseed team which will provide home directories with per-user quotas on JupyterHub. This issue is tracking the tasks to complete so in order to integrate that helm chart into our infrastructure for reuse.

Task List

TBD: Who is responsible for executing each task? Division of labour between 2i2c and devseed. UPDATE: Decided #4647 (comment)

Definition of Done

  • A helm chart enabling home directories with per-user storage quotas for JupyterHub exists
  • The staging veda hub has been migrated to use this new chart
  • There's documentation on how this can be enabled for other clusters in the 2i2c infrastructure repository

Pre-defined Definition of Done

  • All the tasks have been completed
  • It has been tested to work and to not break any existing functionality
  • Documentation was added so other engineers can implement this in the future if needed
@sgibson91 sgibson91 mentioned this issue Aug 21, 2024
4 tasks
@sgibson91 sgibson91 changed the title Work with developmentseed in integration jupyterhub-home-nfs into our infrastructure [DevelopmentSeed partnership] Integrate jupyterhub-home-nfs helm chart into 2i2c infrastructure Aug 22, 2024
@sgibson91 sgibson91 self-assigned this Aug 23, 2024
@yuvipanda
Copy link
Member Author

This looks good. I've proposed a deadline of sep 13 (or alternatively sep 20) on slack. waiting to hear back.

@sgibson91 can you split this into multiple smaller chunks and put them in refined? Thanks!

@sgibson91 sgibson91 changed the title [DevelopmentSeed partnership] Integrate jupyterhub-home-nfs helm chart into 2i2c infrastructure [EPIC] [DevelopmentSeed partnership] Integrate jupyterhub-home-nfs helm chart into 2i2c infrastructure Sep 3, 2024
@sgibson91
Copy link
Member

In a meeting with Tarashish on Friday, it was agreed that he would be responsible for completing the technical work and I would be available for mentoring/answering questions/generally helping with the integration into the 2i2c/infrastructure repo.

@sgibson91
Copy link
Member

Hey @sunu 👋🏻 I have broken up this epic into smaller task issues and tried to refine them. Can you take a look and let me know if anything's unclear? We should also try and set some deadlines for each of these tasks such that this whole epic can be wrapped up by Sep 20, could you let me know some estimates based on where you currently are with the work please?

@sunu
Copy link
Contributor

sunu commented Sep 4, 2024

Hi @sgibson91! Thanks so much for breaking it down down into smaller tasks!

I'm aiming to finish the first three tasks this week. Let's plan to get on a brief call early next week to discuss the data migration process. We can aim to get the data migrated and switch veda staging hub over to the in-cluster NFS server next week. We can keep the following week as buffer and use it to document the whole process. Does that sound reasonable to you?

@sgibson91
Copy link
Member

Thank you for setting up the meeting, and I've added rough due dates to each of the tasks. I shall also get you write access to the repo so you can merge yourself. Here are our review and merge guidelines for your reference but I am happy to be pinged on anything you'd like to chat about: https://infrastructure.2i2c.org/contributing/code-review/

@sgibson91
Copy link
Member

I have opened #4795 to track any technical assistance I give (e.g., like today when we worked in the AWS account because I have access) and this issue will be tracked by 2i2c's engineering sprint board.

@sgibson91
Copy link
Member

Done! 🎉

@Gman0909
Copy link
Contributor

@yuvipanda
Copy link
Member Author

@Gman0909 I think we should wait until at least #4835 is done before closing the PB issue.

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

4 participants