NVIDIA/ai-cloud-validation v0.8.0

M6 Release

Repository: NVIDIA/ai-cloud-validation

Tag: v0.8.0

Published: 2026-06-15T21:10:46Z

Prerelease: yes

Release notes:

M6'26 - Q2'26

attestation

• Issue #315: SEC22-01: Check that hardware passes nonce check
• Issue #316: SEC22-02: Check that TPM Configuration can be set per host
• Issue #319: ATTEST-XX-02: Check that an updated BIOS is installed on all hardware

Benchmarking

• Issue #249: BM01-02: Verify performance is within 5% of NVIDIA Reference

Capacity-Reservations

• Issue #252: CAP04-01: Verify a set of resources can be logically grouped and pinned to an account
• Issue #253: CAP04-02: Verify atomic allocation of a topology block as a single unit

Compute Services: BMaaS

• Issue #134: SEC21-02: Confirm sanitization on delete - Low Level
• Issue #136: Check the health and status of the DPU on instantiation
• Issue #312: SEC21-04: Verify memory sanitization between tenants

Compute Services: VMaaS

• Issue #313: SEC21-05: Verify SRAM/GPU memory is sanitized between tenants
• Issue #314: SEC21-06: Verify TPM and BIOS are reset during tenant transitions or hardware replacement

enhancement

• Issue #412: [[FEA] Select tests to run or view based on labels](https://github.com/NVIDIA/ai-cloud-validation/issues/412)

Governance-Metrics

• Issue #251: CAP01-01: Query and verify governance API returns Delivered, Healthy, Reserved, and Active metrics for nodes/GPUs

hardware-ingestion

• Issue #133: Makes sure that all hardware under test has been ingested, and matches the provided hardware

image-registry

• Issue #259: CNP09-02: Verify all firmware is cryptographically signed and attested during boot

key-secret-mgmt

• Issue #247: AUTH-XX-02: Spin up an instance which uses a specified key

kubernetes-control-plane

• Issue #267: K8S-XX-08: Verify Cluster Autoscaler integration (upstream)
• Issue #277: K8S26-01: Support multiple clusters in the same tenancy and in the same VPC

network-security

• Issue #287: SDN04-04: Verify IB tenant isolation — compute dedicated to NVIDIA is isolated from other customers
• Issue #288: SDN04-05: Verify IB keys are configured: P_Key, Management Key, Aggregation Management Key, VendorSpecific Key, CongestionControl Key, Node2Node Key, Manager2Node Key
• Issue #310: SEC13-02: Verify insecure protocols (HTTP, SSLv3, TLSv1) are disabled

object-storage-service

• Issue #262: DATASVC-XX-01: Verify S3-compatible API access with authenticated endpoints

sdn-controller

• Issue #284: SDN02-08: Measure and verify policy propagation timing is within acceptable bounds
• Issue #286: SDN02-10: Verify customizable port security policies can be applied to virtual interfaces
• Issue #289: SDN08-01: Verify that storage hosts can route to each other with all-to-all L3 communication

sds-controller

• Issue #263: DMS01-01: Verify a dedicated K8s cluster (or ability to create one) for the data mover stack
• Issue #264: DMS02-01: Verify dedicated CPU nodes are available for data mover with high-performance networking
• Issue #265: DMS03-01: Verify the same filesystem mounted on GPU nodes is accessible from data mover nodes
• Issue #266: DMS05-01: Verify stable egress IP for allowlisting access to NVIDIA services

Unified-Health-APIs

• Issue #254: CAP05-01: Verify per-host health API returns real-time GPU state, thermal status, memory health
• Issue #255: CAP05-02: Verify primitive-level health aggregation (cluster, nodegroup, or reservation level)

Misc

• Issue #459: Rename repo 'ai-cloud-validation' and update documentation

---

Total: 32 items (0 PRs, 32 issues)