AutoPlacement
Marks a job as being under AutoManager’s bundle/placement control, and
carries the inputs placement needs. Present iff AutoManager should place
this job; absent means a plain (non-AutoManager) createJob. Wrapping the
requirements this way reads more clearly than a bare optional
requirements field, which a reader could mistake for "no constraints,
place anywhere". Room to grow with future per-job placement policy.
Field |
Type |
Repeated |
Description |
requirements |
|||
target_node |
Hard node pin — the API-only escape hatch for cable-bound hardware. Placement treats it as "this node or nowhere": constraint checks still run against the target, and recovery retries the same node rather than re-placing elsewhere. Label-matched capability requirements are the preferred targeting mechanism; this exists for the cases labels can’t express. |