Hyper-V validation and release architecture
No Management Pack moves directly from authoring to production. Microsoft recommends a pre-production Operations Manager environment for reviewing and tuning new or updated MPs, with version control and archived releases. See Management Pack lifecycle.
Validation layers
Continuous-integration flow
Required lab matrix
| Axis | Minimum fixtures |
|---|---|
| SCOM | Every supported Operations Manager release/update baseline |
| Windows Server | Every supported Hyper-V host release and relevant edition |
| Topology | Standalone, failover cluster, and each accepted SCVMM/SDN variant |
| Networking | Eligible Network ATC, manual networking, and SCVMM/SDN authority |
| Storage | Local, CSV/shared storage, and each accepted SMB/SAN/virtual FC variant |
| VM lifecycle | Create, rename, start, stop, save, pause, checkpoint, move, remove, and restore |
| Cluster lifecycle | Join, drain, pause, failover, node loss, quorum/witness change, and rolling update |
| Monitoring | Agent loss, workflow timeout, access denied, stale data, bad output, and recovery |
| Scale | Empty, typical, supported maximum, and limit-exceeded fixtures |
Research validation defines the exact supported matrix. A topology not represented by a repeatable fixture cannot be listed as supported.
Fault-to-evidence loop
Every threshold and stateful monitor requires both fault and recovery evidence. A test that proves only that an alert opens is incomplete.
Scale budget model
The final support matrix records limits for hosts, clusters, VMs, adapters, disks, relationships, workflow runtime, and collected samples. Crossing a proven limit produces guidance or a pipeline health condition rather than uncontrolled discovery.
Upgrade and removal sequence
Removal can delete configuration and affect monitored data and dependent MPs. It is tested only in an isolated management group and documented accurately; it is not presented as a zero-impact rollback. Microsoft documents dependency and removal constraints in Import, export, and remove an Operations Manager Management Pack.
Release gates
- All proposed Hyper-V ADRs required by the release are accepted.
- The support matrix and monitoring catalog contain evidence for every enabled workflow.
- No unresolved schema, reference, best-practice, security, or secret-scan findings remain.
- Discovery converges correctly for every supported topology and lifecycle transition.
- Health and alerts open, roll up, suppress, recover, and close as designed.
- DA membership, branch health, diagram/state views, reports, dashboards, and SLO targets pass.
- Maximum-scale tests meet approved HealthService, database, and convergence budgets.
- Side-by-side import proves no runtime dependency on Azure Local or Microsoft Hyper-V 2019 MPs.
- Upgrade preserves stable identity and representative customer overrides.
- Separate Discovery and Monitoring override MPs import, export, upgrade, and remove as documented.
- Lab, Standard, and Strict manifests contain valid references for the matching product version and produce the documented effective configuration.
- Static and lab checks prove that no product or test workflow writes customization to the Default Management Pack.
- The release bundle is reproducible and signed only after test artifacts are approved.
- Published docs contain the exact artifact versions, dependencies, known issues, and tuning advice.