Skip to content

Commit 6af038c

Browse files
authored
change the wording from "migration" to "upgrade"
1 parent 49b8bd8 commit 6af038c

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

articles/machine-learning/migrate-to-v2-managed-online-endpoints.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Migration steps for ACI web services to managed online endpoints
2+
title: Upgrade steps for ACI web services to managed online endpoints
33
titleSuffix: Azure Machine Learning
4-
description: Migration steps for ACI web services to managed online endpoints in Azure Machine Learning
4+
description: Upgrade steps for ACI web services to managed online endpoints in Azure Machine Learning
55
services: machine-learning
66
ms.service: machine-learning
77
ms.subservice: core
@@ -10,10 +10,10 @@ author: shohei1029
1010
ms.author: shnagata
1111
ms.date: 09/28/2022
1212
ms.reviewer: blackmist
13-
ms.custom: migration
13+
ms.custom: upgrade
1414
---
1515

16-
# Migration steps for ACI web services to managed online endpoints
16+
# Upgrade steps for ACI web services to managed online endpoints
1717

1818
[Managed online endpoints](concept-endpoints.md#what-are-online-endpoints) help to deploy your ML models in a turnkey manner. Managed online endpoints work with powerful CPU and GPU machines in Azure in a scalable, fully managed way. Managed online endpoints take care of serving, scaling, securing, and monitoring your models, freeing you from the overhead of setting up and managing the underlying infrastructure. Details can be found on [Deploy and score a machine learning model by using an online endpoint](how-to-deploy-managed-online-endpoints.md).
1919

@@ -23,12 +23,12 @@ You can deploy directly to the new compute target with your previous models and
2323
> The scripts are preview and are provided without a service level agreement.
2424
2525
> [!IMPORTANT]
26-
> **The scoring URL will be changed after migration**. For example, the scoring url for ACI web service is like `http://aaaaaa-bbbbb-1111.westus.azurecontainer.io/score`. The scoring URI for a managed online endpoint is like `https://endpoint-name.westus.inference.ml.azure.com/score`.
26+
> **The scoring URL will be changed after upgrade**. For example, the scoring url for ACI web service is like `http://aaaaaa-bbbbb-1111.westus.azurecontainer.io/score`. The scoring URI for a managed online endpoint is like `https://endpoint-name.westus.inference.ml.azure.com/score`.
2727
2828
## Supported Scenarios and Differences
2929

3030
### Auth Mode
31-
No auth isn't supported for managed online endpoint. If you use the migration scripts, it will convert it to key auth.
31+
No auth isn't supported for managed online endpoint. If you use the upgrade scripts, it will convert it to key auth.
3232
For key auth, the original keys will be used. Token-based auth is also supported.
3333

3434
### TLS
@@ -38,7 +38,7 @@ Custom DNS name **isn't** supported.
3838

3939
### Resource Requirements
4040
[ContainerResourceRequirements](/python/api/azureml-core/azureml.core.webservice.aci.containerresourcerequirements) isn't supported, you can choose the proper [SKU](reference-managed-online-endpoints-vm-sku-list.md) for your inferencing.
41-
The migration tool will map the CPU/Memory requirement to corresponding SKU. If you choose to redeploy manually through CLI/SDK V2, we also suggest the corresponding SKU for your new deployment.
41+
The upgrade tool will map the CPU/Memory requirement to corresponding SKU. If you choose to redeploy manually through CLI/SDK V2, we also suggest the corresponding SKU for your new deployment.
4242

4343
| CPU request | Memory request in GB | Suggested SKU |
4444
| :----| :---- | :---- |
@@ -63,15 +63,15 @@ For private workspace and VNet scenarios, see [Use network isolation with manage
6363
6464
## Not supported
6565
+ [EncryptionProperties](/python/api/azureml-core/azureml.core.webservice.aci.encryptionproperties) for ACI container isn't supported.
66-
+ ACI web services deployed through deploy_from_model and deploy_from_image isn't supported by the migration tool. Redeploy manually through CLI/SDK V2.
66+
+ ACI web services deployed through deploy_from_model and deploy_from_image isn't supported by the upgrade tool. Redeploy manually through CLI/SDK V2.
6767

68-
## Migration Steps
68+
## Upgrade Steps
6969

7070
### With our [CLI](how-to-deploy-managed-online-endpoints.md) or [SDK preview](how-to-deploy-managed-online-endpoint-sdk-v2.md)
7171
Redeploy manually with your model files and environment definition.
7272
You can find our examples on [azureml-examples](https://github.com/Azure/azureml-examples). Specifically, this is the [SDK example for managed online endpoint](https://github.com/Azure/azureml-examples/tree/main/sdk/python/endpoints/online/managed).
7373

74-
### With our [migration tool](https://aka.ms/moeonboard) (preview)
74+
### With our [upgrade tool](https://aka.ms/moeonboard) (preview)
7575
This tool will automatically create new managed online endpoint based on your existing web services. Your original services won't be affected. You can safely route the traffic to the new endpoint and then delete the old one.
7676

7777
Use the following steps to run the scripts:
@@ -102,7 +102,7 @@ Use the following steps to run the scripts:
102102
7. After the deployment is completes successfully, you can verify the endpoint with the [az ml online-endpoint invoke](/cli/azure/ml/online-endpoint#az-ml-online-endpoint-invoke) command.
103103
104104
## Contact us
105-
If you have any questions or feedback on the migration script, contact us at [email protected].
105+
If you have any questions or feedback on the upgrade script, contact us at [email protected].
106106
107107
## Next steps
108108

0 commit comments

Comments
 (0)