Skip to content

Project Bourne v0.8.0 :: Runtime Evidence and Scheduler Coverage

Choose a tag to compare

View all tags
@KozakHou KozakHou released this 25 Aug 09:20
· 11 commits to main since this release
v0.8.0
b0098dc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Project Bourne v0.8.0 — Runtime Evidence and Scheduler Coverage

The release adds first-class IBM LSF discovery and lifecycle support, bounded
execution-scoped runtime evidence, more precise partial/failure semantics, and
optional execution through an already-existing Apptainer/Singularity image.
It preserves the v0.7 control-plane/one-shot-worker architecture and exact argv
boundary.

Architecture delta from v0.7

  • ExecutionRequest v2 adds explicit lsf; released v1 remains readable.
  • SQLite schema 7 persists one versioned runtime-evidence record and
    termination evidence atomically with an execution result.
  • worker-result v3 carries runtime and termination evidence; v1/v2 readers
    remain intact.
  • staged-plan v4 carries current ExecutionRequest v2 payloads and optional
    immutable existing-image execution; v1/v2/v3 are still read without
    reinterpretation.
  • remote-worker v1 is unchanged.

LSF uses bounded queue discovery, stdin bsub submission, exact-ID active
bjobs, recent-finished bjobs -a, durable bhist reconciliation, and
exact-job bkill. Resource mapping is
limited to portable Bourne-owned concepts. Site-specific memory/GPU syntax and
generic LSF expression building are intentionally excluded.

Linux process-tree sampling is local to the execution worker and records
coverage explicitly. macOS and unavailable metrics remain truthful rather
than becoming zeros. GPU visibility is not reported as utilization or proven
scheduler allocation.

Apptainer/Singularity support uses existing local images only. There is no
build, pull, install, registry, Docker-daemon, Kubernetes, or shell-string
execution path. v0.8 does not orchestrate multi-node container launch, choose
MPI-launcher/container ordering, or inject MPI launchers.

Bounded limitations

Live LSF and live Apptainer validation have not yet been performed. Runtime
sampling is execution-scoped and does not automatically aggregate across a
multi-node allocation. Bourne does not inject MPI launchers or automatically
choose container/MPI ordering. Portable LSF memory/GPU resource syntax remains
site-specific and unresolved.

This release adds no Docker requirement, automatic dependency
installation/build, cross-cluster placement, bulk data synchronization,
monitoring daemon, distributed telemetry service, Rust component, or v0.9 work.

See Runtime evidence and scheduler coverage for evidence
semantics, protocol details, and bounded limitations.

Assets 4
Loading