Add Gundi v2 push receiver for ICU and normalized data model

ICU now pushes camera events via a Gundi-v2-compatible API instead of
dropping file triplets into S3. The new gundi-receiver service accepts
them directly, so images are in the system within seconds instead of
waiting out the 90s age gate + poll interval. OCR of the burnt-in camera
timestamp stays mandatory (ICU only sends server times; OCR detects
drifting camera clocks) but now runs asynchronously after ingest.

The push path writes a normalized model that separates what the legacy
metadata table conflates: camera_status (status time series), image
(image properties) and detection (classifications), plus the
image_with_status view as the portal's migration target. A repeatable,
batched migration splits existing metadata/category rows into it.

The legacy poller is unchanged and keeps writing metadata/category until
the portal is switched over.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
dom
2026-09-18 13:54:21 +00:00
co-authored by Claude Opus 5
parent 94bfc60fc4
commit 2fc8dea10c
13 changed files with 1638 additions and 11 deletions
+24
View File
@@ -0,0 +1,24 @@
# nginx-vhost fuer den Gundi-Receiver. Nur HTTP; TLS ergaenzt certbot --nginx.
# ICU muss direkt https:// verwenden: der 80->443-Redirect von certbot ist ein 301
# und wuerde POST in GET verwandeln.
server {
listen 80;
server_name icu.meles.eu;
client_max_body_size 32m; # = gundi.max_request_bytes
location /v2/events {
proxy_pass http://127.0.0.1:8090;
include /etc/nginx/proxy_params;
proxy_read_timeout 60s;
}
location = /healthz {
proxy_pass http://127.0.0.1:8090;
include /etc/nginx/proxy_params;
}
location / {
return 404;
}
}