1ES Hosted Pool - MSAIUDP-Pool-Azr

Last updated by Yana Wang on 3/14/2022 7:12:55 AM This content is over 788 days old.

Background

Due to the 1ES Security Policy, MSAI Unified Data Platform needs to migrate the self-hosted Agent pool to the Azure 1ES Hosted Agent Pool. By Sep 30th 2021, we must migrate our own custom Azure DevOps agent pools to 1ES Hosted Azure DevOps pools. You can read more about it here.

Agent Pool Infrastructure

Prerequisite

  1. You need to operate the agent pool on your SAW machine.
  2. You need to apply for the Contributor permission for MSAI Data Platform Subscription (8b8b2cf1-f7e3-4d86-8581-a15cd35463a4) via your Torus account.

1ES Managed Image

1ES Managed Image is the prepared installing environment for the Virtual Machine in the Agent pool. We need to configure the Managed Image to meet the solution dependencies.

MSAI-VS2019 Image

  • Navigate: MSAI Data Platform --> MSAIUnifiedDataPlatform --> MSAI-VS2019

We selected the 1ES Managed Image to configure the image.

{
    "baseImage": "/microsoftvisualstudio/visualstudio2019latest/vs-2019-ent-latest-win10-n/latest",
    "artifacts": [
        {
            "name": "windows-dotnetdevpack35"
        },
        {
            "name": "windows-dotnet472"
        },
        {
            "name": "windows-dotnetcore-sdk",
            "parameters": {
                "DotNetCoreVersion": "3.1.412"
            }
        }
    ],
    "publishingProfile": {
        "targetRegions": [
            {
                "name": "westus2",
                "replicas": 1
            }
        ]
    },
    "subscriptionId": "1fac9f4a-413b-4a9c-898e-6ccd0fb45b48"
}

1ES Hosted AzureDevOps Agents Pool

You can check the MSAIUDP-Pool-Azr settings on Azure Portal.

  • Navigate: MSAI Data Platform --> MSAIUnifiedDataPlatform --> MSAIUDP-Pool-Azr

  • Check the agents status in Running Agents tab.

    • Allocated indicates the machine is running a build pipeline on it.
    • Ready indicates the machine is available for trigger a new build pipeline request.
    • The number of the agents is following the settings in Pool.

Agent Pool Properties

  1. Basic properties: You can try to update the basic properties to improve the agent machine performance.

    • Azure DevOps Organization: https://dev.azure.com/msasg
    • Project Names: Auriga
    • Agent size: Standard D8s v3 (8 vCPUs, 32GB RAM)
    • Maximum pool size: 10 (The maximum number of the machine in Agent Pool)

    MSAIUDP-Pool-Azr Basic Properties

  2. Agent Image: All the VMs in MSAIUDP-Pool-Azr agent pool are the same image - "MSAI-VS2019". Agent Image setting

  3. Agent Pre-provisioning scheme: You can try to adjust the number (need to less than the Maximum pool size) of the pre-provisioning active agents. The larger the number, the active available agents in the running agents.

    [
    {
        "00:00:00": 5
    },
    {
        "16:00:00": 6
    },
    {
        "05:00:00": 6,
        "16:00:00": 6
    },
    {
        "05:00:00": 6,
        "16:00:00": 6
    },
    {
        "05:00:00": 6,
        "16:00:00": 6
    },
    {
        "05:00:00": 6,
        "16:00:00": 6
    },
    {
        "00:50:00": 3
    }
]

How to enable the MSAIUDP-Pool-Azr agent pool in build pipeline

If you create a new build pipeline which is against to the MSAIUDP-Pool-Azr. You need to permit the agent pool in the first build pipeline instance.

Specify the Agent pool in Build Pipeline

  pool:
    name: MSAIUDP-Pool-Azr

Steps

  1. Click "Permission needed".

  2. Click "Permit".

  3. Check the pipeline running status.

Reference