NVIDIA / NVIDIA/ai-cloud-validation
Consolidate overlapping HSS10/HSS14 platform-agnostic vs Kubernetes storage tests
Open
@jkenyon-nvidia is already working on this.
Since Jul 22, 2026.
- Dominant language
- Python
- Stars
- 27
- Forks
- 33
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 28
Description
Problem
HSS10 and HSS14 each have two test-plan entries that cover the same behavior at different layers:
| Req | Platform-agnostic | Kubernetes-specific |
|---|---|---|
| HSS10 | HSS10-01 — live filesystem expansion (HssLiveExpansionCheck, storage.yaml) |
HSS10-02 — PVC expansion via CSI (K8sCsiPvcExpandCheck, maps to N-008) |
| HSS14 | HSS14-01 — flock on mounted client (HssFlockMountCheck, storage.yaml) |
HSS14-02 — flock across pods on RWX PVC (K8sFileLockingCheck, maps to N-010) |
The -02 tests are platform/context-sensitive (kubernetes + CSI). The traceability matrix marks both pairs as partial coverage on offtake HSS10/HSS14 and storage N-008/N-010.
PR #542 flagged these as consolidation candidates before v1.0: two implementations of one behavior should not both ship to customers without a clear rule.
Options
- Partition by context — keep both; run
-01in provider-script storage suites and-02only in k8s/storage-acceptance configs; document exclusions so default runs do not double-test. - Consolidate — deprecate one ID per pair (either drop k8s-specific or provider-agnostic where k8s is the only target).
- Clarify scope only — treat offtake HSS10/HSS14 as filesystem capability and N-008/N-010 as k8s acceptance evidence; accept dual traceability but ensure one runs per provider config.
References
docs/test-plan.yaml— HSS10-02, HSS14-02 notesdocs/requirements/test-requirements-matrix.yaml— partial mappings- PR #542
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.