Skip to content

Commit 294ecbc

Browse files
authored
remove AKS description
1 parent 94e4437 commit 294ecbc

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Migration steps for ACI/AKS webservices to managed online endpoints
2+
title: Migration steps for ACI web services to managed online endpoints
33
titleSuffix: Azure Machine Learning
4-
description: Migration steps for ACI/AKS webservices to managed online endpoints in Azure Machine Learning
4+
description: Migration 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
@@ -13,7 +13,7 @@ ms.reviewer: blackmist
1313
ms.custom: migration
1414
---
1515

16-
# Migration steps for ACI/AKS webservice to Managed online endpoint
16+
# Migration steps for ACI webs ervices 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,7 +23,7 @@ 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. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
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` and the scoring url for AKS web service is like `http://1.2.3.4:80/api/v1/service/aks-service/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 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`.
2727
2828
## Supported Scenarios and Differences
2929

@@ -60,7 +60,7 @@ For private workspace and VNet scenarios, see [Use network isolation with manage
6060
6161
## Not supported
6262
+ [EncryptionProperties](/python/api/azureml-core/azureml.core.webservice.aci.encryptionproperties) for ACI container isn't supported.
63-
+ ACI webservices deployed through deploy_from_model and deploy_from_image isn't supported by the migration tool. Redeploy manually through CLI/SDK V2.
63+
+ 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.
6464

6565
## Migration Steps
6666

@@ -85,7 +85,7 @@ Use the following steps to run the scripts:
8585
* `<SUBSCRIPTION_ID>` - The subscription ID of your Azure subscription that contains your workspace.
8686
* `<RESOURCEGROUP_NAME>` - The resource group that contains your workspace.
8787
* `<WORKSPACE_NAME>` - The workspace name.
88-
* `<SERVICE_NAME>` - The name of your existing ACI/AKS service.
88+
* `<SERVICE_NAME>` - The name of your existing ACI service.
8989
* `<LOCAL_PATH>` - A local path where resources and templates used by the script are downloaded.
9090
* `<NEW_ENDPOINT_NAME>` - The name of the new endpoint that will be created. We recommend that the new endpoint name is different from the previous service name. Otherwise, the original service will not be displayed if you check your endpoints on the portal.
9191
* `<NEW_DEPLOYMENT_NAME>` - The name of the deployment to the new endpoint.

0 commit comments

Comments
 (0)