BundleJobSpec

Field

Type

Description

job_name

string

Unique within the bundle.

requirements

JobRequirements

co_locate_with

string

jobNames in the same replica that MUST land on the same node.

separate_from

string

jobNames in the same replica that MUST land on different nodes.

job

Job

Full job-spec template. At Bundle expansion time Manager derives a per-replica Job by stamping in jobId / state / currentHash / bundleId+replicaIndex+jobName tags; everything else (services, writeFiles, norskMediaVersion, etc.) flows through verbatim. The template’s own requirements field is ignored — requirements above is canonical for placement.

start_mode

string

"auto" (default) — placement runs at bundle creation. "manual" — derived StoredJob entry exists but stays dormant until StartBundleJob activates it. See §10.2 of the design doc. Empty string is treated as "auto" for backward compatibility.