Skip to content

Commit 44327e0

Browse files
author
Larry
committed
tweaks
1 parent dcff5cf commit 44327e0

File tree

1 file changed

+19
-4
lines changed

1 file changed

+19
-4
lines changed

articles/machine-learning/concept-model-management-and-deployment.md

Lines changed: 19 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,19 +9,28 @@ ms.topic: conceptual
99
ms.reviewer: jmartens
1010
author: jpe316
1111
ms.author: jordane
12-
ms.date: 11/22/2019
12+
ms.date: 02/21/2020
1313
ms.custom: seodec18
1414
---
1515

1616
# MLOps: Model management, deployment and monitoring with Azure Machine Learning
1717

1818
In this article, learn about how to use Azure Machine Learning to manage the lifecycle of your models. Azure Machine Learning uses a Machine Learning Operations (MLOps) approach. MLOps improves the quality and consistency of your machine learning solutions.
1919

20-
MLOps is based on DevOps principles and practices that increase the efficiency of workflows. For example, continuous integration, delivery, and deployment. Azure Machine Learning provides the following MLOps capabilities:
20+
## What is MLOps?
21+
22+
Machine Learning Operations (MLOps) is based on DevOps principles and practices that increase the efficiency of workflows. For example, continuous integration, delivery, and deployment. MLOps applies these principals to the machine learning process, with the goal of:
23+
24+
* Faster experimentation and development of models
25+
* Faster deployment of models into production
26+
* Quality assurance
27+
28+
Azure Machine Learning provides the following MLOps capabilities:
2129

2230
- **Create reproducible ML pipelines**. Machine Learning pipelines allow you to define repeatable and reusable steps for your data preparation, training, and scoring processes.
31+
- **Create reusable software environments** for training and deploying models.
2332
- **Register, package, and deploy models from anywhere**. You can also track associated metadata required to use the model.
24-
- **Capture the governance data required for capturing the end-to-end ML lifecycle**. The logged information can include who is publishing models, why changes are being made, and when models were deployed or used in production.
33+
- **Capture the governance data for the end-to-end ML lifecycle**. The logged information can include who is publishing models, why changes are being made, and when models were deployed or used in production.
2534
- **Notify and alert on events in the ML lifecycle**, such as experiment completion, model registration, model deployment, and data drift detection.
2635
- **Monitor ML applications for operational and ML-related issues**. Compare model inputs between training and inference, explore model-specific metrics, and provide monitoring and alerts on your ML infrastructure.
2736
- **Automate the end-to-end ML lifecycle with Azure Machine Learning and Azure Pipelines** to frequently update models, test new models, and continuously roll out new ML models alongside your other applications and services.
@@ -34,6 +43,12 @@ An ML pipeline can contain steps from data preparation to feature extraction to
3443

3544
If you use the [Designer](concept-designer.md) to create your ML pipelines, you may at any time click the **"..."** at the top-right of the Designer page and then select **Clone**. Cloning your pipeline allows you to iterate your pipeline design without losing your old versions.
3645

46+
## Create reusable software environments
47+
48+
Azure Machine Learning environments allow you to track and reproduce your projects' software dependencies as they evolve. Environments allow you to ensure that builds are reproducible without manual software configurations.
49+
50+
Environments describe the pip and Conda dependencies for your projects, and can be used for both training and deployment of models. For more information, see [What are Azure Machine Learning environments](concept-environments.md).
51+
3752
## Register, package, and deploy models from anywhere
3853

3954
### Register and track ML models
@@ -77,7 +92,7 @@ When using a model as a web service or IoT Edge device, you provide the followin
7792

7893
* The model(s) that are used to score data submitted to the service/device.
7994
* An entry script. This script accepts requests, uses the model(s) to score the data, and return a response.
80-
* A conda environment file that describes the dependencies required by the model(s) and entry script.
95+
* An Azure Machine Learning environment that describes the pip and Conda dependencies required by the model(s) and entry script.
8196
* Any additional assets such as text, data, etc. that are required by the model(s) and entry script.
8297

8398
You also provide the configuration of the target deployment platform. For example, the VM family type, available memory, and number of cores when deploying to Azure Kubernetes Service.

0 commit comments

Comments
 (0)