What is Validation as a Service for Azure Stack Hub?
Validation as a service (VaaS) is a native Azure service designed for solution partners who are co-engineering Azure Stack Hub offerings with Microsoft. Solution partners can use the service to check that their solutions meet Microsoft's requirements and work as expected with Azure Stack Hub.
The primary uses for VaaS are:
- Validating new Azure Stack Hub solutions.
- Validating changes to the Azure Stack Hub software.
- Digitally signing solution partner packages used during deployment.
- Previewing VaaS test collateral.
Validate a new Azure Stack Hub solution
Partners use the Solution Validation workflow to validate new Azure Stack Hub solutions. The solution must pass the required Hardware Lab Kit (HLK) Azure Stack Hub component tests. To certify a range of hardware configurations, the workflow must be run twice for each new solution: once each for the minimum and maximum configurations.
For more information, see Validate a new Azure Stack Hub solution.
Validate changes to the Azure Stack Hub software
Partners use the Package Validation workflow to check that their solution works with the most recent Azure Stack Hub software updates. The Package Validation workflow must be run on a Microsoft-recommended hardware environment where patch and update (P&U) was used to apply the update. It's recommended to also run the workflow on the baseline build.
For more information, see Validate software updates from Microsoft.
Get digitally signed solution partner packages
In addition to validating Azure Stack Hub updates, partners use the Package Validation workflow to validate updates to OEM customization packages. These updates include Azure Stack Hub partner-specific drivers, firmware, and other software used during deployment of the Azure Stack Hub software. Deploy the package you're validating on the current version of the Azure Stack Hub software using at least the minimum-sized solution that will be supported. The package is submitted to VaaS before executing tests. If the tests succeed, notify vaashelp@microsoft.com that the package has completed testing and should be digitally signed with the Azure Stack Hub digital signature. Microsoft signs the package and notifies the Azure Stack Hub partner that the package is available for download in the Azure Stack Hub Validation portal.
For more information, see Validate OEM packages.
Preview VaaS test collateral
Microsoft regularly makes new features available in Azure Stack Hub. As part of the development process for delivering these features to market, new test collateral is made available in the Test Pass workflow. The Test Pass workflow includes test collateral from the other workflows to allow for unofficial test execution. Don't use the Test Pass workflow to submit results for approval. Use the Solution Validation and Package Validation workflows to get official approval for your solution.
For more information, see Quickstart: Use the Azure Stack Hub Validation portal to schedule your first test.
Validation workflow tests summary
| Validation workflow | Required tests |
|---|---|
| New solution validation | Cloud Simulation Engine Compute SDK Operational Suite Disk Identification Test KeyVault Extension SDK Operational Suite KeyVault SDK Operational Suite Network SDK Operational Suite Storage Account SDK Operational Suite |
| OEM package validation | OEM Extension Package Verification Cloud Simulation Engine |
| Monthly update validation | Monthly Azure Stack Hub Update Verification Cloud Simulation Engine |
Next steps
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for