more rename

This commit is contained in:
Adil Hafeez 2025-12-23 18:19:20 -08:00
parent d7da8eca6f
commit 8eb0dbc538
No known key found for this signature in database
GPG key ID: 9B18EF7691369645
26 changed files with 51 additions and 51 deletions

View file

@ -18,7 +18,7 @@ services:
extra_hosts:
- "host.docker.internal:host-gateway"
volumes:
- ./config.yaml:/app/config.yaml
- ./config.yaml:/app/arch_config.yaml
jaeger:
build:

View file

@ -20,7 +20,7 @@ start_demo() {
# Step 3: Start Arch
echo "Starting Arch with config.yaml..."
archgw up config.yaml
plano up config.yaml
# Step 4: Start developer services
echo "Starting Network Agent using Docker Compose..."
@ -35,7 +35,7 @@ stop_demo() {
# Step 2: Stop Arch
echo "Stopping Arch..."
archgw down
plano down
}
# Main script logic

View file

@ -10,7 +10,7 @@ services:
extra_hosts:
- "host.docker.internal:host-gateway"
volumes:
- ./config.yaml:/app/config.yaml
- ./config.yaml:/app/arch_config.yaml
jaeger:
build:

View file

@ -20,7 +20,7 @@ start_demo() {
# Step 3: Start Arch
echo "Starting Arch with config.yaml..."
archgw up config.yaml
plano up config.yaml
# Step 4: Start developer services
echo "Starting Network Agent using Docker Compose..."
@ -35,7 +35,7 @@ stop_demo() {
# Step 2: Stop Arch
echo "Stopping Arch..."
archgw down
plano down
}
# Main script logic

View file

@ -21,4 +21,4 @@ services:
extra_hosts:
- "host.docker.internal:host-gateway"
volumes:
- ./config.yaml:/app/config.yaml
- ./config.yaml:/app/arch_config.yaml

View file

@ -20,7 +20,7 @@ start_demo() {
# Step 3: Start Arch
echo "Starting Arch with config.yaml..."
archgw up config.yaml
plano up config.yaml
# Step 4: Start Network Agent
echo "Starting HR Agent using Docker Compose..."
@ -35,7 +35,7 @@ stop_demo() {
# Step 2: Stop Arch
echo "Stopping Arch..."
archgw down
plano down
}
# Main script logic

View file

@ -10,7 +10,7 @@ services:
extra_hosts:
- "host.docker.internal:host-gateway"
volumes:
- ./config.yaml:/app/config.yaml
- ./config.yaml:/app/arch_config.yaml
jaeger:
build:

View file

@ -20,7 +20,7 @@ start_demo() {
# Step 3: Start Arch
echo "Starting Arch with config.yaml..."
archgw up config.yaml
plano up config.yaml
# Step 4: Start developer services
echo "Starting Network Agent using Docker Compose..."
@ -35,7 +35,7 @@ stop_demo() {
# Step 2: Stop Arch
echo "Stopping Arch..."
archgw down
plano down
}
# Main script logic

View file

@ -20,7 +20,7 @@ services:
extra_hosts:
- "host.docker.internal:host-gateway"
volumes:
- ./config.yaml:/app/config.yaml
- ./config.yaml:/app/arch_config.yaml
otel-collector:
build:

View file

@ -20,7 +20,7 @@ services:
extra_hosts:
- "host.docker.internal:host-gateway"
volumes:
- ./config.yaml:/app/config.yaml
- ./config.yaml:/app/arch_config.yaml
jaeger:
build:

View file

@ -20,7 +20,7 @@ services:
extra_hosts:
- "host.docker.internal:host-gateway"
volumes:
- ./config.yaml:/app/config.yaml
- ./config.yaml:/app/arch_config.yaml
otel-collector:
build:

View file

@ -23,7 +23,7 @@ services:
extra_hosts:
- "host.docker.internal:host-gateway"
volumes:
- ./config.yaml:/app/config.yaml
- ./config.yaml:/app/arch_config.yaml
prometheus:
build:

View file

@ -20,4 +20,4 @@ services:
extra_hosts:
- "host.docker.internal:host-gateway"
volumes:
- ./config.yaml:/app/config.yaml
- ./config.yaml:/app/arch_config.yaml

View file

@ -74,7 +74,7 @@ start_demo() {
# Step 4: Start Arch
echo "Starting Arch with config.yaml..."
archgw up config.yaml
plano up config.yaml
# Step 5: Start Network Agent with the chosen Docker Compose file
echo "Starting Network Agent with $COMPOSE_FILE..."
@ -93,7 +93,7 @@ stop_demo() {
# Stop Arch
echo "Stopping Arch..."
archgw down
plano down
}
# Main script logic

View file

@ -28,8 +28,8 @@ Once the config file is created ensure that you have env vars setup for `MISTRAL
Start arch gateway,
```
$ archgw up config.yaml
2024-12-05 11:24:51,288 - cli.main - INFO - Starting archgw cli version: 0.1.5
$ plano up config.yaml
2024-12-05 11:24:51,288 - cli.main - INFO - Starting plano cli version: 0.4.0
2024-12-05 11:24:51,825 - cli.utils - INFO - Schema validation successful!
2024-12-05 11:24:51,825 - cli.main - INFO - Starting arch model server and arch gateway
...

View file

@ -20,7 +20,7 @@ start_demo() {
# Step 3: Start Arch
echo "Starting Arch with config.yaml..."
archgw up config.yaml
plano up config.yaml
# Step 4: Start LLM Routing
echo "Starting LLM Routing using Docker Compose..."
@ -35,7 +35,7 @@ stop_demo() {
# Step 2: Stop Arch
echo "Stopping Arch..."
archgw down
plano down
}
# Main script logic

View file

@ -1,6 +1,6 @@
# RAG Agent Demo
A multi-agent RAG system demonstrating archgw's agent filter chain with MCP protocol.
A multi-agent RAG system demonstrating plano's agent filter chain with MCP protocol.
## Architecture
@ -46,9 +46,9 @@ This starts:
- Context Builder MCP server on port 10502
- RAG Agent REST server on port 10505
### 2. Start archgw
### 2. Start plano
```bash
archgw up --foreground
plano up --foreground
```
### 3. Test the system
@ -82,7 +82,7 @@ filters:
## How It Works
1. User sends request to archgw listener on port 8001
1. User sends request to plano listener on port 8001
2. Request passes through MCP filter chain:
- **Input Guards** validates the query is within TechCorp's domain
- **Query Rewriter** rewrites the query for better retrieval
@ -113,7 +113,7 @@ curl -X POST http://localhost:8001/v1/chat/completions \
]
}'
```
- `LLM_GATEWAY_ENDPOINT` - archgw endpoint (default: `http://localhost:12000/v1`)
- `LLM_GATEWAY_ENDPOINT` - lpano endpoint (default: `http://localhost:12000/v1`)
- `OPENAI_API_KEY` - OpenAI API key for model providers
## Additional Resources

View file

@ -22,7 +22,7 @@ services:
- ARCH_CONFIG_PATH=/config/config.yaml
- OPENAI_API_KEY=${OPENAI_API_KEY:?OPENAI_API_KEY environment variable is required but not set}
volumes:
- ./config.yaml:/app/config.yaml
- ./config.yaml:/app/arch_config.yaml
- /etc/ssl/cert.pem:/etc/ssl/cert.pem
jaeger:
build:

View file

@ -1,6 +1,6 @@
# Model Choice Newsletter Demo
This folder demonstrates a practical workflow for rapid model adoption and safe model switching using Arch Gateway (`archgw`). It includes both a minimal test harness and a sample proxy configuration.
This folder demonstrates a practical workflow for rapid model adoption and safe model switching using Arch Gateway (`plano`). It includes both a minimal test harness and a sample proxy configuration.
---
@ -34,13 +34,13 @@ fixtures:
#### 2. Candidate Models
List the model aliases (e.g., `arch.summarize.v1`, `arch.reason.v1`) you want to test. The harness will route requests through `archgw`, so you dont need provider API keys in your code.
List the model aliases (e.g., `arch.summarize.v1`, `arch.reason.v1`) you want to test. The harness will route requests through `plano`, so you dont need provider API keys in your code.
#### 3. Minimal Python Harness
See `bench.py` for a complete example. It:
- Loads fixtures.
- Sends requests to each candidate model via `archgw`.
- Sends requests to each candidate model via `plano`.
- Validates output against schema and anchor words.
- Reports success rate and latency.
@ -60,7 +60,7 @@ python bench.py
### Part 2 — Network Infrastructure
**Goal:** Use a proxy server (`archgw`) to decouple your app from vendor-specific model names and centralize control.
**Goal:** Use a proxy server (`plano`) to decouple your app from vendor-specific model names and centralize control.
#### Why Use a Proxy?
@ -108,12 +108,12 @@ See `config.yaml` for a sample configuration mapping aliases to provider models.
- `bench.py` — Minimal Python test harness
- `evals_summarize.yaml` — Example test fixtures
- `pyproject.toml` — Poetry environment file
- `config.yaml` — Sample archgw config (if present)
- `config.yaml` — Sample plano config (if present)
---
## Troubleshooting
- If you see `Success: 0/2 (0%)`, check your anchor words and prompt clarity.
- Make sure archgw is running and accessible at `http://localhost:12000/`.
- Make sure plano is running and accessible at `http://localhost:12000/`.
- For schema validation errors, ensure your prompt instructs the model to output the correct JSON structure.

View file

@ -10,7 +10,7 @@ services:
extra_hosts:
- "host.docker.internal:host-gateway"
volumes:
- ./config.yaml:/app/config.yaml
- ./config.yaml:/app/arch_config.yaml
jaeger:
build:

View file

@ -10,7 +10,7 @@ services:
extra_hosts:
- "host.docker.internal:host-gateway"
volumes:
- ./config.yaml:/app/config.yaml
- ./config.yaml:/app/arch_config.yaml
otel-collector:
build:

View file

@ -20,7 +20,7 @@ start_demo() {
# Step 3: Start Arch
echo "Starting Arch with config.yaml..."
archgw up config.yaml
plano up config.yaml
# Step 4: Start developer services
echo "Starting Network Agent using Docker Compose..."
@ -35,7 +35,7 @@ stop_demo() {
# Step 2: Stop Arch
echo "Stopping Arch..."
archgw down
plano down
}
# Main script logic

View file

@ -3,7 +3,7 @@ This demo shows how you can use user preferences to route user prompts to approp
## How to start the demo
Make sure your machine is up to date with [latest version of archgw]([url](https://github.com/katanemo/archgw/tree/main?tab=readme-ov-file#prerequisites)). And you have activated the virtual environment.
Make sure your machine is up to date with [latest version of plano]([url](https://github.com/katanemo/plano/tree/main?tab=readme-ov-file#prerequisites)). And you have activated the virtual environment.
1. start the openwebui
@ -11,15 +11,15 @@ Make sure your machine is up to date with [latest version of archgw]([url](https
(venv) $ cd demos/use_cases/preference_based_routing
(venv) $ docker compose up -d
```
2. start archgw in the foreground
2. start plano in the foreground
```bash
(venv) $ archgw up --service archgw --foreground
2025-05-30 18:00:09,953 - cli.main - INFO - Starting archgw cli version: 0.4.0
(venv) $ plano up --service plano --foreground
2025-05-30 18:00:09,953 - cli.main - INFO - Starting plano cli version: 0.4.0
2025-05-30 18:00:09,953 - cli.main - INFO - Validating /Users/adilhafeez/src/intelligent-prompt-gateway/demos/use_cases/preference_based_routing/config.yaml
2025-05-30 18:00:10,422 - cli.core - INFO - Starting arch gateway, image name: archgw, tag: katanemo/plano:0.4.0
2025-05-30 18:00:10,662 - cli.core - INFO - archgw status: running, health status: starting
2025-05-30 18:00:11,712 - cli.core - INFO - archgw status: running, health status: starting
2025-05-30 18:00:12,761 - cli.core - INFO - archgw is running and is healthy!
2025-05-30 18:00:10,422 - cli.core - INFO - Starting arch gateway, image name: plano, tag: katanemo/plano:0.4.0
2025-05-30 18:00:10,662 - cli.core - INFO - plano status: running, health status: starting
2025-05-30 18:00:11,712 - cli.core - INFO - plano status: running, health status: starting
2025-05-30 18:00:12,761 - cli.core - INFO - plano is running and is healthy!
...
```

View file

@ -10,7 +10,7 @@ services:
extra_hosts:
- "host.docker.internal:host-gateway"
volumes:
- ./config.yaml:/app/config.yaml
- ./config.yaml:/app/arch_config.yaml
jaeger:
build:

View file

@ -20,7 +20,7 @@ start_demo() {
# Step 3: Start Arch
echo "Starting Arch with config.yaml..."
archgw up config.yaml
plano up config.yaml
# Step 4: Start developer services
echo "Starting Network Agent using Docker Compose..."
@ -35,7 +35,7 @@ stop_demo() {
# Step 2: Stop Arch
echo "Stopping Arch..."
archgw down
plano down
}
# Main script logic

View file

@ -39,7 +39,7 @@ cd ../../
plano build
cd -
# Once we build archgw we have to install the dependencies again to a new virtual environment.
# Once we build plano we have to install the dependencies again to a new virtual environment.
poetry install
log startup arch gateway with function calling demo