dask / dask/dask-cloudprovider
It should be possible to provide custom Scheduler and Worker classes to ECSCluster
Open
- Dominant language
- Python
- Stars
- 147
- Forks
- 119
- PR merge metrics
- No merged PRs in 30d
Description
The ECS clusters have built-in scheduler and worker classes which are hard-coded into their configurations for firing up new tasks. It should be possible for users to subclass Scheduler and Worker and tell ECSCluster to use those subclasses instead. e.g. if we want to alter their behaviour at all in ways not exposed by ECSCluster itself.
Contributor guide
Research direction
Start by tracing ECSCluster's configuration for its built-in Scheduler and Worker classes. Confirm how existing cluster startup uses those classes, then verify that user-supplied subclasses are accepted and used when creating tasks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100