Skip to content

Commit 89a01be

Browse files
Merge pull request #245210 from LouisBerner/v-lberner-ADO_123699
Updated the GPU tutorial.
2 parents 3944ce4 + 5ec5b8f commit 89a01be

File tree

2 files changed

+12
-9
lines changed

2 files changed

+12
-9
lines changed

articles/databox-online/azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: alkohli
77
ms.service: databox
88
ms.subservice: edge
99
ms.topic: tutorial
10-
ms.date: 01/25/2023
10+
ms.date: 07/19/2023
1111
ms.author: alkohli
1212
zone_pivot_groups: azure-stack-edge-device-deployment
1313
# Customer intent: As an IT admin, I need to understand how to connect and activate Azure Stack Edge Pro so I can use it to transfer data to Azure.
@@ -142,8 +142,9 @@ Follow these steps to add or delete virtual switches and virtual networks.
142142

143143
1. Provide a name for your virtual switch.
144144
1. Choose the network interface on which the virtual switch should be created.
145-
1. If deploying 5G workloads, set **Supports accelerated networking** to **Yes**.
146-
1. Select **Apply**. You can see that the specified virtual switch is created.
145+
1. Select **Apply**. You can see that the specified virtual switch is created.
146+
147+
You can create Virtual Machines from Azure portal using any of the virtual networks you have created.
147148

148149
![Screenshot of "Advanced networking" page with virtual switch added and enabled for compute in local UI for one node.](./media/azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy/configure-compute-network-3.png)
149150

@@ -448,8 +449,9 @@ After the cluster is formed and configured, you can now create new virtual switc
448449

449450
1. Provide a name for your virtual switch.
450451
1. Choose the network interface on which the virtual switch should be created.
451-
1. If deploying 5G workloads, set **Supports accelerated networking** to **Yes**.
452-
1. Select **Apply**.
452+
1. Select **Apply**.
453+
454+
You can create Virtual Machines from Azure portal using any of the virtual networks you have created.
453455

454456
1. The configuration will take a couple minutes to apply and once the virtual switch is created, the list of virtual switches updates to reflect the newly created switch. You can see that the specified virtual switch is created and enabled for compute.
455457

articles/databox-online/azure-stack-edge-pro-2-deploy-configure-network-compute-web-proxy.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: alkohli
77
ms.service: databox
88
ms.subservice: edge
99
ms.topic: tutorial
10-
ms.date: 04/27/2023
10+
ms.date: 07/19/2023
1111
ms.author: alkohli
1212
zone_pivot_groups: azure-stack-edge-device-deployment
1313
# Customer intent: As an IT admin, I need to understand how to connect and activate Azure Stack Edge Pro so I can use it to transfer data to Azure.
@@ -476,11 +476,12 @@ After the cluster is formed and configured, you'll now create new virtual switch
476476

477477
1. Provide a name for your virtual switch.
478478
1. Choose the network interface on which the virtual switch should be created.
479-
1. If deploying 5G workloads, set **Supports accelerated networking** to **Yes**.
480479
1. Select the intent to associate with this network interface as **compute**. Alternatively, the switch can be used for management traffic as well. You can't configure storage intent as storage traffic was already configured based on the network topology that you selected earlier.
481480

482-
> [!TIP]
483-
> Use *CTRL + Click* to select more than one intent for your virtual switch.
481+
You can create Virtual Machines from Azure portal using any of the virtual networks you have created.
482+
483+
> [!TIP]
484+
> Use *CTRL + Click* to select more than one intent for your virtual switch.
484485
485486
1. Assign **Kubernetes node IPs**. These static IP addresses are for the Kubernetes VMs.
486487

0 commit comments

Comments
 (0)