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/tutorial-train-deploy-model-cli.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ The `examples/cli-train-deploy` directory from the project contains the followin
63
63
The repository contains the following files, which are used to deploy the trained model as a web service:
64
64
65
65
*`aciDeploymentConfig.yml`: A __deployment configuration__ file. This file defines the hosting environment needed for the model.
66
-
*`inferenceConfig.yml`: An __inference configuration__ file. This file defines the software environment used by the service to score data with the model.
66
+
*`inferenceConfig.json`: An __inference configuration__ file. This file defines the software environment used by the service to score data with the model.
67
67
*`score.py`: A python script that accepts incoming data, scores it using the model, and then returns a response.
68
68
*`scoring-env.yml`: The conda dependencies needed to run the model and `score.py` script.
69
69
*`testdata.json`: A data file that can be used to test the deployed web service.
@@ -196,10 +196,10 @@ The output of this command is similar to the following JSON:
196
196
}
197
197
```
198
198
199
-
This command creates a new compute target named `cpu`, with a maximum of four nodes. The VM size selected provides a VM with a GPU resource. For information on the VM size, see [VM types and sizes].
199
+
This command creates a new compute target named `cpu-cluster`, with a maximum of four nodes. The VM size selected provides a VM with a GPU resource. For information on the VM size, see [VM types and sizes].
200
200
201
201
> [!IMPORTANT]
202
-
> The name of the compute target (`cpu` in this case), is important; it is referenced by the `.azureml/mnist.runconfig` file used in the next section.
202
+
> The name of the compute target (`cpu-cluster` in this case), is important; it is referenced by the `.azureml/mnist.runconfig` file used in the next section.
203
203
204
204
## Define the dataset
205
205
@@ -297,7 +297,7 @@ For more information on run configuration files, see [Set up and use compute tar
297
297
298
298
## Submit the training run
299
299
300
-
To start a training run on the `cpu-compute` compute target, use the following command:
300
+
To start a training run on the `cpu-cluster` compute target, use the following command:
301
301
302
302
```azurecli-interactive
303
303
az ml run submit-script -c mnist -e myexperiment --source-directory scripts -t runoutput.json
@@ -366,7 +366,7 @@ The first command downloads the registered model to the current directory. The f
366
366
To deploy a model, use the following command:
367
367
368
368
```azurecli-interactive
369
-
az ml model deploy -n myservice -m "mymodel:1" --ic inferenceConfig.yml --dc aciDeploymentConfig.yml
369
+
az ml model deploy -n myservice -m "mymodel:1" --ic inferenceConfig.json --dc aciDeploymentConfig.yml
370
370
```
371
371
372
372
> [!NOTE]
@@ -446,10 +446,10 @@ This command returns a JSON document that contains the name of the deleted servi
446
446
447
447
### Delete the training compute
448
448
449
-
If you plan on continuing to use the Azure Machine Learning workspace, but want to get rid of the `cpu-compute` compute target created for training, use the following command:
449
+
If you plan on continuing to use the Azure Machine Learning workspace, but want to get rid of the `cpu-cluster` compute target created for training, use the following command:
450
450
451
451
```azurecli-interactive
452
-
az ml computetarget delete -n cpu
452
+
az ml computetarget delete -n cpu-cluster
453
453
```
454
454
455
455
This command returns a JSON document that contains the ID of the deleted compute target. It may take several minutes before the compute target has been deleted.
0 commit comments