Svc-db-qdrant Role¶

Description: Central vector database engine for storing and searching per-consumer embeddings shared across the stack

Variables¶

author: Kevin Veen-Birkenbach
description: Central vector database engine for storing and searching per-consumer embeddings shared across the stack
license: Infinito.Nexus Community License (Non-Commercial)
company: Kevin Veen-Birkenbach https://www.veen.world
min_ansible_version: 2.9
platforms: [{‘name’: ‘ArchLinux’, ‘versions’: [‘all’]}, {‘name’: ‘Debian’, ‘versions’: [‘all’]}, {‘name’: ‘EL’, ‘versions’: [‘all’]}, {‘name’: ‘Fedora’, ‘versions’: [‘all’]}, {‘name’: ‘Ubuntu’, ‘versions’: [‘all’]}]
galaxy_tags: [‘qdrant’, ‘docker’, ‘database’, ‘vector’, ‘central-database’]
issue_tracker_url: https://s.infinito.nexus/issues

README¶

Qdrant¶

Description¶

This Ansible role deploys and configures a Qdrant vector database in a Docker container using Docker Compose. It runs Qdrant as a central, pinned engine that many application roles share over the cross-stack network, keeping the consumer roles stateless and NFS-shareable in swarm.

Overview¶

Built for environments that demand reliability and ease of management, this role:

Sets up a dedicated Docker network for Qdrant.
Deploys a Qdrant container with secure configurations and an HTTP readiness healthcheck.
Provides a connection lookup (engine) so consumers resolve the central instance and their own per-consumer collection prefix.

Cosmos¶

The diagram places Qdrant in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).

flowchart LR
    subgraph deps [Dependencies]
        dep_svc_bkp_volume_2_local["svc-bkp-volume-2-local 💻"]
        dep_svc_net_tor["svc-net-tor 🐳🐝"]
        dep_web_app_flowise["web-app-flowise 🐳🐝"]
        dep_web_app_hermes["web-app-hermes 🐳🐝"]
        dep_web_app_openclaw["web-app-openclaw 🐳🐝"]
        dep_web_app_openwebui["web-app-openwebui 🐳🐝"]
    end
    subgraph role [svc-db-qdrant 🐳🐝]
        svc_qdrant["qdrant"]
        svc_qdrantmcp["qdrantmcp"]
        svc_tor["tor"]
        svc_container_backup["container_backup"]
        svc_openwebui["openwebui"]
        svc_hermes["hermes"]
        svc_openclaw["openclaw"]
        svc_flowise["flowise"]
    end
    subgraph dependents [Dependents]
        dpt_web_app_flowise["web-app-flowise 🐳🐝"]
    end
    dep_svc_bkp_volume_2_local -. "0..1" .-> svc_container_backup
    dep_svc_net_tor -. "0..1" .-> svc_tor
    dep_web_app_flowise -. "0..1" .-> svc_flowise
    dep_web_app_hermes -. "0..1" .-> svc_hermes
    dep_web_app_openclaw -. "0..1" .-> svc_openclaw
    dep_web_app_openwebui -. "0..1" .-> svc_openwebui
    svc_qdrant -. "0..1" .-> dpt_web_app_flowise

Solid 1:1 edges are fixed relationships; dashed 0..1 edges are conditional (enabled only in matching deployments); red 0..0 edges are turned off in this role. Node markers show the role’s deploy modes (💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly turned off, and ⚙️ an Ansible role dependency declared in meta/main.yml.

Purpose¶

The purpose of this role is to provide an effortless way to deploy a Qdrant vector database via Docker. It minimizes manual interventions while ensuring that the engine is configured securely and reliably for both production and development scenarios.

Features¶

Automated Deployment: Installs Qdrant with minimal manual steps.
Central Engine: A single pinned stack shared by many consumers, mirroring the central database roles.
Per-Consumer Isolation: OSS Qdrant has no per-user auth; each consumer is isolated by the collection-name prefix {entity}_.
Enhanced Security: The service is bound to 127.0.0.1:6333, restricting access and enhancing security.
Seamless Docker Integration: Works harmoniously with Docker Compose and other roles in your infrastructure.

Quick Setup¶

Development¶

Clone, set up the workstation, and deploy Qdrant onto the local stack:

git clone https://github.com/infinito-nexus/core.git
cd core
make onboard
make compose-deploy mode=reinstall apps=svc-db-qdrant full_cycle=false

Production¶

Run the published image to provision the inventory and deploy Qdrant to a managed server (the mounted volume persists the inventory):

APP=svc-db-qdrant
HOST=<your-server>
DOMAIN=<your-domain>
TLS_MODE=self_signed
SSH_PUBLIC_KEY="<your-ssh-public-key>"

docker run --rm -it \
  -v "$PWD/inventories:/etc/infinito.nexus/inventories" \
  -e APP="$APP" -e HOST="$HOST" -e DOMAIN="$DOMAIN" -e TLS_MODE="$TLS_MODE" -e SSH_PUBLIC_KEY="$SSH_PUBLIC_KEY" \
  ghcr.io/infinito-nexus/core/debian bash -c '
    INVENTORY=/etc/infinito.nexus/inventories/production
    infinito administration inventory provision "$INVENTORY" \
      --inventory-file "$INVENTORY/devices.yml" \
      --host "$HOST" \
      --include "$APP" \
      --vars "{\"TLS_MODE\": \"$TLS_MODE\", \"DOMAIN_PRIMARY\": \"$DOMAIN\", \"users\": {\"administrator\": {\"authorized_keys\": [\"$SSH_PUBLIC_KEY\"]}}}" &&
    infinito administration deploy dedicated "$INVENTORY/devices.yml" \
      --password-file "$INVENTORY/.password" \
      --diff -vv'

Credits¶

Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).