Making this project Cloud compatible and EOSC infrastructure runs #45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi everyone.
cc @tinaok @sebastian-luna-valero.
So I'm trying to revive this project, and to make it Cloud (Dask-gateway for the time being) compatible. I wanted to make this work apparent through this PR to get some early feedback if people have some.
In particular, I have a high level question, maybe to @rabernat: is this the good place to start a benchmarking for Cloud infrastructure performances using Pangeo? Should I look somewhere else ?
And more related to this project, I am under the impression that there have been evolutions across time that have not been reflected in Yaml configuration files, am I correct @andersy005 or @kmpaul if you ever remember? For example, trying to use cheyenne.yaml throws this:
Question is: should we keep and update those files, or just throw them away?
Any other advice welcome!