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: docs/getting_started.md
+68-43Lines changed: 68 additions & 43 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ Please make note of the following values after creating a service principal, we
20
20
- Application Secret
21
21
22
22
23
-
**Note:** You must have sufficient permissions to register an application with your Azure AD tenant, and assign the application to a role in your Azure subscription. Contact your subscription adminstator if you don't have the permissions. Normally a subscription admin can create a Service principal and can provide you the details.
23
+
**Note:** You must have sufficient permissions to register an application with your Azure AD tenant, and assign the application to a role in your Azure subscription. Contact your subscription administrator if you don't have the permissions. Normally a subscription admin can create a Service principal and can provide you the details.
24
24
25
25
26
26
### 4. Create a Variable Group
@@ -29,26 +29,26 @@ We make use of variable group inside Azure DevOps to store variables and their v
29
29
30
30
Please name your variable group **``devopsforai-aml-vg``** as we are using this name within our build yaml file.
31
31
32
-
The varibale group should contain the following variables:
**Note:** Creating of a Kubernetes cluster on AKS is out of scope of this tutorial, so you should take care of it on your own.
205
205
206
-
Save the pipeline and craete a release to trigger it manually. Once the pipeline exection is finished, check out deployments in the **mlops-AML-WS** workspace.
206
+
**Deploy trained model to Azure Web App for containers**
207
+
208
+
Note: This is an optional step and can be used only if you are deploying your scoring service on Azure Web Apps.
can be used to create a scoring image from the release pipeline. Image created by this script will be registered under Azure Container Registry(ACR) instance that belongs to Azure Machine Learning Service. Any dependencies that scoring file depends on can also be packaged with the container with Image config. To learn more on how to create a container with AML SDK click [here](https://docs.microsoft.com/en-us/python/api/azureml-core/azureml.core.image.image.image?view=azure-ml-py#create-workspace--name--models--image-config-).
212
+
213
+
Below is release pipeline with two tasks one to create an image using the above script and second is the deploy the image to Web App for containers
Save the pipeline and create a release to trigger it manually. Once the pipeline execution is finished, check out deployments in the **mlops-AML-WS** workspace.
207
232
208
233
209
234
210
235
Congratulations! You have three pipelines set up end to end:
211
-
- Build pipeline: triggered on code change to master branch on GitHub, performs linting, unit testing and publishing a trainig pipeline
212
-
- Release Trigger pipeline: runs a published training pipeline to trian, evaluate and register a model
213
-
- Release Deployment pipeline: deploys a model to QA (ACI) and Prod (AKS) environemts
236
+
- Build pipeline: triggered on code change to master branch on GitHub, performs linting, unit testing and publishing a training pipeline
237
+
- Release Trigger pipeline: runs a published training pipeline to train, evaluate and register a model
238
+
- Release Deployment pipeline: deploys a model to QA (ACI) and Prod (AKS) environments
0 commit comments