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: articles/machine-learning/service/concept-ml-pipelines.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ Use Python to create your ML pipelines. The Azure Machine Learning SDK offers im
57
57
58
58
Using declarative data dependencies, you can optimize your tasks. The SDK includes a framework of pre-built modules for common tasks such as data transfer, compute target creation, and model publishing. The framework can be extended to model your own conventions by implementing custom steps that are reusable across pipelines.
59
59
60
-
Pipelines can be saved as templates so you can schedule batch-scoring or retraining jobs.
60
+
Pipelines can be saved as templates and can be deployed to a REST endpoint so you can schedule batch-scoring or retraining jobs.
61
61
62
62
Check out the [Python SDK reference docs for pipelines](http://aka.ms/aml-sdk).
Copy file name to clipboardExpand all lines: articles/machine-learning/service/concept-model-management-and-deployment.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,12 +49,14 @@ Images allow for reliable model deployment, along with all components needed to
49
49
50
50
The image can also include SDK components for logging and monitoring. The SDK logs data can be used to fine-tune or retrain your model, including the input and output of the model.
51
51
52
+
Azure Machine Learning supports the most popular frameworks, but in general any framework that can be pip installed can work.
53
+
52
54
When your workspace was created, so were other several other Azure resources used by that workspace.
53
55
All the objects used to create the image are stored in the Azure storage account in your workspace. The image is created and stored in the Azure Container Registry. You can provide additional metadata tags when creating the image, which are also stored by the image registry and can be queried to find your image.
54
56
55
57
## Step 3: Deployment
56
58
57
-
You can deploy registered images into the cloud or to edge devices. The deployment process creates all the resources needed to monitor, load-balance, and auto-scale your model. You can also upgrade an existing deployment to use a newer image.
59
+
You can deploy registered images into the cloud or to edge devices. The deployment process creates all the resources needed to monitor, load-balance, and auto-scale your model. Access to the deployed services can be secured with certificate based authentication by providing the security assets during deployment. You can also upgrade an existing deployment to use a newer image.
58
60
59
61
Web service deployments are also searchable. For example, you can search for all deployments of a specific model or image.
Copy file name to clipboardExpand all lines: articles/machine-learning/service/how-to-migrate.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ ms.date: 09/24/2018
17
17
**If you have installed the Workbench (preview) application and/or have experimentation and model management preview accounts, use this article to migrate to the latest version.** If you don't have preview Workbench installed, or an experimentation and/or model management account, you don't need to migrate anything.
18
18
19
19
## What can I migrate?
20
-
Most artifacts created in the first preview of Azure Machine Learning service are stored in your own local or cloud storage. These artifacts won't disappear. To migrate, register the artifacts again with the updated Azure Machine Learning offering.
20
+
Most artifacts created in the first preview of Azure Machine Learning service are stored in your own local or cloud storage. These artifacts won't disappear. To migrate, register the artifacts again with the updated Azure Machine Learning service.
21
21
22
22
The following table and article explain what you can do with your existing assets and resources before or after moving over to the latest version of Azure Machine Learning service. You can also continue to use the previous version and your assets for some time ([see transition support timeline](overview-what-happened-to-workbench.md#timeline)).
Copy file name to clipboardExpand all lines: articles/machine-learning/service/overview-what-happened-to-workbench.md
+10-4Lines changed: 10 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ While there are new improved CLI and SDK clients in the current release, the des
31
31
32
32
## How do I migrate?
33
33
34
-
Most of the artifacts created in the earlier version of the Azure Machine Learning service are stored in your own local or cloud storage. These artifacts won't ever disappear. To migrate, you need to register the artifacts again with the updated Azure Machine Learning offering. Learn what you can migrate and how in this [migration article](how-to-migrate.md).
34
+
Most of the artifacts created in the earlier version of the Azure Machine Learning service are stored in your own local or cloud storage. These artifacts won't ever disappear. To migrate, you need to register the artifacts again with the updated Azure Machine Learning service. Learn what you can migrate and how in this [migration article](how-to-migrate.md).
35
35
36
36
<aname="timeline"></a>
37
37
@@ -71,21 +71,27 @@ You can use this same SDK for larger data sets or use Azure Databricks to prepar
71
71
72
72
You won't lose any code or work. In the older version, projects are cloud entities with a local directory. In the latest version, you attach local directories to the Azure Machine Learning Workspace using a local config file. [See a diagram of the latest architecture](concept-azure-machine-learning-architecture.md).
73
73
74
-
Since much of the project contents was already on your local machine, you just need to create a config file in that directory and reference it in your code to connect to your workspace. [Learn how migrate your existing projects.](how-to-migrate.md#projects)
74
+
Since much of the project content was already on your local machine, you just need to create a config file in that directory and reference it in your code to connect to your workspace. [Learn how migrate your existing projects.](how-to-migrate.md#projects)
75
75
76
76
Learn how to get started [in Python with the SDK](quickstart-get-started.md).
77
77
78
+
## What about my registers models and images?
79
+
80
+
The models that you registered in your old model registry must migrated to your new workspace if you want to continue to use them. You can do this by [downloading the models and re-registering them](how-to-migrate.md) in your new workspace.
81
+
82
+
The images that you created in your old image registry must be re-created in the new workspace to continue to use them. You can do this by following the [create docker image](how-to-deploy-to-aci.md) section.
83
+
78
84
## What about deployed web services?
79
85
80
86
The models you deployed as web services using your Model Management account will continue to work for as long as Azure Container Service (ACS) is supported. Those web services will even work after support has ended for Model Management accounts. However, when support for the old CLI ends, so does your ability to manage those web services.
81
87
82
88
In the newer version, models are deployed as web services to [Azure Container Instances](how-to-deploy-to-aci.md) (ACI) or [Azure Kubernetes Service](how-to-deploy-to-aks.md) (AKS) clusters. You can also [deploy to FPGAs and to the IoT edge](how-to-deploy-and-where.md). Without having to change any of your scoring files, dependencies, and schemas, you can redeploy your models using the new SDK or CLI.
83
89
84
-
## What about the SDK & CLI?
90
+
## What about the old SDK & CLI?
85
91
86
92
Yes, they will continue to work for a while (see the [timeline](#timeline) above). We recommend that you start creating your new experiments and models with the latest SDK and/or CLI.
87
93
88
-
In the latest release, the new Python SDK allows you to interact with the Azure Machine Learning service in any Python environment. Learn how to install the <ahref="http://aka.ms/aml-sdk"target="_blank">SDK</a>. You can also use the [updated Azure CLI machine learning extension](reference-azure-machine-learning-cli.md) with the rich set of `az ml` commands to interact the service in any command-line environment, including Azure portal cloud shell.
94
+
In the latest release, the new Python SDK allows you to interact with the Azure Machine Learning service in any Python environment. Learn how to install the latest <ahref="http://aka.ms/aml-sdk"target="_blank">SDK</a>. You can also use the [updated Azure CLI machine learning extension](reference-azure-machine-learning-cli.md) with the rich set of `az ml` commands to interact the service in any command-line environment, including Azure portal cloud shell.
0 commit comments