[Deprecated] Onboard a new VM machine as MSAI UDP Test Agent
The MSAI UDP Pool has been migrated to the 1ES Hosted Pool. So, this page has been deprecated. Please check the latest page about the MSAIUDP-Pool_Azr.
Background
We have setup a new Agent Pool (MSAI UDP-Pool) for the new data cooking pipeline codebase. This agent pool is configured in the Azure build pipeline (yaml) in the new code repository - DM.Auriga.Impression. Due to the high duration for each build job triggered by pull requests, we suggest that you can onboard your private virtual machine onto our Agent Pool.
Proposal
For the improvement of the development agility, we can increase the number of the Agent Pool machine. The member for developing the data cooking pipeline can add their private virtual machine into Agent Pool and execute the buddybuild pipeline more flexibly. We have a public uninterrupted agent(MSAIUDPAGENT) from Torus Azure Subscription as master agent. Your machine could be just online when you need it.
Onboarded Agent Machine list
| Agent Name | Owner | Category | Remark |
|---|---|---|---|
| UDP-Azr01 | MSAI Data Platform Azure Subscription | Public Azure VM | 24hours Online |
| Dev-zhxin-vm-549 | zhxin@microsoft.com | Personal VM | Business hour Online |
| Dev-lishengq-vm-MININT-9B9TNS1 | lishengq@micorosoft.com | Personal Physical Machine | User Control |
| Dev-dechen-vm-stcac-212 | dechen@microsoft.com | Personal VM | Business hour Online |
Prerequisites
Permission
- MSAI Data Platform DRI is the administrator of the MSAI UDP-Pool, contact this alias if you have no permission.
Virtual Machine environment
- Visual Studio 2019 Download
- .NET Framework 3.5 (Used for Bond.NET 3.0.67 package) Download
- .NET Framework >4.7.2 Runtime Download
- Note: Your VM machine system time zone should be PST(UTC-08:00 Pacific Time (US & Canada)) time
Onboard Steps
Step1: Setup System Environment Variable
We need to invoke the System Account Credential to access the Cosmos. So we need to add a new Environment variable UseSystemAccount and its value should be true.
Step2: Create the new Windows Credential
The Cosmos E2E test access the windows system credential via Credential Manager. Add these neccessary Windows Credentials in Generic Credentials section.
- Contact MSAI Data Platform DRI member to check the Credential settings.
- Contact xinqia@microsoft.com or niliao@microsoft.com to check the Credential password.
| Internet or Network Address | User name |
|---|---|
| CosmosSystemAccount | ssssqi@microsoft.com |
| aeexo | aeexo@microsoft.com |
Step3: Onboard virtual machine to Agent Pool
Prepare permissions
Follow this link, create PAT and check if you have valid permission ready for setup the agent. Note and Save this token!
Get the agent configuration
- Choose New Agent at the top-right corner of the agent pool page.
- Download the agent.
- Follow the steps on the webpage, unzip the agent into your virtual machine folder. Suggest put the agent files into a short name subfolder under the data disk such as the 'udp' folder under the Disk E in the demo pic.
- Run Config.cmd via PowerShell from your agent folder.
- Server URL: https://dev.azure.com/msasg or https://msasg.visualstudio.com
- Personal Access Token(PAT): the PAT token you applied from the last step.
- Agent Pool: MSAI UDP-Pool
- Agent Name: Dev-{your alias}-vm-{vmname} (such as 'Dev-zhxin-vm-549')
- Work folder: default value (_work)
- Run Agent as Service: Yes
- User account for the service: Your VM machine login user account (such as 'FAREAST\zhxin')
- Password for the account: Your login password
Check the status for your VM agent
- You can open the link of MSAI UDP-Pool and check the agent status of your VM.
- You can try to queue a new Build pipeline on master branch and check if your agent is triggered. Then monitor if the build pipeline passes on your private agent.
