You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ NVIDIA AI Cluster Runtime (AICR) is a suite of tooling designed to automate the
16
16
|**Component**| A deployable software package (e.g., GPU Operator, Network Operator, cert-manager). Components have versions, Helm sources, and configuration values. |
17
17
|**ComponentRef**| A reference to a component in a recipe, including version, source repository, values file, and dependency references. |
18
18
|**Constraint**| A validation rule in a recipe specifying required system conditions (e.g., `K8s.server.version >= 1.31`, `OS.release.ID == ubuntu`). Constraints can have severity (error/warning), remediation guidance, and units. |
19
-
|**Validation Phase**| A stage of validation in the deployment lifecycle: readiness (infrastructure), deployment (components), performance (system), conformance (workloads). |
19
+
|**Validation Phase**| A stage of validation in the deployment lifecycle: deployment (components), performance (system), conformance (workloads). Readiness constraints are evaluated implicitly before any phase. |
20
20
|**ValidationConfig**| Configuration in a recipe defining phase-specific checks, constraints, expected resources, and node selection for validation. |
21
21
|**Measurement**| A captured data point from the system organized by type (K8s, OS, GPU, SystemD), subtype, and key-value readings. |
22
22
|**Specificity**| A score indicating how specific a recipe's criteria is (number of non-"any" fields). More specific recipes are applied later during merge. |
@@ -449,12 +449,13 @@ Validation can be run in different phases to validate different aspects of the d
449
449
450
450
| Phase | Description | When to Run |
451
451
|-------|-------------|-------------|
452
-
|`readiness`| Evaluates constraints inline against snapshot (K8s version, OS, kernel) — no checks or Jobs | Before deploying any components |
453
452
|`deployment`| Validates component deployment health and expected resources | After deploying components |
454
453
|`performance`| Validates system performance and network fabric health | After components are running |
455
454
|`conformance`| Validates workload-specific requirements and conformance | Before running production workloads |
456
455
|`all`| Runs all phases sequentially with dependency logic | Complete end-to-end validation |
457
456
457
+
> **Note:** Readiness constraints (K8s version, OS, kernel) are always evaluated implicitly before any phase runs. If readiness fails, validation stops before deploying any Jobs.
458
+
458
459
**Phase Dependencies:**
459
460
- Phases run sequentially when using `--phase all`
> **Note:** The `tests` array above is truncated for brevity. A full validation run produces one entry per check across all phases. Each entry includes `stdout` with detailed diagnostic output.
608
+
609
+
**Test Statuses:**
630
610
| Status | Description |
631
611
|--------|-------------|
632
-
| `passed` | Constraint satisfied |
633
-
| `failed` | Constraint not satisfied |
634
-
| `skipped` | Constraint could not be evaluated (missing data, invalid path) |
612
+
|`passed`| Check or constraint passed |
613
+
|`failed`| Check or constraint failed |
614
+
|`skipped`| Check could not be evaluated (missing data, no-cluster mode) |
0 commit comments