@colony2/c2j 0.0.51 → 0.0.52
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +14 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -14,6 +14,20 @@ Use it when you want to:
|
|
|
14
14
|
|
|
15
15
|
Examples below assume you are running from the repo root.
|
|
16
16
|
|
|
17
|
+
For execution requirements, actual allocation inputs, compatibility filtering,
|
|
18
|
+
job status, progress, handoffs, and child-job lineage, see the
|
|
19
|
+
[execution tracking user guide](GUIDE-Execution-Tracking.md).
|
|
20
|
+
|
|
21
|
+
Recipes can declare an `execution` block for CPU, memory, scratch, platform,
|
|
22
|
+
and image. Node-level `execution_needs` adds templatable, scoped overrides that
|
|
23
|
+
inherit within a job and restore the parent on exit. Completed tasks replay
|
|
24
|
+
without requesting their historical environments. Pass actual executor facts using individual `--execution-*` flags
|
|
25
|
+
or `C2J_EXECUTION_*` variables. If requirements change or the environment is
|
|
26
|
+
insufficient, execution yields the same job and reports `environment_required`.
|
|
27
|
+
A provisioner can then resume it in a compatible environment; c2j does not
|
|
28
|
+
provision resources itself. Listings show submission/latest-yield requirements
|
|
29
|
+
only for waiting jobs; in-flight needs are not presented as current snapshots.
|
|
30
|
+
|
|
17
31
|
## JobDB upgrade compatibility
|
|
18
32
|
|
|
19
33
|
The typed-route JobDB update requires fresh format-3 databases/artifact storage
|