Skip to content

Commit e326d5c

Browse files
author
Larry
committed
writing
1 parent 079ebc3 commit e326d5c

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

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

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -119,6 +119,16 @@ To deploy the model as a web service, you must provide the following items:
119119

120120
For more information, see [Deploy models](how-to-deploy-and-where.md).
121121

122+
#### Controlled rollout
123+
124+
When deploying to Azure Kubernetes Service, you can use controlled rollout to enable the following scenarios:
125+
126+
* Create multiple versions of an endpoint for a deployment
127+
* Perform A/B testing by routing traffic to different versions of the endpoint.
128+
* Switch between endpoint versions by updating the traffic percentage in endpoint configuration.
129+
130+
For more information, see [Controlled rollout of ML models](how-to-deploy-azure-kubernetes-service.md#deploy-models-to-aks-using-controlled-rollout-preview).
131+
122132
#### IoT Edge devices
123133

124134
You can use models with IoT devices through **Azure IoT Edge modules**. IoT Edge modules are deployed to a hardware device, which enables inference, or model scoring, on the device.
@@ -135,8 +145,10 @@ Azure ML gives you the capability to track the end-to-end audit trail of all of
135145

136146
- Azure ML [integrates with Git](how-to-set-up-training-targets.md#gitintegration) to track information on which repository / branch / commit your code came from.
137147
- [Azure ML Datasets](how-to-create-register-datasets.md) help you track, profile, and version data.
148+
- [Interpretability](how-to-machine-learning-interpretability.md) allows you to explain your models, meet regulatory compliance, and understand how models arrive at a result for given input.
138149
- Azure ML Run history stores a snapshot of the code, data, and computes used to train a model.
139150
- The Azure ML Model Registry captures all of the metadata associated with your model (which experiment trained it, where it is being deployed, if its deployments are healthy).
151+
- [Integration with Azure Event Grid](concept-event-grid-integration) allows you to act on events in the ML lifecycle. For example, model registration, deployment, data drift, and training (run) events.
140152

141153
> [!TIP]
142154
> While some information on models and datasets are automatically captured, you can add additional information by using __tags__. When looking for registered models and datasets in your workspace, you can use tags as a filter.
@@ -158,7 +170,7 @@ For more information, see [How to enable model data collection](how-to-enable-da
158170

159171
## Retrain your model on new data
160172

161-
Often, you'll want to update your model, or even retrain it from scratch, as you receive new information. Sometimes, receiving new data is an expected part of the domain. Other times, as discussed in [Detect data drift (preview) on datasets](how-to-monitor-datasets.md), model performance can degrade in the face of such things as changes to a particular sensor, natural data changes such as seasonal effects, or features shifting in their relation to other features.
173+
Often, you'll want to validate your model, update it, or even retrain it from scratch, as you receive new information. Sometimes, receiving new data is an expected part of the domain. Other times, as discussed in [Detect data drift (preview) on datasets](how-to-monitor-datasets.md), model performance can degrade in the face of such things as changes to a particular sensor, natural data changes such as seasonal effects, or features shifting in their relation to other features.
162174

163175
There is no universal answer to "How do I know if I should retrain?" but Azure ML event and monitoring tools previously discussed are good starting points for automation. Once you have decided to retrain, you should:
164176

0 commit comments

Comments
 (0)