You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-setup-mlops-azureml.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ Azure Machine Learning allows you to integrate with [Azure DevOps pipeline](/azu
25
25
* Deployment of machine learning models as public or private web services
26
26
* Monitoring deployed machine learning models (such as for performance analysis)
27
27
28
-
In this article, you learn about using Azure Machine Learning to set up an end-to-end MLOps pipeline that runs a linear regression to predict taxi fares in NYC. The pipeline is made up of components, each serving different functions, which can be registered with the workspace, versioned, and reused with various inputs and outputs. you are going to be using the [recommended Azure architecture for MLOps](/azure/architecture/data-guide/technology-choices/machine-learning-operations-v2) and [Azure MLOps (v2) solution accelerator](https://github.com/Azure/mlops-v2) to quickly set up an MLOps project in AzureML.
28
+
In this article, you learn about using Azure Machine Learning to set up an end-to-end MLOps pipeline that runs a linear regression to predict taxi fares in NYC. The pipeline is made up of components, each serving different functions, which can be registered with the workspace, versioned, and reused with various inputs and outputs. you're going to be using the [recommended Azure architecture for MLOps](/azure/architecture/data-guide/technology-choices/machine-learning-operations-v2) and [Azure MLOps (v2) solution accelerator](https://github.com/Azure/mlops-v2) to quickly setup an MLOps project in AzureML.
29
29
30
30
> [!TIP]
31
31
> We recommend you understand some of the [recommended Azure architectures](/azure/architecture/data-guide/technology-choices/machine-learning-operations-v2) for MLOps before implementing any solution. You'll need to pick the best architecture for your given Machine learning project.
@@ -39,7 +39,7 @@ In this article, you learn about using Azure Machine Learning to set up an end-t
39
39
- Git running on your local machine.
40
40
- An [organization](/azure/devops/organizations/accounts/create-organization) in Azure DevOps.
41
41
-[Azure DevOps project](how-to-devops-machine-learning.md) that will host the source repositories and pipelines.
42
-
- The [Terraform extension for Azure DevOps](https://marketplace.visualstudio.com/items?itemName=ms-devlabs.custom-terraform-tasks) if you are using Azure DevOps + Terraform to spin up infrastructure
42
+
- The [Terraform extension for Azure DevOps](https://marketplace.visualstudio.com/items?itemName=ms-devlabs.custom-terraform-tasks) if you're using Azure DevOps + Terraform to spin up infrastructure
43
43
44
44
> [!NOTE]
45
45
>
@@ -66,7 +66,7 @@ Before you can set up an MLOps project with AzureML, you need to set up authenti
66
66
67
67

68
68
69
-
1. Copy the bash commands below to your computer and update the **projectName**, **subscriptionId**, and **environment** variables with the values for your project. If you are creating both a Dev and Prod environment, you'll need to run this script once for each environment, creating a service principal for each. This command will also grant the **Contributor** role to the service principal in the subscription provided. This is required for Azure DevOps to properly use resources in that subscription.
69
+
1. Copy the following bash commands to your computer and update the **projectName**, **subscriptionId**, and **environment** variables with the values for your project. If you're creating both a Dev and Prod environment, you'll need to run this script once for each environment, creating a service principal for each. This command will also grant the **Contributor** role to the service principal in the subscription provided. This is required for Azure DevOps to properly use resources in that subscription.
70
70
71
71
```bash
72
72
projectName="<your project name>"
@@ -94,7 +94,7 @@ Before you can set up an MLOps project with AzureML, you need to set up authenti
94
94
}
95
95
```
96
96
97
-
1. Repeat **Step 3.** if you're creating service principals for Dev and Prod environments. For this demo, we will be creating only one environment which is Prod.
97
+
1. Repeat **Step 3.** if you're creating service principals for Dev and Prod environments. For this demo, we'll be creating only one environment, which is Prod.
98
98
99
99
1. Close the Cloud Shell once the service principals are created.
100
100
@@ -160,18 +160,18 @@ The Azure DevOps setup is successfully finished.
160
160
161
161

162
162
163
-
1. Enter https://github.com/Azure/mlops-v2-ado-demo into the Clone URL field. Click import at the bottom of the page
163
+
1. Enter https://github.com/Azure/mlops-v2-ado-demo into the Clone URL field. Select import at the bottom of the page
164
164
165
165

166
166
167
167
1. Open the **Project settings** at the bottom of the left hand navigation pane
168
168
169
-
1. Under the Repos section, click**Repositories**. Select the repository you created in**Step 6.** Select the **Security** tab
169
+
1. Under the Repos section, select **Repositories**. Select the repository you created in **Step 6.** Select the **Security** tab
170
170
171
171
1. Under the User permissions section, select the **mlopsv2 Build Service** user. Change the permission **Contribute** permission to **Allow** and the **Create branch** permission to **Allow**.
172
172

173
173
174
-
1. Open the **Pipelines** section in the left hand navigation pane and click on the 3 vertical dots next to the **Create Pipelines** button. Select **Manage Security**
174
+
1. Open the **Pipelines** section in the left hand navigation pane and select on the 3 vertical dots next to the **Create Pipelines** button. Select **Manage Security**
175
175
176
176

177
177
@@ -190,7 +190,7 @@ This step deploys the training pipeline to the Azure Machine Learning workspace
190
190
> Make sure you understand the [Architectural Patterns](/azure/architecture/data-guide/technology-choices/machine-learning-operations-v2) of the solution accelerator before you checkout the MLOps v2 repo and deploy the infrastructure. In examples you'll use the [classical ML project type](/azure/architecture/data-guide/technology-choices/machine-learning-operations-v2#classical-machine-learning-architecture).
191
191
192
192
### Run Azure infrastructure pipeline
193
-
1. Go to the first repo you imported in the previous section, `mlops-v2-ado-demo`, and please select the **config-infra-prod.yml** file.
193
+
1. Go to the first repo you imported in the previous section, `mlops-v2-ado-demo`, and selectthe**config-infra-prod.yml** file.
194
194
195
195

196
196
@@ -204,7 +204,7 @@ This step deploys the training pipeline to the Azure Machine Learning workspace
204
204
> [!NOTE]
205
205
> If you are running a Deep Learning workload such as CV or NLP, ensure your GPU compute is available in your deployment zone.
206
206
207
-
1. Click Commit and push code to get these values into the pipeline.
207
+
1. Select Commit and push code to get these values into the pipeline.
208
208
209
209
1. Go to Pipelines section
210
210
@@ -308,7 +308,7 @@ This step deploys the training pipeline to the Azure Machine Learning workspace
308
308
309
309
1. Select `main` as a branch and choose Managed Online Endpoint `/mlops/devops-pipelines/deploy-online-endpoint-pipeline.yml` then select **Continue**.
310
310
311
-
1. Online endpoint names need to be unique, so change **[your endpoint-name]** to another unique name and thenselect**Run**. No need to change the default if it does not fail.
311
+
1. Online endpoint names need to be unique, so change **[your endpoint-name]** to another unique name and then select **Run**. No need to change the default if it doesn't fail.
312
312
313
313

0 commit comments