doru/intelligence-router
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases Wiki Activity

6. LXC fallback chain completion #7

New Issue
Open
opened 2026-06-15 02:48:58 +03:00 by doru · 0 comments
doru commented 2026-06-15 02:48:58 +03:00
Owner
Copy Link

Parent

  • #1 Epic: Model Switching via Sidecar

What to build

Complete the fallback chain: Main PC → OpenRouter → LXC. If OpenRouter credits are exhausted (or OpenRouter is unreachable), the Router falls back to the LXC container on 10.0.4.200.

  • Router — after Sidecar circuit is open AND OpenRouter request fails (402/429/unreachable), falls back to LXC. Full chain: Main PC → OpenRouter → LXC. LXC is static — no switching, no Sidecar.
  • Router — health check for LXC before routing to it.

Acceptance criteria

  • Full fallback chain: Main PC → OpenRouter → LXC
  • OpenRouter failure (402, 429, timeout) → routes to LXC
  • LXC health check before routing
  • All backends unavailable → 503 response
  • Tests: OpenRouter failure triggers LXC fallback, all backends down returns 503

Blocked by

  • #5 (Circuit breaker + OpenRouter fallback)

User stories covered

8

## Parent - #1 Epic: Model Switching via Sidecar ## What to build Complete the fallback chain: Main PC → OpenRouter → LXC. If OpenRouter credits are exhausted (or OpenRouter is unreachable), the Router falls back to the LXC container on 10.0.4.200. - **Router** — after Sidecar circuit is open AND OpenRouter request fails (402/429/unreachable), falls back to LXC. Full chain: Main PC → OpenRouter → LXC. LXC is static — no switching, no Sidecar. - **Router** — health check for LXC before routing to it. ## Acceptance criteria - [ ] Full fallback chain: Main PC → OpenRouter → LXC - [ ] OpenRouter failure (402, 429, timeout) → routes to LXC - [ ] LXC health check before routing - [ ] All backends unavailable → 503 response - [ ] Tests: OpenRouter failure triggers LXC fallback, all backends down returns 503 ## Blocked by - #5 (Circuit breaker + OpenRouter fallback) ## User stories covered 8
doru added the
type:afk
triage:ready
 labels 2026-06-15 02:48:58 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
triage:ready

Ready for AFK agent implementation

  
type:afk

Can be implemented autonomously without human interaction

  
type:hitl

Requires human interaction: architectural decision or design review

No Label
triage:ready
type:afk
type:hitl
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: doru/intelligence-router#7
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?