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

Modify globus strategy to use single guest collection #239

Open
jdhayhurst opened this issue May 11, 2023 · 3 comments
Open

Modify globus strategy to use single guest collection #239

jdhayhurst opened this issue May 11, 2023 · 3 comments
Assignees

Comments

@jdhayhurst
Copy link
Collaborator

Currently, we create a separate dir and guest collection for each submission. Instead, we can create one guest collection and each time create a subdir and add an ACL to that subdir. This cuts down on the overheads of managing so many collections.

@ljwh2
Copy link

ljwh2 commented May 31, 2023

Prioritise this in next sprint commencing 14th June

@jdhayhurst
Copy link
Collaborator Author

Top level function: sumstats_service.resources.globus.mkdir

Currently this function:

  1. creates a new directory a submission
  2. creates a "guest collection" to give the user access to that directory only.

Change this strategy to:
0. Setup a guest collection at the parent dir (not something we need to do once, not something that needs coding)

  1. create a subdirectory inside the parent dir
  2. add permissions to that subdir allowing the user access to the subdir only (can modify add_permissions_to_endpoint() to do this)
  3. make sure that we can still get a link for the user to navigate to their subdir

@jdhayhurst
Copy link
Collaborator Author

ACLs are also limited to 1000 (per guest collection), so this solution doesn't change the fact that we can only have 1000 concurrent submissions open.

Recommend closing this as a non-issue and focusing on #252 instead

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