Replies: 1 comment
|
Hi @mchmarny thanks for reaching out, seems like a good fit between projects, I'll ask @jkenyon-nvidia to set up a meeting. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi team 👋
I'm a maintainer on NVIDIA/aicr (AI Cluster Runtime). I came across ai-cloud-validation and was intrigued by it — the provider-agnostic stub model, the breadth of checks (NCCL, NVLink, InfiniBand, NIM, BMC/Redfish posture, Slurm + K8s workloads), and the requirements-driven test plan are exactly the kind of real-hardware validation the ecosystem needs.
A bit about AICR
AICR generates and validates GPU-accelerated Kubernetes configurations (Snapshot → Recipe → Validate → Bundle). Alongside the recipe workflow, we've built a general-purpose trust substrate: every artifact we emit gets a signed, tamper-evident, offline-verifiable attestation using Sigstore keyless signing + Fulcio + Rekor + in-toto/DSSE, with a content-addressed manifest and a small pointer file committed to the repo (so
git logis the audit trail). It answers three questions about any artifact — where it came from (provenance), whether it actually worked on real hardware (validity), and whether it's been altered (falsification).Where I see complementarity
We seem to sit on the same axis from different ends: ACV runs a broad, deep library of real-hardware validation checks, while AICR provides a cryptographic trust and portability layer for validation results. A few areas that might be worth exploring together:
Just wanted to make sure you're aware of the trust primitives we've built (all OSS, reusable independent of AICR), and see if any of the above resonates. Happy to jam on a call, share a short design sketch, or prototype something if useful.
Either way — nice work on this. 🙌
Mark
github.com/NVIDIA/aicr
All reactions