[Docs] Amplify the main use-cases for tasks and services (WIP) - #4260
Draft
peterschmidt85 wants to merge 3 commits into
Draft
[Docs] Amplify the main use-cases for tasks and services (WIP)#4260peterschmidt85 wants to merge 3 commits into
peterschmidt85 wants to merge 3 commits into
Conversation
Tasks: Nodes and Node groups lead the page; Node groups nested under Nodes; router-and-workers example reframed as "Prototyping services". Services: replicas made explicit in the main example; Replica groups (router, PD disaggregation) is the only replica section. Minor: same Configuration options order on both pages; Retry policy and Ports top-level on Tasks, Gateway on Services; fix dead #replicas-and-scaling anchor. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Rename "distributed task" to "multi-node task" across docs and the dstack skill to match the Nodes section; keep "distributed training". Point links to the removed sections at their replacements: #nodes, #replica-groups, #scaling, #router. Quickstart: mention node groups for tasks and add the matching replicas and replica groups sentence for services. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…rking Apply the multi-node task rename to blog posts. Add compatibility anchors so links to tasks#distributed-tasks and services#replicas-and-scaling still land on the right section. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Amplifies the main use-cases on the Tasks and Services concept pages.
Tasks
NodesandNode groupslead the page. Node groups is nested under Nodes, and the router-and-workers example is reframed as "Prototyping services" with a pointer to thedstack-prototypingskill."Distributed tasks" are now called "multi-node tasks" across the docs, blog posts, and the
dstackskill, matching theNodessection. "Distributed training" is unchanged.Services
replicasis made explicit in the main example, andReplica groups(router, PD disaggregation) is the only replica section, since a router is what production inference needs.Minor
Configuration optionssubsections follow the same order on both pagesRetry policyandPortsare top-level on Tasks,Gatewayon ServicesDistributed tasksandReplicas and scalingsections point to their replacementstasks#distributed-tasksandservices#replicas-and-scalingkeep working via compatibility anchorsTODO
🤖 Generated with Claude Code