A node's worker label is worker, so a device is only a paired one
- NodeDef `device`/`device_policy` become `worker`/`worker_policy`, the issue `ignored_device` becomes `ignored_worker`, and the SDK's `@node` takes `worker=` and `worker_policy=` - FlowStore._migrate renames the keys in published and draft documents once, bumping their version; a queued run's `needs` reads the old key - placement passes the label as `label`, client regenerated - docs: worker placement wording, MCP issuer without DOMAIN, device rows in the CLI data directory and the API table, device links in compose comments Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
f8011d2a8a
commit
a9d453c9d9
@@ -91,7 +91,7 @@ class SlurmProfile:
|
||||
cpus: int = 1
|
||||
gpus: int = 0
|
||||
ram_mb: int = 0
|
||||
#: What a worker started this way advertises, so a node bound to a device
|
||||
#: What a worker started this way advertises, so a node naming one of them
|
||||
#: can be the reason one is started.
|
||||
labels: list[str] = field(default_factory=list)
|
||||
#: ``#SBATCH`` lines, verbatim: partition, gres, walltime, account.
|
||||
|
||||
Reference in New Issue
Block a user