Azure Stack Validation as a Service (VaaS) Test Parameters

**THESE PAGES HAVE BEEN DEPRECATED **

PLEASE REFER TO https://docs.microsoft.com/en-us/azure/azure-stack/partner/ Before executing any Test Suite from VaaS, you need to select a Solution and create a Test Pass.

• Log in with your registered VaaS tenant credentials
• Create a new Solution (by clicking Add Solution button) or select any existing
• Then click on the Start button from the Test Passes workflow tile

Note: It is recommended that you create a new Solution entry for a unique machine set/hardware configuration that you are validating and a new Test Pass for every build deployment on that machine set

The Test Pass Information page will prompt for several parameters which are needed by the tests.

Note: you need to supply these parameters only once when starting a new test pass or validation run. Most of the parameters have exactly the same values that were provided when deploying Azure Stack.

While you could enter these values manually using the method described in the below table, an alternative and the recommended approach is to simply upload the deployment configuration file which contains full Azure Stack stamp information. Once uploaded, the values are automatically extracted from the file and populated in the UI.

To generate the configuration file:

• Login to the DVM machine or any machine that has access to the Azure Stack environment
• Open a PowerShell window with Administrator privileges
• Run the following:

$stampInfoPass = ConvertTo-SecureString $CloudAdminPassword -AsPlainText -Force
$stampInfoCreds = New-Object System.Management.Automation.PSCredential($CloudAdminUser, $stampInfoPass)    
$params = Invoke-RestMethod -Method Get -Uri 'https://ASAppGateway:4443/ServiceTypeId/4dde37cc-6ee0-4d75-9444-7061e156507f/CloudDefinition/GetStampInformation' -Credential $stampInfoCreds
ConvertTo-Json $params > stampinfoproperties.json

• Upload stampinfoproperties.json to the portal

Below are the details on the parameters:

For manually locating these values, open the ECE configuration file C:\EceStore\403314e1-d945-9558-fad2-42ba21985248\80e0921f-56b5-17d3-29f5-cd41bf862787 on the DVM machine

Parameter	Description
Azure Stack Build	Azure Stack Build or version number that was deployed (e.g., 1.0.170330.0).
Tenant ID	Azure Active Directory Tenant specified during Azure Stack deployment. Search for AADTenant in the configuration file and select the GUID value in the Id tag.
Region	Azure Stack deployment region. Search for Region in the configuration file.
Tenant Resource Manager	Tenant ARM endpoint (e.g., https://management.<ExternalFqdn>).
Admin Resource Manager	Admin ARM endpoint (e.g., https://adminmanagement.<ExternalFqdn>).
External FQDN	External FQDN of the Environment. Search for ExternalFqdn in the configuration file.
Tenant User	Azure Active Directory Tenant Admin that was either provisioned already or needs to be provisioned by the Service Admin in the AAD Directory. For details on provisioning tenant account see here. This value is used by the test to perform tenant level operations such as deploying templates to provision resources (VMs, storage accounts etc.) and execute workloads.
Service Administrator User	Azure Active Directory Admin of the AAD Directory Tenant specified during Azure Stack deployment. Search for AADTenant in the configuration file and select the value in the UniqueName tag in the configuration file.
Cloud Administrator User	Azure Stack domain administrator account (e.g., contoso\cloudadmin). Search for User Role="CloudAdmin" in the configuration file and select the value in the UserName tag in the configuration file.
Diagnostics Connection String	A SAS URI to an Azure Storage Account to which diagnostics logs will be copied during test execution. Instructions for generating the SAS URI are located here.

Sanity checks before kicking off tests

As mentioned earlier, the tests that get executed perform remote operations. It is therefore crucial that the machine from where the tests are being launched has access to the Azure Stack endpoints. Otherwise the test will be aborted. In case of VaaS On Premise agent this would be the machine where this agent will be running on.

In order to verify that the machine can successfully resolve the addresses, please perform the below steps and ensure they succeed.

Step 1: Resolution of Base URI succeeds

nslookup adminmanagement.<EXTERNALFQDN>

Step 2: Access to MAS Portal succeeds

Open internet browser and navigate to https://adminportal.<EXTERNALFQDN>

Login using the AAD Service Admin Name and Password values provided in the Test Pass Information page.