draft

Author: biswapanda

0001-TBD-inference-gw-integration/0001-TBD-inference-gw-integration.md

@@ -0,0 +1,283 @@
+# Dynamo integration with Inference Gateway
+
+**Status**: Draft
+
+**Authors**: [Biswa Panda](https://github.com/biswapanda) 
+
+**Category**: Architecture
+
+**Replaces**: [Link of previous proposal if applicable] 
+
+**Replaced By**: [Link of previous proposal if applicable] 
+
+**Sponsor**: [Name of code owner or maintainer to shepard process]
+
+**Required Reviewers**: [Names of technical leads that are required for acceptance]
+
+**Review Date**: [Date for review]
+
+**Pull Request**: [Link to Pull Request of the Proposal itself]
+
+**Implementation PR / Tracking Issue**: [Link to Pull Request or Tracking Issue for Implementation]
+
+# Summary
+
+This proposal outlines the integration of Dynamo components with the Gateway API Inference Extension. 
+
+The current Inference Gateway is tightly coupled with model's tokenizer. However use cases require:
+1. **External Tokenization**: Preprocessing requests outside the gateway for specialized tokenization logic
+2. **KV-Aware Routing**: Intelligent routing based on prefix cache status and token analysis
+3. **Flexible side channel to offload tokens**: Support for both external cache and direct token passing strategies. This would be helpful for transfering large blob of tokens for VLMs (image/audio/video tokens)
+4. **Unified Dynamo Architecture**: Consolidated deployment model for all processing components
+
+## Terminology & Definitions
+
+| Term | Definition |
+| :---- | :---- |
+| **Dynamo EPP** | Enhanced Endpoint Picker Protocol service with Dynamo integration |
+| **Dynamo Processor** | Dynamo component responsible for request tokenization and preprocessing |
+| **Dynamo Router** | Dynamo component responsible for KV aware Routing strategy |
+| **Token Cache / Side Channel** | External storage system for tokenized request |
+
+## Acronyms & Abbreviations
+
+**EPP:** Endpoint Picker Protocol
+**IGW:** Inference Gateway
+
+## Goals
+
+* Integrate Dynamo Processor for request preprocessing and tokenization
+* Enable KV-aware routing through Dynamo Router Service
+* Support flexible token management (cache keys vs direct values)
+* Provide unified deployment architecture for all Dynamo components
+* Maintain backward compatibility with existing EPP functionality
+
+### Non Goals
+
+* Replace existing EPP internal scheduling completely
+* Modify core Gateway API specifications
+* Change existing worker pod interfaces significantly
+
+## Requirements
+
+### REQ 1 External Processing Integration
+
+Dynamo EPP (Endpoint picker) **MUST** support calling LLM processors for request preprocessing and tokenization while maintaining the existing ext-proc interface.
+
+### REQ 2 Flexible Routing Strategies
+
+The system **SHOULD** support both external routing (via Dynamo Router) and internal EPP scheduling based on request configuration.
+
+### REQ 3 Token offloading capability 
+
+The system **SHOULD** support both external cache-based token storage and direct token value passing to worker pods.
+
+### REQ 4 Unified Dynamo Architecture
+
+Dynamo EPP and components (Processor, Router, Workers) **MUST** be deployable as a unified dynamo graph within Kubernetes.
+
+### REQ 5 Maintain compatibility with Inference Gateway protocols
+
+Dynamo EPP **MUST** be compatible with Inference Gateway
+
+# Proposal
+
+## Architecture Overview
+
+
+The updated architecture unifies Inference Gateway with Dynamo Graph deployment. See [Architecture Diagram](./arch1.png) for detailed component interactions.
+
+## Request Flow Sequence
+
+```mermaid
+sequenceDiagram
+    participant Client
+    participant IGW as Inference Gateway<br/>(Envoy/kGateway)
+    participant EPP as EPP Service<br/>(ext-proc/Endpoint Picker)
+    participant ExtProcessor as (Dynamo) External LLM<br/>Processor
+    participant Router as (Dynamo) Router
+    participant TokenCache as External Token<br/>Cache/Side-channel
+    participant Worker as (Dynamo) Worker<br/>Pod
+
+    Note over Client,Worker: Token Handling & Routing Strategies
+
+    %% Client Request
+    Client->>IGW: POST /v1/chat/completions<br/>{"model": "llama-instruct",<br/> "messages": [...]<br/> }
+
+    IGW->>EPP: ext-proc: RequestHeaders 
+    EPP->>EPP: Parse model name from request<br/>Set X-Gateway-Model-Name header
+    IGW->>EPP: ext-proc: RequestBody
+
+    %% Scenario 1: route=true (External routing via Router Service)
+    alt route=true
+        EPP->>ExtProcessor: POST /process<br/>{"request_body": {<br/>   "model": "llama-instruct",<br/>   "messages": [...],<br/>   "route": true<br/> },<br/> "headers": {"x-request-id": "req-123"}}
+        
+        ExtProcessor->>ExtProcessor: Tokenize prompt (always)<br/>Generate token_ids: [1, 15043, 29892, ...]
+        
+        ExtProcessor->>Router: POST /route<br/>{"token_ids": [1, 15043, 29892, ...]}
+        
+        Router->>Router: Apply KV aware routing:<br/>- Check prefix cache<br/>- Apply custom routing strategy<br/>- Select optimal worker
+        
+        Router-->>ExtProcessor: Worker selection:<br/>{"worker_address": "worker-3:8080"}
+        
+        %% Token storage decision
+        alt Using External Cache
+            ExtProcessor->>TokenCache: Store tokens<br/>Key: "cache_key_abc123"<br/>Value: [1, 15043, 29892, ...]
+            
+            ExtProcessor-->>EPP: Response with token_key:<br/>{"worker_address": "worker-3:8080",<br/> "token_key": "cache_key_abc123"}
+            
+            EPP->>EPP: Set x-gateway-destination-endpoint: "worker-3:8080"<br/>Set routing metadata
+            EPP->>EPP: Prepare headers:<br/>x-req-tokens-key: "cache_key_abc123"
+            
+        else Direct Token Values
+            ExtProcessor-->>EPP: Response with token_value:<br/>{"worker_address": "worker-2:8080",<br/> "token_value": "[1,15043,29892,...]"}
+            
+            EPP->>EPP: Set x-gateway-destination-endpoint: "worker-2:8080"<br/>Set routing metadata
+            EPP->>EPP: Modify request body:<br/>Add "token_ids": [1,15043,29892,...]
+        end
+        
+    %% Scenario 2: route not specified (Internal routing)
+    else route not specified
+        Note over EPP: EPP schedules worker pods<br/>using internal logic
+        
+        EPP->>ExtProcessor: POST /process<br/>{"request_body": {<br/>   "model": "llama-instruct",<br/>   "messages": [...]<br/> },<br/> "headers": {"x-request-id": "req-123"}}
+        
+        ExtProcessor->>ExtProcessor: Tokenize prompt (always)
+        
+        %% Allow external cache for internal routing too
+        alt Store in External Cache
+            ExtProcessor->>TokenCache: Store tokens<br/>Key: "cache_key_xyz789"<br/>Value: [1, 15043, 29892, ...]
+            
+            ExtProcessor-->>EPP: Response with token_key:<br/>{"token_key": "cache_key_xyz789"}
+            
+            EPP->>EPP: Schedule worker pods:<br/>- Apply internal scheduling<br/>- Check pod availability<br/>- Select: worker-pool-1:8080
+            
+            EPP->>EPP: Set x-gateway-destination-endpoint: "worker-pool-1:8080"<br/>Set routing metadata
+            EPP->>EPP: Prepare headers:<br/>x-req-tokens-key: "cache_key_xyz789"
+            
+        else Direct Token Values
+            ExtProcessor-->>EPP: Response with tokens:<br/>{"token_value": "[1,15043,29892,...]"}
+            
+            EPP->>EPP: Schedule worker pods:<br/>- Apply internal scheduling<br/>- Select: worker-pool-1:8080
+            
+            EPP->>EPP: Set x-gateway-destination-endpoint: "worker-pool-1:8080"<br/>Set routing metadata
+            EPP->>EPP: Modify request body:<br/>Add "token_ids": [1,15043,29892,...]
+        end
+    end
+
+    EPP-->>IGW: ext-proc Response<br/>Header: x-gateway-destination-endpoint<br/>Header: x-req-tokens-key (if using cache)<br/>Modified request body (if direct tokens)
+
+    %% Request forwarding
+    IGW->>Worker: HTTP Request to selected worker<br/>Header: x-gateway-destination-endpoint<br/>Header: x-req-tokens-key (if applicable)<br/>Body: includes token_ids (if direct)
+
+    alt Worker receives token_key in header
+        Worker->>TokenCache: Fetch tokens<br/>Key from header: x-req-tokens-key
+        TokenCache-->>Worker: Token array: [1,15043,29892,...]
+    else Worker receives token_ids in body
+        Worker->>Worker: Use token_ids directly<br/>from request body
+    end
+
+    Worker->>Worker: LLM Inference with tokens
+    Worker-->>IGW: Response<br/>{"choices": [...], "usage": {...}}
+
+    IGW-->>Client: Final Response
+```
+
+# Implementation Details
+
+## Key Components
+
+### Dynamo EPP (ext-proc)
+- Integrates with Gateway via ext-proc protocol
+- Parses model names and sets `X-Gateway-Model-Name` header
+- Calls External LLM Processor for tokenization
+- Handles both external and internal routing strategies
+- Manages token key/value header and body modifications
+
+### Dynamo Processor
+- Performs request tokenization
+- Supports both routing modes (external via Router, internal via EPP)
+- Manages token transfer strategies (cache vs direct)
+- Returns worker selection and dynamo backend framework (vLLM/Trtllm/sglang) agnostic request 
+
+### Dynamo Router Service
+- Implements KV-aware routing algorithms
+- Analyzes token_ids for optimal worker selection based on prefix cache
+- Called only when `route=true` is specified
+
+### Dynamo Worker Pods
+- Perform LLM inference with preprocessed tokens
+- Support both token retrieval methods (cache keys, direct values)
+- Maintain compatibility with existing worker interfaces
+- exposes HTTP endpoint for direct intgerration with Inference gateway
+
+### Token Cache / Side channel
+- External storage system which provides a Key/Value store interface transfer token_ids from processor to worker
+- Stores tokenized data with generated keys
+- Enables efficient token sharing between components
+- Optional component (direct token passing also supported)
+
+## Configuration
+
+### Environment Variables
+- `EXTERNAL_LLM_PROCESSOR_ENDPOINT`: Dynamo External LLM Processor URL
+- `USE_EXTERNAL_LLM_PROCESSOR`: Enable/disable external pre-processing (apply prompt templates/tokenization)
+- `USE_EXTERNAL_LLM_ROUTER`: Enable/disable external routing (in this case it's Dynamo Router)
+
+### Headers
+- `X-Gateway-Model-Name`: Set by EPP from parsed model name in user request's body
+- `x-req-tokens-key`: Token cache key (when using external cache)
+- `x-req-tokens-value`: Direct token values (alternative to cache)
+
+## Deferred to Implementation
+
+- Specific token cache implementation details (Redis vs alternatives)
+- Fallback mechanisms for external service failures
+- Metrics and observability integration
+
+# Implementation Phases
+
+## Phase 1 Core Integration
+**Supported API / Behavior:**
+- External tokenization via Dynamo Processor
+- External scheduling/routiung using Dynamo Router
+- Direct token value passing to workers
+
+**Not Supported:**
+- External cache-based token passing 
+
+## Phase 2 Tokens transfer thrugh side channel/cache
+**Supported API / Behavior:**
+- External cache-based token passing 
+
+# Related Proposals
+* Gateway API Inference Extension Architecture
+* EPP Architecture Proposal 
+* Model Server Protocol
+
+# Alternate Solutions
+
+## Alt 1 Direct Tokenizer Integration in EPP (current EPP architecture)
+
+**Pros:**
+- Simpler architecture without additional layer
+- Lower latency for request processing
+- Fewer network hops
+
+**Cons:**
+- Less flexible for different models
+- Harder to maintain separation of concerns
+
+**Reason Rejected:**
+- Violates Gateway API integration principles
+- Reduces portability across models
+- Increases complexity/TCO by using golang based tokenizer
+
+## Alt 2 Sidecar Pattern
+- TODO
+
+## References
+
+* [Gateway API Inference Extension Documentation](https://gateway-api-inference-extension.sigs.k8s.io/)
+* [Envoy External Processing Filter](https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/ext_proc_filter)
+* [Gateway API Specification](https://gateway-api.sigs.k8s.io/)