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

Add public storage folder where all users have read/write permissions #43

Closed
tsnow03 opened this issue Mar 3, 2023 · 7 comments
Closed

Comments

@tsnow03
Copy link
Member

tsnow03 commented Mar 3, 2023

We need to create a public storage folder because workshop groups are going to be working in CryoCloud soon and all users will need to freely share data across the entire group.

@MattF-NSIDC @trey-stafford and QGreenland (May 22-25) will definitely need this feature for a relatively small group. @elliesch and @facusapienza21 may also need this for the Norwegian ML workshop held on April 16-21, but it may be necessary for them to have a completely separate file sharing folder that is only linked to their GitHub Team so that data storage can be more easily monitored.

We need input from @colliand @jmunroe and the 2i2c team to understand if there are ways to make storage folders only visible and writable by certain GitHub teams and if this is the use model we want to adopt for some of the more resource intensive events we support.

@jmunroe
Copy link

jmunroe commented Mar 3, 2023

Is the need for block file storage (conventional, filenames and paths) or object storage (e.g. Zarr datasets) ? The shared/ folder already exists for the purpose of sharing files between groups (although that's readable to everyone and writable by hub-admins)

I'll get feedback from the 2i2c engineering team on options when it comes to assigning permissions and access controls to storage resources.

@tsnow03
Copy link
Member Author

tsnow03 commented Mar 7, 2023

Conventional. They need something that all users can read/write to and we would like to keep our shared-readwrite separate from that. I think some hubs have used a public folder for this in the past, but I'm not sure if this is still the best solution. Thank you @jmunroe!

@tsnow03 tsnow03 moved this to 📋 Backlog in March 2023 Event Mar 7, 2023
@tsnow03
Copy link
Member Author

tsnow03 commented Mar 7, 2023

@jmunroe would you mind assigning this task and the (small server task)[https://github.com/orgs/CryoInTheCloud/projects/1/views/2#:~:text=Add%20a%20couple%20smaller%20server%20options%20to%20initial%20menu%3F] to someone in our github project? I'm not sure who would work on this. Is this something you would like me to email the 2i2c help to request?

@jmunroe
Copy link

jmunroe commented Mar 7, 2023

This exactly the kind of request best made via [email protected] so it gets action by one of the 2i2c cloud engineers.

@tsnow03
Copy link
Member Author

tsnow03 commented Mar 13, 2023

We settled on wanting to add a public storage folder that everyone has read/write permissions for.

We would also like to know if it is possible to have a storage folder related to an event that only a specific GitHub team can read and write from - allowing us to more easily monitor the data storage use for an event.

@jmunroe
Copy link

jmunroe commented Mar 16, 2023

Having a storage folder that is accessible by on specific GitHub teams is not something that exists yet. But it is a feature that 2i2c is investigating. There is preliminary work that would first need to be done on user managed JupyterHub groups:

I don't have timeline on when such a feature could be rolled-out but feedback from communites like CryoCloud will help us prioritize where to focus our development efforts.

yuvipanda added a commit to yuvipanda/pilot-hubs that referenced this issue Mar 20, 2023
@tsnow03 tsnow03 moved this from 📋 Backlog to 👀 In review in March 2023 Event Mar 27, 2023
@tsnow03 tsnow03 moved this from 👀 In review to 🏗 In progress in March 2023 Event Mar 27, 2023
@tsnow03
Copy link
Member Author

tsnow03 commented Mar 27, 2023

The shared-public folder looks great! Is there anything else still being worked on for this issue? If not, I think we are ready to close it.

@tsnow03 tsnow03 closed this as completed Jun 15, 2023
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in March 2023 Event Jun 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants