Refactor high-level description to more accurately reflect Dask cloudprovider #391
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.
This project has become a bit of a catchall for Dask community cloud tooling. It contains cluster managers for launching VMs, containers, etc natively but it also has plugins and tools that can be used independently on any Dask cluster running on the cloud such as the spot/ephemeral termination watchdog plugins.
In the future, it could contain other things like example Cloudformation/Terraform templates,
dask-mpi
style runners for various cloud services and more.There are so many ways to deploy Dask on the cloud and I'm keen not to present this repo as "the way" but more as a collection of community-maintained cloud utilities and a resource for all folks using Dask on the cloud. So I've reworded the docs and README to reflect this hopefully.
I've also added an alternatives page with links to other tools and services that are commonly used for running Dask on the cloud.
cc @mrocklin, @jsignell, @costrouc in case you have input on the alternatives page.