Skip to content

Unified overrides for custom router and orchestrator models#820

Merged
salmanap merged 8 commits intomainfrom
adil/custom_orchestrator
Mar 15, 2026
Merged

Unified overrides for custom router and orchestrator models#820
salmanap merged 8 commits intomainfrom
adil/custom_orchestrator

Conversation

@adilhafeez
Copy link
Copy Markdown
Contributor

@adilhafeez adilhafeez commented Mar 11, 2026

  • Replace separate routing and orchestration config sections with overrides.router_model and overrides.orchestrator_model
  • Add plano provider interface (alias for arch) for self-hosted models
  • Strip provider prefix when resolving model names for upstream requests
  • Update docs, demos, and schema

@adilhafeez adilhafeez changed the title support configurable orchestrator model via orchestration config section Support configurable orchestrator model Mar 11, 2026
@adilhafeez adilhafeez changed the title Support configurable orchestrator model Unified overrides for custom router and orchestrator models Mar 11, 2026
Copy link
Copy Markdown
Contributor

@salmanap salmanap left a comment

Choose a reason for hiding this comment

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

Presume you have tested these changes. Minor comments.

updated_model_providers.append(
{
"name": "plano-orchestrator",
"provider_interface": "arch",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

make this plano/plano-orchestrator

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

updated

hermesllm::ProviderId::try_from(self.to_string().as_str())
// Plano provider uses the same interface as Arch
let provider_str = match self {
LlmProviderType::Plano => "arch",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Just make that plano and create a cluster for it in the envoy config file?

orchestrator_model: plano/katanemo/Plano-Orchestrator-4B

model_providers:
- model: plano/katanemo/Plano-Orchestrator-4B
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

just plano/Plano-Orchestrator is fine.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

thats actually name of the model from hugging face

"name": "plano-orchestrator",
"provider_interface": "arch",
"model": "Plano-Orchestrator",
"model": orchestrator_model_id,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

we should standardize on the model field. I am not sure how the name is different from the model field.

upstream_tls_ca_path:
type: string
description: "Path to the trusted CA bundle for upstream TLS verification. Default is '/etc/ssl/certs/ca-certificates.crt'."
router_model:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

how about llm_routing_model and agent_orchestration_model

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

its more descriptive and better - updating

@salmanap salmanap merged commit bc059ae into main Mar 15, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants