ores.compute.core
Table of Contents
2. Summary
ores.compute.core manages the compute cluster for ORE risk runs. It maintains
a registry of available compute applications (app, app_version), assigns
batch jobs to available hosts, tracks execution state, and collects results.
Worker nodes running ores.compute.wrapper register themselves and receive
job assignments via NATS; results flow back through the same channel.
3. Inputs
- NATS messages from
ores.compute.wrapperinstances (registration, heartbeat, job completion with result paths). - NATS request messages from UI clients (batch CRUD, host/app queries).
- PostgreSQL connections to
ores_compute_*tables.
4. Outputs
- Batch and result records persisted to the
ores_computeschema. - NATS job-assignment messages dispatched to compute workers.
- NATS response messages returned to callers.
5. Entry points
include/ores.compute.core/ores.compute.hpp— the component's banner header, the same shape every component carries. It declares no symbol.include/ores.compute.core/messaging/registrar.hpp— registers handlers.include/ores.compute.core/service/— app, batch, host, result services.
6. Dependencies
ores.compute.api— shared domain types and NATS protocol schemas.ores.dq— ORM base classes.ores.iam.core— authorisation context.rfl,sqlgen,nats.c.
7. See also
- ores.compute — component group overview.
- ores.compute.api — protocol types and domain entities.
- ores.compute.service — NATS service entrypoint.
- ores.compute.wrapper — worker node that executes ORE runs.
