-
Notifications
You must be signed in to change notification settings - Fork 7
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
💡 [Feature] Include rook server in optional components #455
Comments
Should also consider adding it as a provider to Weaver to give it instant OGC API support. |
I did a quick search on DockerHub, did not find a matching docker image. Is Rook publishing their docker image to another public registry? Or they do not yet publish any docker images? |
They don't. Can we use our dockerhub account to do it? |
Oh ! So I guess they deploy using Ansible. Yes we can use our DockerHub account to host their image. We are paying so have unlimited storage. But that also means their Dockerfile is not tested ! I was hoping for a quick win on this one, might not be the case anymore. |
Yes, their production backend runs SLURM. |
Could also be added to their repo directly and make use of GitHub Container Registry. |
Description
Rook is a birdhouse WPS server offering simple subsetting and averaging processes. See https://github.com/roocs/rook/tree/master/rook/processes
Unlike Finch, it has an established database of datasets it is willing to operate on. That is, process input includes a dataset ID, not a URL to a file, and the server converts that ID to an actual path. This database is built from an intake catalog.
Rook comes with a custom-built client, rooki, based off birdy.
This work would align with the ESGF roadmap to deploy remote computing along ESGF nodes.
Steps:
References
Concerned Organizations
The text was updated successfully, but these errors were encountered: