You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Primary issue: Users are confused and frustrated when they hear they can only read from S3 buckets, and can’t write to them.
Secondary issue: Users want to be able to connect to data in other storage services other than S3 (for example, PolyBox). This is particularly important to the SDSC Academic Team (according to Nati).
Also datashim (the current technology for mounting S3) is unreliable and has lots of issues (r/w not working properly, sometimes doesn’t mount, not really actively supported)
🚞 User stories / journeys
As a RenkuLab sessions user, I want to be able to write data outputs back to my S3 bucket.
As a SDSC Academic Team member, I want to mount my NextCloud or PolyBox drive in a RenkuLab session so I have some personal storage space that I take with me across all my projects.
The text was updated successfully, but these errors were encountered:
Reference pitch: https://www.notion.so/Make-Cloud-Storage-Read-Write-Universal-Storage-73fc06c3b65a40d6bb073a8b76db0905
🤔 Problem
Primary issue: Users are confused and frustrated when they hear they can only read from S3 buckets, and can’t write to them.
Secondary issue: Users want to be able to connect to data in other storage services other than S3 (for example, PolyBox). This is particularly important to the SDSC Academic Team (according to Nati).
Also datashim (the current technology for mounting S3) is unreliable and has lots of issues (r/w not working properly, sometimes doesn’t mount, not really actively supported)
🚞 User stories / journeys
As a RenkuLab sessions user, I want to be able to write data outputs back to my S3 bucket.
As a SDSC Academic Team member, I want to mount my NextCloud or PolyBox drive in a RenkuLab session so I have some personal storage space that I take with me across all my projects.
The text was updated successfully, but these errors were encountered: