RnD/infra

Files

znetsixe 2f5e3b4183 feat: SQL=postgres, nginx+certbot, MQTT split, ML stacks, gitea HTTPS-only, gemaal1 site

Round-2 changes locking in scaffold-phase decisions and adding ML/notebook stacks.

Locked decisions
- sql: postgres 16-alpine (was TBD); init.d/ mount for per-app DB provisioning
- nginx-proxy: stock nginx + certbot sidecar (was nginx:alpine TODO).
  Chose stock over nginxproxy/nginx-proxy because stream{} is required for
  MQTT-TLS reverse-proxy on tcp/8883 to rabbitmq:1883.
- gitea: HTTPS-only (DISABLE_SSH=true). No SSH port published.

MQTT split
- Remove stacks/mqtt placeholder.
- Add stacks/rabbitmq — general-purpose broker (AMQP + MQTT plugin),
  used at both cloud and edge. External MQTT clients reach cloud broker
  via nginx stream-proxy on 8883.
- Add stacks/mosquitto — reserved for the FROST (SensorThings) stack
  only. Cloud-only. Internal to its own stack; no external ingress.

ML / notebooks (cloud-only)
- stacks/mlflow — experiment tracking + model registry. Postgres backend
  on sql stack; local volume for artifacts (S3/MinIO is a TODO).
- stacks/jupyterhub — multi-user notebook server. DockerSpawner via
  mounted docker.sock; users spawn into cloud-app network so they can
  reach mlflow, influxdb (via grafana), rabbitmq.

Sites
- sites/gemaal1 — first edge deployment scaffold. Site-local override
  template for binding nginx to PLANT_LAN_IP.

Docs
- README + docs/architecture.md updated: stacks table now lists 15 stacks,
  ingress + attachment tables reflect mlflow/jupyterhub, TLS strategy
  section locked, MQTT-split section added, Gitea HTTPS-only noted.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-21 13:22:46 +02:00

2.2 KiB

Raw Blame History

infra

R&D infrastructure stacks for Waterschap Brabantse Delta. Hub-and-spoke deployment: one cloud central hub + per-plant edge sites.

Layout

infra/
├── stacks/         # reusable, runnable stack defs (kebab-case)
├── cloud/          # the single central hub
├── sites/          # per-plant edge deployments
└── docs/           # architecture + conventions

Stacks are pulled into the cloud and site composes via the Compose Spec include: directive. Each stack is also runnable standalone for testing.

Quick start

# Cloud hub (run on the central server)
cd cloud
cp .env.example .env       # fill in real secrets
docker compose up -d

# A plant edge (run on the edge gateway at the plant)
cd sites/<plant>
cp .env.example .env
docker compose up -d

Stacks

Stack	Purpose	Cloud	Edge
node-red	Flow-based automation	✓	✓
influxdb	Time-series database	✓	✓
grafana	Dashboards / SCADA	✓	✓
keycloak	Identity / SSO	✓	✓
portainer	Container management UI	✓	✓
nginx-proxy	Stock nginx + certbot sidecar	✓	✓
rabbitmq	General-purpose broker (AMQP + MQTT plugin)	✓	✓
postfix	Outbound mail relay	✓	✓
wireguard-server	VPN server	✓	—
wireguard-client	VPN client	—	✓
gitea	Git server (HTTPS-only)	✓	—
jenkins	CI/CD	✓	—
sql	Config DB (postgres 16)	✓	—
mlflow	ML experiment tracking + registry	✓	—
jupyterhub	Multi-user notebook server	✓	—
mosquitto	MQTT broker for FROST stack only	✓	—

Sites

Site	Status
gemaal1	Scaffolded — awaiting hardware provisioning

Design

See docs/architecture.md for the hub-and-spoke topology, 4-network model, ingress table, and the reasoning behind each choice.

Conventions

kebab-case folder names
compose.yml (Compose Spec), not docker-compose.yml
Stack composes pulled into cloud/site via include:
Secrets in .env files (gitignored); .env.example committed with placeholders
OT layer (OPCUA, PLCs) is out of scope for this repo

2.2 KiB Raw Blame History