Merge pull request #268926 from sdgilley/sdg-freshness

Freshness: how to customize and how to manage compute

Author: v-dirichards

articles/machine-learning/how-to-create-attach-compute-studio.md

@@ -8,10 +8,11 @@ ms.author: vijetaj
 ms.reviewer: sgilley
 ms.service: machine-learning
 ms.subservice: compute
-ms.date: 08/11/2022
+ms.date: 03/04/2024
 ms.topic: how-to
 ms.custom: build-2023
 ---
+
 # Manage compute resources for model training and deployment in studio
 
 In this article, learn how to manage the compute resources you use for model training and deployment in Azure Machine studio.  
@@ -37,7 +38,7 @@ To see all compute targets for your workspace, use the following steps:
 
 1. Select tabs at the top to show each type of compute target.
 
-    :::image type="content" source="media/how-to-create-attach-studio/compute-targets.png" alt-text="View list of compute targets":::
+    :::image type="content" source="media/how-to-create-attach-studio/compute-targets.png" alt-text="Screenshot of view list of compute targets." lightbox="media/how-to-create-attach-studio/compute-targets.png":::
 
 [!INCLUDE [retiring vms](./includes/retiring-vms.md)]
 

articles/machine-learning/how-to-customize-compute-instance.md

@@ -6,17 +6,17 @@ services: machine-learning
 ms.service: machine-learning
 ms.subservice: compute
 ms.topic: how-to
-ms.author: jcioffi
-author: jesscioffi
+ms.author: vijetaj
+author: vijetajo
 ms.reviewer: sgilley
-ms.date: 05/04/2022
+ms.date: 03/13/2024
 ---
 
-# Customize the compute instance with a script 
+# Customize the compute instance with a script
 
 Use a setup script for an automated way to customize and configure a compute instance at provisioning time. 
 
-Use a compute instance as your fully configured and managed development environment in the cloud. For development and testing, you can also use the instance as a [training compute target](concept-compute-target.md#training-compute-targets) or for an [inference target](concept-compute-target.md#compute-targets-for-inference).   A compute instance can run multiple jobs in parallel and has a job queue. As a development environment, a compute instance can't be shared with other users in your workspace.
+Use a compute instance as your fully configured and managed development environment in the cloud. For development and testing, you can also use the instance as a [training compute target](concept-compute-target.md#training-compute-targets) or for an [inference target](concept-compute-target.md#compute-targets-for-inference).  A compute instance can run multiple jobs in parallel and has a job queue. As a development environment, a compute instance can't be shared with other users in your workspace.
 
 As an administrator, you can write a customization script to be used to provision all compute instances in the workspace according to your requirements. You can configure your setup script as a Creation script, which will run once when the compute instance is created. Or you can configure it as a Startup script, which will run every time the compute instance is started (including initial creation).
 
@@ -32,19 +32,19 @@ Some examples of what you can do in a setup script:
 
 ## Create the setup script
 
-The setup script is a shell script, which runs as `rootuser`.  Create or upload the script into your **Notebooks** files:
+The setup script is a shell script, which runs as `rootuser`. Create or upload the script into your **Notebooks** files:
 
 1. Sign into the [studio](https://ml.azure.com) and select your workspace.
-2. On the left, select **Notebooks**
-3. Use the **Add files** tool to create or upload your setup shell script.  Make sure the script filename ends in ".sh".  When you create a new file, also change the **File type** to *bash(.sh)*.
+1. On the left, select **Notebooks**.
+1. Use the **Add files** tool to create or upload your setup shell script. Make sure the script filename ends in ".sh". When you create a new file, also change the **File type** to *bash(.sh)*.
 
 :::image type="content" source="media/how-to-create-manage-compute-instance/create-or-upload-file.png" alt-text="Create or upload your setup script to Notebooks file in studio":::
 
 When the script runs, the current working directory of the script is the directory where it was uploaded. For example, if you upload the script to **Users>admin**, the location of the script on the compute instance and current working directory when the script runs is */home/azureuser/cloudfiles/code/Users/admin*. This location enables you to use relative paths in the script.
 
 Script arguments can be referred to in the script as $1, $2, etc.
 
-If your script was doing something specific to azureuser such as installing conda environment or Jupyter kernel, you'll have to put it within `sudo -u azureuser` block like this
+If your script was doing something specific to azureuser such as installing conda environment or Jupyter kernel,  put it within `sudo -u azureuser` block like this:
 
 :::code language="bash" source="~/azureml-examples-main/setup/setup-ci/install-pip-package.sh":::
 
@@ -71,13 +71,11 @@ Once you store the script, specify it during creation of your compute instance:
 1. On the left, select **Compute**.
 1. Select **+New** to create a new compute instance.
 1. [Fill out the form](how-to-create-compute-instance.md?tabs=azure-studio#create).
-1. On the second page of the form, open **Show advanced settings**.
-1. Turn on **Provision with setup script**.
-1. Select either **Creation script** or **Startup script** tab.
-1. Browse to the shell script you saved.  Or upload a script from your computer.
+1. On the **Applications** page of the form, toggle on the type of script you want to use, creation script (run once when creating the compute instance) or startup script (run every time the compute instance is started).
+1. Browse to the shell script you saved. Or upload a script from your computer.
 1. Add command arguments as needed.
 
-:::image type="content" source="media/how-to-create-manage-compute-instance/setup-script.png" alt-text="Provision a compute instance with a setup script in the studio.":::
+:::image type="content" source="media/how-to-create-manage-compute-instance/setup-script.png" alt-text="Screenshot of provision a compute instance with a setup script in the studio." lightbox="media/how-to-create-manage-compute-instance/setup-script.png":::
 
 > [!TIP]
 > If workspace storage is attached to a virtual network you might not be able to access the setup script file unless you are accessing the studio from within virtual network.
@@ -101,7 +99,7 @@ In a Resource Manager [template](https://github.com/Azure/azure-quickstart-templ
 `scriptData` above specifies the location of the creation script in the notebooks file share such as `Users/admin/testscript.sh`.
 `scriptArguments` is optional above and specifies the arguments for the creation script.
 
-You could instead provide the script inline for a Resource Manager template.  The shell command can refer to any dependencies uploaded into the notebooks file share.  When you use an inline string, the working directory for the script is `/mnt/batch/tasks/shared/LS_root/mounts/clusters/**ciname**/code/Users`.
+You could instead provide the script inline for a Resource Manager template. The shell command can refer to any dependencies uploaded into the notebooks file share. When you use an inline string, the working directory for the script is `/mnt/batch/tasks/shared/LS_root/mounts/clusters/**\<ciname\>**/code/Users`.
 
 For example, specify a base64 encoded command string for `scriptData`:
 
@@ -121,7 +119,7 @@ For example, specify a base64 encoded command string for `scriptData`:
 
 Logs from the setup script execution appear in the logs folder in the compute instance details page. Logs are stored back to your notebooks file share under the `Logs\<compute instance name>` folder. Script file and command arguments for a particular compute instance are shown in the details page.
 
-## Next steps
+## Related resources
 
 * [Access the compute instance terminal](how-to-access-terminal.md)
 * [Create and manage files](how-to-manage-files.md)