Skip to content

Conversation

nealvaidya
Copy link
Contributor

@nealvaidya nealvaidya commented Jul 17, 2025

Overview:

New hello world example that focuses on LLM deployment. Also includes some explanation of what's happening under the hood.

Summary by CodeRabbit

  • Documentation
    • Added a new Quickstart guide for deploying Large Language Models (LLMs) with Dynamo, including setup instructions, architecture overview, and example usage.

@nealvaidya nealvaidya force-pushed the nealv/new_hello_world branch from 17abadc to fcee50d Compare July 23, 2025 01:43
@nealvaidya nealvaidya marked this pull request as ready for review July 23, 2025 01:44
@nealvaidya nealvaidya requested review from nnshah1, whoisj and a team as code owners July 23, 2025 01:44
@nealvaidya nealvaidya requested a review from athreesh July 23, 2025 01:45
@nealvaidya nealvaidya changed the title docs: hello world with new UX docs: Quickstart with new UX Jul 23, 2025
Copy link
Contributor

coderabbitai bot commented Jul 23, 2025

Walkthrough

A new Quickstart guide in Markdown format has been added to the documentation. The guide provides step-by-step instructions for deploying Large Language Models using Dynamo, including setup prerequisites, component descriptions, request flow, and example usage. No code or exported entities were modified.

Changes

File(s) Change Summary
examples/basics/quickstart/README.md Added a new Quickstart guide for Dynamo LLM deployment

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Frontend
    participant NATS
    participant vLLM Backend
    participant etcd

    User->>Frontend: Send chat completion request (HTTP)
    Frontend->>etcd: Discover available vLLM models
    Frontend->>NATS: Package & route request
    NATS->>vLLM Backend: Deliver request
    vLLM Backend->>NATS: Send response
    NATS->>Frontend: Relay response
    Frontend->>User: Stream response (HTTP)
Loading

Estimated code review effort

1 (~2 minutes)

Poem

In a warren of docs, a new guide appears,
Quickstart for Dynamo, to banish your fears.
With NATS and etcd, the models deploy,
Frontend and backend, in seamless convoy.
Now LLMs run with a hop and a cheer—
Rabbits and humans, the quickstart is here!
🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
examples/basics/quickstart/README.md (1)

69-80: curl example: quoting & JSON formatting brittle

The long, single-quoted payload breaks on shells that honour single quotes literally across newlines and prevents variable interpolation. For portability:

curl -X POST http://localhost:8000/v1/chat/completions \
  -H 'Content-Type: application/json' \
  -d '{
    "model": "Qwen/Qwen3-0.6B",
    "messages": [
      { "role": "user", "content": "Tell me a story about a brave cat" }
    ],
    "stream": false,
    "max_tokens": 1028
  }'

Changes:
• Added -X POST to be explicit.
• Kept JSON in one literal block without trailing spaces after backslashes.
• Ensured a space after "stream":.

Helps avoid copy-paste glitches and clarifies the request method.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b127d95 and fcee50d.

📒 Files selected for processing (1)
  • examples/basics/quickstart/README.md (1 hunks)
🧠 Learnings (1)
examples/basics/quickstart/README.md (4)

Learnt from: ptarasiewiczNV
PR: #2027
File: container/deps/vllm/install_vllm.sh:0-0
Timestamp: 2025-07-22T10:22:28.951Z
Learning: The --torch-backend=auto flag works with vLLM installations via uv pip install, even though it's not a standard pip option. This flag is processed by vLLM's build system during installation to automatically match PyTorch distribution with container CUDA versions.

Learnt from: GuanLuo
PR: #1371
File: examples/llm/benchmarks/vllm_multinode_setup.sh:18-25
Timestamp: 2025-06-05T01:46:15.509Z
Learning: In multi-node setups with head/worker architecture, the head node typically doesn't need environment variables pointing to its own services (like NATS_SERVER, ETCD_ENDPOINTS) because local processes can access them via localhost. Only worker nodes need these environment variables to connect to the head node's external IP address.

Learnt from: fsaady
PR: #1730
File: examples/sglang/slurm_jobs/scripts/worker_setup.py:230-244
Timestamp: 2025-07-03T10:14:30.570Z
Learning: In examples/sglang/slurm_jobs/scripts/worker_setup.py, background processes (like nats-server, etcd) are intentionally left running even if later processes fail. This design choice allows users to manually connect to nodes and debug issues without having to restart the entire SLURM job from scratch, providing operational flexibility for troubleshooting in cluster environments.

Learnt from: PeaBrane
PR: #1409
File: examples/router_standalone/worker.py:171-186
Timestamp: 2025-06-08T08:30:45.126Z
Learning: Example code in the examples/ directory may intentionally use hard-coded values or simplified implementations that wouldn't be appropriate for production code, but are acceptable for demonstration and testing purposes.

🧰 Additional context used
🧠 Learnings (1)
examples/basics/quickstart/README.md (4)

Learnt from: ptarasiewiczNV
PR: #2027
File: container/deps/vllm/install_vllm.sh:0-0
Timestamp: 2025-07-22T10:22:28.951Z
Learning: The --torch-backend=auto flag works with vLLM installations via uv pip install, even though it's not a standard pip option. This flag is processed by vLLM's build system during installation to automatically match PyTorch distribution with container CUDA versions.

Learnt from: GuanLuo
PR: #1371
File: examples/llm/benchmarks/vllm_multinode_setup.sh:18-25
Timestamp: 2025-06-05T01:46:15.509Z
Learning: In multi-node setups with head/worker architecture, the head node typically doesn't need environment variables pointing to its own services (like NATS_SERVER, ETCD_ENDPOINTS) because local processes can access them via localhost. Only worker nodes need these environment variables to connect to the head node's external IP address.

Learnt from: fsaady
PR: #1730
File: examples/sglang/slurm_jobs/scripts/worker_setup.py:230-244
Timestamp: 2025-07-03T10:14:30.570Z
Learning: In examples/sglang/slurm_jobs/scripts/worker_setup.py, background processes (like nats-server, etcd) are intentionally left running even if later processes fail. This design choice allows users to manually connect to nodes and debug issues without having to restart the entire SLURM job from scratch, providing operational flexibility for troubleshooting in cluster environments.

Learnt from: PeaBrane
PR: #1409
File: examples/router_standalone/worker.py:171-186
Timestamp: 2025-06-08T08:30:45.126Z
Learning: Example code in the examples/ directory may intentionally use hard-coded values or simplified implementations that wouldn't be appropriate for production code, but are acceptable for demonstration and testing purposes.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: Mirror Repository to GitLab
  • GitHub Check: Build and Test - vllm
🔇 Additional comments (2)
examples/basics/quickstart/README.md (2)

14-16: Verify Docker-Compose file path and service coverage

deploy/metrics/docker-compose.yml sounds metrics-specific and may not spin up etcd + NATS. If the compose file under that path only exposes Prometheus/Grafana stacks, the quick-start will fail at runtime.
Double-check that the referenced compose file:

  1. Exists in the repo at that exact path.
  2. Declares etcd and nats (with JetStream enabled).

If not, point to the correct compose file or provide an inline snippet with the required services.


42-44: CLI may be ahead of implementation status

Past discussion (see PR #2046) notes that the v2 UX entry-point python -m dynamo.vllm is planned but not yet wired for vLLM. If users run this today they may hit ModuleNotFoundError.
Consider temporarily documenting the currently-working module path (e.g. python -m dynamo.components.backends.vllm …) or add a note that the short form will land once UX v2 is fully merged.

Copy link
Contributor

@ishandhanani ishandhanani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving to unblock but please address changes before merge

Copy link
Collaborator

@whoisj whoisj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nealvaidya nealvaidya merged commit 195c4c4 into main Jul 29, 2025
10 checks passed
@nealvaidya nealvaidya deleted the nealv/new_hello_world branch July 29, 2025 17:42
python -m dynamo.vllm --model Qwen/Qwen3-0.6B
```

Leave this terminal running - it will show vLLM Backend logs.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it will show vLLM Backend logs

Nice. SDK/serve mixed the logs of all the components, and people were asking to change that, so great to highlight it.

**Open a new terminal** and run:

```bash
python -m dynamo.vllm --model Qwen/Qwen3-0.6B
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should mention that the model will be downloaded from Hugging Face.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants