-
Notifications
You must be signed in to change notification settings - Fork 17
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
Document object storage and scratch bucket #135
Comments
@rabernat would be lovely for you to write it! We can keep it inside 2i2c for now as I don't see another obvious location, and we can move it around later as we find places for it. |
Merged
Related PRs (besides the one linked): |
Repository owner
moved this from In progress
to Complete
in DEPRECATED Engineering and Product Backlog
Apr 25, 2022
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
Our hubs are in the cloud, which means that a powerful and scalable way to interact with data is via cloud object storage. The Pangeo-style hubs are (afaik) all configured with an object storage "scratch bucket", meaning that object storage is part of 2i2c's service.
Our new LEAP and M2LInES hubs will need user-facing documentation that explains how to work with object storage. This documentation can live inside or outside 2i2c. Currently 2i2c docs do not address object storage at all. I believe it would be advantageous to us all if this were part of 2i2c documentation.
Proposal
I propose we start by migrating some of the content in
https://pangeo.io/cloud.html#cloud-object-storage
to
https://docs.2i2c.org/en/latest/admin/howto/data.html
Overall, a longer and more detailed "data management" section, without more information about how to work with data in the cloud, should be our goal.
I can commit to writing this documentation if we agree it is in-scope for 2i2c.
Updates and actions
No response
The text was updated successfully, but these errors were encountered: