ZTF-Orchestrator

What it demonstrates

The project explores evidence-first infrastructure automation: checking whether a workflow is ready, recording who approved it, showing what ran, and keeping enough evidence for later review. It is explicitly presented as a personal engineering project, not a vendor-supported Nutanix product.

Current evidence

• Public source repository and MIT license.
• Static UI demo for safe inspection without infrastructure access.
• v1.8.4 release baseline with automated Drift Detection policies, scheduled baseline comparisons, run-now policy execution, policy create/edit/enable/pause/delete lifecycle controls, notification targeting metadata, and aligned runtime, demo, appliance, and documentation release markers.
• Sep 22 main-branch evidence fixes drift schedule preset handling after the v1.8.4 release.
• v1.8.3 and v1.8.2 evidence remains visible: Native Foundation Deploy progress visibility, light-theme execution detail readability, Preview badges for ZTF 2.x and NKP areas, provider configuration maturity labels, refreshed documentation screenshots, and updated demo-version evidence.
• Sep 11 main-branch evidence adds Native Foundation deployment gates, Dell XC770 HCI deployment requirements, appliance environment-gate wiring, API tests, enterprise sign-in polish, and a js-yaml security dependency update after the v1.8.1 release.
• Native Foundation Deploy now has first-class operator-facing fields for runner identity, image repository sources, AOS/AHV checksums, Dell iDRAC nodes, Prism Element validation, dry-run evidence, and unsupported-path controls.
• README/dashboard evidence was refreshed on Sep 18, 2026, with clearer demo screenshots, Native Foundation UI cleanup, Dell iDRAC probe-status clarity, Docker build validation, provider maturity labelling, and readable light-theme detail panes before the v1.8.4 drift-policy baseline.
• Workflows 1.x / Workflows 2.x and Scripts 1.x / Scripts 2.x are separated so legacy workflow execution remains distinct from ZTF 2.x plan/apply behavior.
• ZTF 2.x apply and destroy remain approval-bound and require a successful source plan job plus matching plan/input/global/state hashes.
• Native Foundation now has a deeper review-only control model for multi-site planning, provider/topology checks, execution readiness, evidence packs, approval binding, recovery planning, and controlled-UAT gates.
• Dell iDRAC Redfish is represented as a scoped native Foundation provider path, but mutating adapter execution remains disabled unless the required controlled-UAT gates and environment flags are explicitly satisfied.
• Checksum-backed standard, minimal, and air-gapped appliance evidence is available for lab/operator evaluation; it remains separate from any production or vendor-supported appliance claim.
• Dedicated operating workflow case study.