Add roadmap. #1317
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,59 @@ | ||
| # SkyPilot Roadmap | ||
|
|
||
| This doc lists general directions of interest to facilitate community contributions. | ||
|
|
||
| Note that | ||
| - This list is not meant to be comprehensive (i.e., new work items of interest may pop up) | ||
| - Even though listed under a specific version, not all items need to be completed before we ship that version (i.e., some items can go into future versions) | ||
|
|
||
| ## v0.3 | ||
|
|
||
| ### Managed Spot | ||
| - Minimize the cost of the controller | ||
| - Support running spot controller on an existing/local cluster | ||
| - Reducing the fixed cost of the controller (e.g., allow setting controller VM type) | ||
| - Supporting a higher number of pending/concurrent jobs | ||
| - Framework-specific guides to add checkpointing/reloading using SkyPilot Storage | ||
|
|
||
| ### Smarter Optimizer | ||
| - Fine-grained optimizer: pick by cheapest zone order | ||
| - Better consider data egress time/cost | ||
| - Consider buckets/Storage objects in file_mounts | ||
| - Optimizing the data placement for SkyPilot Storage local uploads | ||
| - Use the optimizer to decide the bucket location | ||
|
|
||
| ### Programmatic API | ||
| - Refactor/extend the current API to *make it easy to programmatically use SkyPilot* | ||
| - Expose core classes in docs | ||
|
|
||
| ### Support more clouds | ||
| - Refactoring of interfaces to ease adding new clouds | ||
| - IBM Cloud | ||
|
There was a problem hiding this comment. Add lambda labs/runpod/jarvis labs? |
||
| - Explore support for low-cost clouds (e.g., lambda labs/runpod/jarvis labs) | ||
|
|
||
| ### On-prem | ||
| - Robustify the on-prem feature | ||
| - Design for switching between cloud and on-prem | ||
|
There was a problem hiding this comment. Do we want to add an item before this: |
||
| - Explore/design of "local mode" to run SkyPilot tasks locally | ||
|
|
||
| ### Faster launching speed | ||
| - Consider a more minimal image | ||
| - Azure speed investigation | ||
|
|
||
| ### k8s support | ||
| - Ray-on-k8s backend | ||
| - To figure out: Launch a new k8s cluster? Launch SkyPilot Tasks to an existing k8s cluster? | ||
|
|
||
| ### Cost: Optimization, Tracking, and Reporting | ||
| - Track and show costs related to a job/cluster | ||
| - For managed spot jobs, track and show %savings vs. on-demand | ||
| - Optimizer: take into account disk costs | ||
|
|
||
| ### Serverless | ||
| - Design and prototype of a "serverless jobs" submission API and CLI | ||
| - Initial use case: hundreds of hyperparameter tuning trials | ||
|
|
||
| ### Backend | ||
| - Support heterogeneous node types in a cluster (e.g., in RL, CPU actor(s) and GPU learner(s) in the same cluster) | ||
| - Support CPUs as resource requirements | ||
| - General robustness/UX improvements | ||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like to call this
v1.0.0-dev0orv1.0.0to align with the current master version. Reason: I believe thev0.3will not include all the features listed here and we should not make a promise for the features we are not going to have inv0.3. This doc is a longer-term plan thanv0.3.