Skip to content

Commit ad9e240

Browse files
Merge pull request #265926 from ChaseCrum/CEOL-8
EOL message insert
2 parents 8c80e23 + 7526e12 commit ad9e240

10 files changed

+105
-74
lines changed

articles/batch/batch-rendering-functionality.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,9 @@ ms.topic: how-to
77

88
# Azure Batch rendering capabilities
99

10+
> [!CAUTION]
11+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
12+
1013
Standard Azure Batch capabilities are used to run rendering workloads and applications. Batch also includes specific features to support rendering workloads.
1114

1215
For an overview of Batch concepts, including pools, jobs, and tasks, see [this article](./batch-service-workflow-features.md).

articles/batch/virtual-file-mount.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,9 @@ ms.date: 08/22/2023
99

1010
# Mount a virtual file system on a Batch pool
1111

12+
> [!CAUTION]
13+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
14+
1215
Azure Batch supports mounting cloud storage or an external file system on Windows or Linux compute nodes in Batch pools. When a compute node joins the pool, the virtual file system mounts and acts as a local drive on that node. This article shows you how to mount a virtual file system on a pool of compute nodes by using the [Batch Management Library for .NET](/dotnet/api/overview/azure/batch).
1316

1417
Mounting the file system to the pool makes accessing data easier and more efficient than requiring tasks to get their own data from a large shared data set. Consider a scenario where multiple tasks need access to a common set of data, like rendering a movie. Each task renders one or more frames at once from the scene files. By mounting a drive that contains the scene files, it's easier for each compute node to access the shared data.

articles/databox-online/azure-stack-edge-gpu-create-virtual-machine-marketplace-image.md

Lines changed: 20 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,14 @@ ms.topic: how-to
1111
ms.date: 05/24/2022
1212
ms.author: alkohli
1313
#Customer intent: As an IT admin, I need to understand how to create and upload Azure VM images that I can use with my Azure Stack Edge Pro device so that I can deploy VMs on the device.
14+
1415
---
1516

1617
# Use Azure Marketplace image to create VM image for your Azure Stack Edge Pro GPU
1718

19+
> [!CAUTION]
20+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
21+
1822
[!INCLUDE [applies-to-GPU-and-pro-r-and-mini-r-skus](../../includes/azure-stack-edge-applies-to-gpu-pro-r-mini-r-sku.md)]
1923

2024
To deploy VMs on your Azure Stack Edge Pro GPU device, you need to create a VM image that you can use to create VMs. This article describes the steps that are required to create a VM image starting from an Azure Marketplace image. You can then use this VM image to deploy VMs on your Azure Stack Edge Pro GPU device.
@@ -41,9 +45,9 @@ Before you can use Azure Marketplace images for Azure Stack Edge, make sure you'
4145

4246
## Search for Azure Marketplace images
4347

44-
You'll now identify a specific Azure Marketplace image that you wish to use. Azure Marketplace hosts thousands of VM images.
48+
You'll now identify a specific Azure Marketplace image that you wish to use. Azure Marketplace hosts thousands of VM images.
4549

46-
To find some of the most commonly used Marketplace images that match your search criteria, run the following command.
50+
To find some of the most commonly used Marketplace images that match your search criteria, run the following command.
4751

4852
```azurecli
4953
az vm image list --all [--publisher <Publisher>] [--offer <Offer>] [--sku <SKU>]
@@ -54,13 +58,13 @@ Some example queries are:
5458

5559
```azurecli
5660
#Returns all images of type “Windows Server”
57-
az vm image list --all --publisher "MicrosoftWindowsserver" --offer "WindowsServer"
61+
az vm image list --all --publisher "MicrosoftWindowsserver" --offer "WindowsServer"
5862
5963
#Returns all Windows Server 2019 Datacenter images from West US published by Microsoft
6064
az vm image list --all --location "westus" --publisher "MicrosoftWindowsserver" --offer "WindowsServer" --sku "2019-Datacenter"
6165
62-
#Returns all VM images from a publisher
63-
az vm image list --all --publisher "Canonical"
66+
#Returns all VM images from a publisher
67+
az vm image list --all --publisher "Canonical"
6468
```
6569

6670
Here is an example output when VM images of a certain publisher, offer, and SKU were queried.
@@ -131,13 +135,13 @@ PS /home/user> az vm image list --all --publisher "Canonical" --offer "UbuntuSer
131135
PS /home/user>
132136
```
133137

134-
In this example, we will select Windows Server 2019 Datacenter Core, version 2019.0.20190410. We will identify this image by its Universal Resource Number (“URN”).
135-
138+
In this example, we will select Windows Server 2019 Datacenter Core, version 2019.0.20190410. We will identify this image by its Universal Resource Number (“URN”).
139+
136140
:::image type="content" source="media/azure-stack-edge-create-virtual-machine-marketplace-image/marketplace-image-1.png" alt-text="List of marketplace images":::
137141

138142
### Commonly used Marketplace images
139143

140-
Below is a list of URNs for some of the most commonly used images. If you just want the latest version of a particular OS, the version number can be replaced with “latest” in the URN. For example, “MicrosoftWindowsServer:WindowsServer:2019-Datacenter:Latest”.
144+
Below is a list of URNs for some of the most commonly used images. If you just want the latest version of a particular OS, the version number can be replaced with “latest” in the URN. For example, “MicrosoftWindowsServer:WindowsServer:2019-Datacenter:Latest”.
141145

142146

143147
| OS | SKU | Version | URN |
@@ -156,7 +160,7 @@ Below is a list of URNs for some of the most commonly used images. If you just w
156160

157161
## Create a new managed disk from the Marketplace image
158162

159-
Create an Azure Managed Disk from your chosen Marketplace image.
163+
Create an Azure Managed Disk from your chosen Marketplace image.
160164

161165
1. Set some parameters.
162166

@@ -172,7 +176,7 @@ Create an Azure Managed Disk from your chosen Marketplace image.
172176
```azurecli
173177
az disk create -g $diskRG -n $diskName --image-reference $urn
174178
$sas = az disk grant-access --duration-in-seconds 36000 --access-level Read --name $diskName --resource-group $diskRG
175-
$diskAccessSAS = ($sas | ConvertFrom-Json)[0].accessSas
179+
$diskAccessSAS = ($sas | ConvertFrom-Json)[0].accessSas
176180
```
177181
178182
Here is an example output:
@@ -245,12 +249,12 @@ PS /home/user> $diskAccessSAS = ($sas | ConvertFrom-Json)[0].accessSas
245249
PS /home/user>
246250
```
247251

248-
## Export a VHD from the managed disk to Azure Storage
252+
## Export a VHD from the managed disk to Azure Storage
249253

250254
This step will export a VHD from the managed disk to your preferred Azure blob storage account. This VHD can then be used to create VM images on Azure Stack Edge.
251255

252256
1. Set the destination storage account where the VHD will be copied.
253-
257+
254258
```azurecli
255259
$storageAccountName = <destination storage account name>
256260
$containerName = <destination container name>
@@ -266,9 +270,9 @@ This step will export a VHD from the managed disk to your preferred Azure blob s
266270
```
267271
268272
The VHD copy will take several minutes to complete. Ensure the copy has completed before proceeding by running the following command. The status field will show “Success” when complete.
269-
273+
270274
```azurecli
271-
Get-AzureStorageBlobCopyState –Container $containerName –Context $destContext -Blob $destBlobName
275+
Get-AzureStorageBlobCopyState –Container $containerName –Context $destContext -Blob $destBlobName
272276
```
273277
274278
Here is an example output:
@@ -316,8 +320,8 @@ DestinationSnapshotTime :
316320
To delete the managed disk you created, follow these steps:
317321

318322
```azurecli
319-
az disk revoke-access --name $diskName --resource-group $diskRG
320-
az disk delete --name $diskName --resource-group $diskRG --yes
323+
az disk revoke-access --name $diskName --resource-group $diskRG
324+
az disk delete --name $diskName --resource-group $diskRG --yes
321325
```
322326
The deletion takes a couple minutes to complete.
323327

0 commit comments

Comments
 (0)