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

Investigate and Implement Integration of CyberGIS with CIROH JupyterHub #60

Open
arpita0911patel opened this issue Aug 21, 2024 · 5 comments
Assignees
Labels
enhancement New feature or request

Comments

@arpita0911patel
Copy link
Member

No description provided.

@arpita0911patel arpita0911patel added the enhancement New feature or request label Aug 21, 2024
@ciroh-it-admin ciroh-it-admin changed the title CyberGIS-Compute Integration with CIROH JupyterHub Investigate and Implement Integration of CyberGIS with CIROH JupyterHub Sep 27, 2024
@alexandermichels
Copy link

Generally, we need:

  • the URL of the JupyterHub
  • the ID of the Globus endpoint to transfer data to/from the JupyterHub. The Globus user [email protected] will also need permissions on the endpoint.
  • the path on the endpoint where user data is located (so if user data is at /data/user_data/<USERNAME>, we want /data/user_data)
  • the path within the Jupyter container to transfer data to (usually /home/jovyan/ or /home/jovyan/work)

Examples here: https://github.com/cybergis/cybergis-compute-core/blob/v2/configs/jupyter-globus-map.example.json

We also need to know (for file transfer purposes) what format your user data folders are. For example, our I-GUIDE Jupyterhub uses the pattern i-guide-claim-<USERNAME> where (https://github.com/cybergis/cybergis-compute-core/blob/v2/src/helpers/python/globus_user_mapping.py). We default to using the username with only ascii lowercase and numeric digits, but if you have some other pattern we can add it to our user mapping.

@benlee0423
Copy link
Collaborator

@alexandermichels
Where "path on the endpoint where user data is located" is defined?
Maybe in the below location?
https://gitlab.nrp-nautilus.io/prp/globus-connect/-/blob/master/globus-connect.yaml?ref_type=heads#L35
Is this path accessible from jupyter instance?

@benlee0423
Copy link
Collaborator

@alexandermichels
Globus endpoint has to be setup in the same namespace where jupyter hub is installed in k8s?
We have staging and prod namespace in k8s, where staging and prod resources for jupyterhub are installed.

@alexandermichels
Copy link

I haven't deployed globus with K8s, but based on the README in the repo it appears the data is stored in /data/gridftp-save/. The Jupyter user containers don't need to know about this path, but the Globus transfer is being executed by the Globus pod so we need to tell it where to put the files.

I don't think the namespace matters for Compute as long as you can make the data accessible to both the Globus pod and the user Jupyter pod, but I am not an expert on PVs/PVCs.

@benlee0423
Copy link
Collaborator

benlee0423 commented Oct 8, 2024

@alexandermichels
I have emailed the information requested for testing purpose.
This information will be different what we will have in our prod k8s cluster.

Now, I have assigned to subscription status, and please let me know how to add the Globus user [email protected] to the endpoint.

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

No branches or pull requests

3 participants