feat: Python frontend / ingress node

[grahamking]

Before: dynamo-run in=http out=dyn [flags]
After: python -m dynamo.ingress [flags]

No need to build or install the dynamo-run Rust binary. This will have the same performance as dynamo-run, it uses the Rust library.

Note we want to use dynamo.frontend but the older examples still use that namespace. As soon as they are removed we can rename this.

Summary by CodeRabbit

• New Features

  • Introduced a new frontend node that provides an OpenAI-compatible HTTP server with integrated pre-processing and routing capabilities.
  • Added command-line options for customizing HTTP port and cache block size.
  • The frontend node now automatically discovers and registers engines or workers.

• Documentation

  • Added a README with usage instructions and dependency requirements for the new frontend node.

• Chores

  • Updated build configuration to include the new frontend package.

[grahamking]

Replaces #1887

[coderabbitai]

Walkthrough

A new ingress/frontend node component for Dynamo was introduced, including its main Python entry point, supporting module, and documentation. The build configuration was updated to include the new ingress package for wheel distribution. No changes were made to existing code or exported entities outside of the new ingress functionality.

Changes

File(s)	Change Summary
components/ingress/README	Added documentation for the ingress/frontend node, including usage, dependencies, and functionality.
components/ingress/src/dynamo/ingress/main.py	Added entry-point script to launch the ingress node via Python module execution.
components/ingress/src/dynamo/ingress/main.py	Introduced main module for starting the ingress node with argument parsing and async server logic.
pyproject.toml	Updated build configuration to include the new ingress package in wheel targets.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant IngressNode
    participant OpenAI_HTTP_Server
    participant PreProcessor
    participant Router
    participant EngineRegistry

    User->>IngressNode: Run as Python module (optionally specify port)
    IngressNode->>OpenAI_HTTP_Server: Start server on specified port
    OpenAI_HTTP_Server->>PreProcessor: Forward incoming HTTP requests
    PreProcessor->>Router: Pre-process and route requests
    Router->>EngineRegistry: Discover/route to registered engines
    EngineRegistry-->>Router: Return available engine
    Router-->>PreProcessor: Forward request/response
    PreProcessor-->>OpenAI_HTTP_Server: Return response
    OpenAI_HTTP_Server-->>User: Send response

Loading

Poem

In the warren, code hops anew,
Ingress node joins the Dynamo crew!
With servers and routers in perfect sync,
And docs to help you in a blink.
Now wheel builds know just what to do—
Rabbit-approved, this launch is true! 🐇✨

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (1)

components/ingress/src/dynamo/ingress/main.py (1)

44-44: Consider making the runtime debug flag configurable.

The False parameter in DistributedRuntime appears to be a debug flag that's hard-coded. Consider making this configurable via command-line arguments.

Add a debug flag to the argument parser:

+    parser.add_argument(
+        "--debug", action="store_true", help="Enable debug mode."
+    )

And use it in the runtime initialization:

-    runtime = DistributedRuntime(asyncio.get_running_loop(), False)
+    runtime = DistributedRuntime(asyncio.get_running_loop(), flags.get("debug", False))

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6cdda03 and 0d9f959.

📒 Files selected for processing (4)

• components/ingress/README (1 hunks)
• components/ingress/src/dynamo/ingress/__main__.py (1 hunks)
• components/ingress/src/dynamo/ingress/main.py (1 hunks)
• pyproject.toml (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: biswapanda
PR: ai-dynamo/dynamo#1412
File: lib/bindings/python/src/dynamo/runtime/logging.py:100-100
Timestamp: 2025-06-06T21:48:35.214Z
Learning: In the Dynamo codebase, BentoML has been completely removed from all executable code, with only documentation and attribution references remaining. The error_loggers configuration in lib/bindings/python/src/dynamo/runtime/logging.py should not include "bentoml" since those modules no longer exist.

🧬 Code Graph Analysis (1)

components/ingress/src/dynamo/ingress/__main__.py (1)

components/ingress/src/dynamo/ingress/main.py (1)

• main (58-59)

⏰ 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). (4)

• GitHub Check: pre-merge-rust (lib/runtime/examples)
• GitHub Check: pre-merge-rust (lib/bindings/python)
• GitHub Check: pre-merge-rust (.)
• GitHub Check: Build and Test - vllm

🔇 Additional comments (5)

components/ingress/src/dynamo/ingress/__main__.py (1)

4-7: LGTM! Clean entry point implementation.

The entry point follows Python conventions correctly and enables the package to be executed as python -m dynamo.ingress.

pyproject.toml (1)

84-84: LGTM! Correct build configuration update.

The ingress package is properly added to the wheel build targets, following the same path pattern as existing components.

components/ingress/README (1)

1-9: LGTM! Clear and informative documentation.

The README effectively explains the ingress node's purpose, usage, dependencies, and relationship to existing commands.

components/ingress/src/dynamo/ingress/main.py (2)

58-59: LGTM! Correct async event loop setup.

Using uvloop.run() provides better performance than the standard asyncio event loop for this use case.

---

62-63: LGTM! Standard Python main guard pattern.

The main guard follows Python conventions correctly, enabling the module to be executed directly.

[ryanolson]

Do you have a config file?

Should we add that to control the behavior?

I'm thinking we have an all in one config as is currently described.

But also be able to use a different config and multiple instances with different configs to setup individually scalable workers that run each component individually:

• http frontend
• processor (pre/post)
• router

[grahamking]

Do you have a config file?

Should we add that to control the behavior?

This PR aims for feature parity with dynamo-run in=http out=dyn. There aren't enough flags (just 2) to justify a config file.

A big issue with config files in prod is you don't know if the file changed since the process started, so you can never really know what config your process is running with. That is why ops deployments often insist on command line flags.

I'm thinking we have an all in one config as is currently described.

But also be able to use a different config and multiple instances with different configs to setup individually scalable workers that run each component individually:

• http frontend
• processor (pre/post)
• router

If the KVBM project wasn't occupying all our Rust engineers except me, we might even have this already 😝