CompTech AIOps - superseded local RAG runtime

Historical note for the first Open WebUI/Ollama RAG experiment, now superseded by the custom AIOps platform architecture.

This page is historical. The first runtime experiment combined Ollama on the host with Open WebUI in Docker. That decision has been superseded.

The current target architecture uses:

a custom portal from day 1;
direct model serving through vLLM or TGI-class runtimes;
LiteLLM as the model gateway;
Qdrant, Postgres, and MinIO for RAG state and objects;
LangGraph, Temporal, OPA, and MCP for governed agent execution.

Open WebUI and Ollama are not target platform components.

Historical Runtime Shape

Component	Runtime	Role
Ollama	Host service	Historical local model serving and embeddings experiment.
Open WebUI	Docker Compose	Historical browser UI and document-upload experiment.
GitHub repo	Git	Desired state, ADRs, changelog, docs, templates, and future deployment definitions.

Historical Compose Intent

The earlier experiment used an Open WebUI Compose service bound to localhost:

services:
  open-webui:
    image: ghcr.io/open-webui/open-webui:main
    container_name: rag-open-webui
    restart: unless-stopped
    ports:
      - "127.0.0.1:3000:8080"
    extra_hosts:
      - "host.docker.internal:host-gateway"
    environment:
      WEBUI_NAME: "ZE Tower RAG"
      WEBUI_AUTH: "true"
      OLLAMA_BASE_URL: "http://host.docker.internal:11434"
      RAG_EMBEDDING_ENGINE: "ollama"
      RAG_EMBEDDING_MODEL: "nomic-embed-text"
      RAG_TOP_K: "5"
      RAG_EMBEDDING_BATCH_SIZE: "4"
    volumes:
      - /srv/rag/open-webui:/app/backend/data
      - /srv/rag/import:/data/import:ro

The important boundary was that Open WebUI was bound to localhost on the host. It was never intended to become the production AIOps portal.

Persistent Paths

Path	Purpose
`/srv/rag/compose.yaml`	Historical Compose file.
`/srv/rag/open-webui`	Preserved legacy Open WebUI data path.
`/srv/rag/import`	Preserved legacy import path.

Decommission Status

The legacy rag-open-webui container was removed from ze-tower after the custom AIOps control plane was deployed and verified. The old data paths were preserved for recoverability pending a separate archive or deletion decision.

The current runtime is documented in Current AIOps architecture and ze-tower deployment.