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

mount user's volume #94

Merged
merged 1 commit into from
Sep 23, 2024
Merged

mount user's volume #94

merged 1 commit into from
Sep 23, 2024

Conversation

Tianhao-Gu
Copy link
Collaborator

No description provided.

Copy link

codecov bot commented Sep 20, 2024

Codecov Report

Attention: Patch coverage is 11.76471% with 15 lines in your changes missing coverage. Please review.

Project coverage is 54.37%. Comparing base (81cf6e0) to head (102f5eb).
Report is 4 commits behind head on main.

Files with missing lines Patch % Lines
src/jupyterhub_config/custom_docker_spawner.py 11.76% 15 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #94      +/-   ##
==========================================
- Coverage   56.20%   54.37%   -1.84%     
==========================================
  Files           6        6              
  Lines         306      320      +14     
==========================================
+ Hits          172      174       +2     
- Misses        134      146      +12     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

mount_base_dir = Path(os.environ['JUPYTERHUB_MOUNT_BASE_DIR'])
hub_secrets_dir = Path(os.environ['JUPYTERHUB_SECRETS_DIR'])

cdm_shared_dir = Path(os.environ['CDM_SHARED_DIR']) # Legacy data volume from JupyterLab
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we just get rid of this? Seems like a good time to do so if we're switching infrastructure

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmmm I am thinking we will need to mount a shared dir for people to put shared notebooks. Also, I am planning to use admin account to move existing notebooks to user's new workspace. For the later, there are other ways.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So it's not really legacy then?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmmm yea. Maybe I will remove the comments or remove the mount once we are set stone of mounting volume.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Comment on lines +159 to +161
f'{mount_base_dir}/{user_home_dir}': f'{user_home_dir}', # Global users home directory
f'{mount_base_dir}/{hub_secrets_dir}': f'{hub_secrets_dir}',
f'{mount_base_dir}/{cdm_shared_dir}': f'{cdm_shared_dir}', # Legacy data volume from JupyterLab
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Admin doesn't need the hive metastore dir?

Actually, didn't we say last time there shouldn't be a hive dir at all?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hive is within cdm_shared_dir. So I didn't mount it here specifically.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But didn't we say it's not needed in a recent pr?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you are referring to postgres dir which is remote now so we don't need it. I think users need to read hive in order to read correctly.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems like when a namespace is created in postgres, an associated namespace.db file is created in the hive dir. So I am guessing it's needed. But we can remove it if we noticed it's no longer needed. I want to grant users broad privileges initially, then scale them back gradually based on our findings. That way we can move faster.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@Tianhao-Gu Tianhao-Gu merged commit d48c16f into main Sep 23, 2024
7 of 10 checks passed
@Tianhao-Gu Tianhao-Gu deleted the dev_jupyterhub branch September 23, 2024 20:51
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

Successfully merging this pull request may close these issues.

2 participants