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/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-powershell.md
+25-21Lines changed: 25 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: alkohli
7
7
ms.service: databox
8
8
ms.subservice: edge
9
9
ms.topic: how-to
10
-
ms.date: 05/24/2022
10
+
ms.date: 07/20/2023
11
11
ms.author: alkohli
12
12
ms.custom: devx-track-azurepowershell
13
13
#Customer intent: As an IT admin, I need to understand how to create and manage virtual machines (VMs) on my Azure Stack Edge Pro device. I want to use APIs so that I can efficiently manage my VMs.
@@ -26,8 +26,8 @@ The high-level deployment workflow of the VM deployment is as follows:
26
26
1. Connect to the local Azure Resource Manager of your device.
27
27
1. Identify the built-in subscription on the device.
28
28
1. Bring your VM image.
29
-
1. Create a resource group in the built-in subscription. The resource group will contain the VM and all the related resources.
30
-
1. Create a local storage account on the device to store the VHD that will be used to create a VM image.
29
+
1. Create a resource group in the built-in subscription. The resource group contains the VM and all the related resources.
30
+
1. Create a local storage account on the device to store the VHD that is used to create a VM image.
31
31
1. Upload a Windows/Linux source image into the storage account to create a managed disk.
32
32
1. Use the managed disk to create a VM image.
33
33
1. Enable compute on a device port to create a virtual switch.
@@ -188,7 +188,7 @@ Start by creating a new Azure resource group and use this as a logical container
188
188
```powershell
189
189
$ResourceGroupName = "<Resource group name>"
190
190
```
191
-
1. Create a resource group for the resources that you'll create for the VM.
191
+
1. Create a resource group for the resources that you create for the VM.
By default, an IP is dynamically assigned to your network interface from the network enabled for compute. Use the `-PrivateIpAddress parameter` if you are allocating a static IP to your network interface.
574
+
By default, an IP is dynamically assigned to your network interface from the network enabled for compute. Use the `-PrivateIpAddress parameter` if you're allocating a static IP to your network interface.
By default, an IP is dynamically assigned to your network interface from the network enabled for compute. Use the `-PrivateIpAddress parameter` if you are allocating a static IP to your network interface.
652
+
By default, an IP is dynamically assigned to your network interface from the network enabled for compute. Use the `-PrivateIpAddress parameter` if you're allocating a static IP to your network interface.
#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 GPU device so that I can deploy VMs on the device.
14
14
---
@@ -39,7 +39,7 @@ The high-level workflow to deploy a VM from a specialized image is:
39
39
40
40
Before you can deploy a VM on your device via PowerShell, make sure that:
41
41
42
-
- You have access to a client that you'll use to connect to your device.
42
+
- You have access to a client that you use to connect to your device.
43
43
- Your client runs a [Supported OS](azure-stack-edge-gpu-system-requirements.md#supported-os-for-clients-connected-to-device).
44
44
- Your client is configured to connect to the local Azure Resource Manager of your device as per the instructions in [Connect to Azure Resource Manager for your device](azure-stack-edge-gpu-connect-resource-manager.md).
45
45
@@ -53,7 +53,7 @@ Verify that your client can connect to the local Azure Resource Manager.
2. Provide the username `EdgeArmUser` and the password to connect via Azure Resource Manager. If you do not recall the password, [Reset the password for Azure Resource Manager](azure-stack-edge-gpu-set-azure-resource-manager-password.md) and use this password to sign in.
56
+
2. Provide the username `EdgeArmUser` and the password to connect via Azure Resource Manager. If you don't recall the password, [Reset the password for Azure Resource Manager](azure-stack-edge-gpu-set-azure-resource-manager-password.md) and use this password to sign in.
57
57
58
58
## Deploy VM from specialized image
59
59
@@ -65,7 +65,7 @@ Follow these steps to copy VHD to local storage account:
65
65
66
66
1. Copy the source VHD to a local blob storage account on your Azure Stack Edge.
67
67
68
-
1. Take note of the resulting URI. You'll use this URI in a later step.
68
+
1. Take note of the resulting URI. You use this URI in a later step.
69
69
70
70
To create and access a local storage account, see the sections [Create a storage account](azure-stack-edge-gpu-deploy-virtual-machine-powershell.md#create-a-local-storage-account) through [Upload a VHD](azure-stack-edge-gpu-deploy-virtual-machine-powershell.md#upload-a-vhd) in the article: [Deploy VMs on your Azure Stack Edge device via Azure PowerShell](azure-stack-edge-gpu-deploy-virtual-machine-powershell.md).
71
71
@@ -80,7 +80,7 @@ Follow these steps to create a managed disk from a VHD that you uploaded to the
$DiskConfig = New-AzureRmDiskConfig -Location DBELocal -StorageAccountId $StorageAccountId -CreateOption Import -SourceUri "Source URL for your VHD"
96
+
95
97
```
96
98
97
-
Here is an example output. The location here is set to the location of the local storage account and is always `DBELocal` for all local storage accounts on your Azure Stack Edge Pro GPU device.
99
+
Here's an example output. The location here is set to the location of the local storage account and is always `DBELocal` for all local storage accounts on your Azure Stack Edge Pro GPU device.
@@ -121,7 +123,7 @@ Follow these steps to create a VM from a managed disk:
121
123
>[!NOTE]
122
124
> The `PrivateIP` parameter is optional. Use this parameter to assign a static IP else the default is a dynamic IP using DHCP.
123
125
124
-
Here is an example output. In this example, the same resource group is specified for all the VM resources though you can create and specify separate resource groups for the resources if needed.
126
+
Here's an example output. In this example, the same resource group is specified for all the VM resources though you can create and specify separate resource groups for the resources if needed.
125
127
126
128
```powershell
127
129
PS C:\WINDOWS\system32> $NicRG = "myasevm1rg"
@@ -135,15 +137,15 @@ Follow these steps to create a VM from a managed disk:
135
137
136
138
1. Get the virtual network information and create a new network interface.
137
139
138
-
This sample assumes you are creating a single network interface on the default virtual network `ASEVNET` that is associated with the default resource group `ASERG`. If needed, you could specify an alternate virtual network, or create multiple network interfaces. For more information, see [Add a network interface to a VM via the Azure portal](azure-stack-edge-gpu-manage-virtual-machine-network-interfaces-portal.md).
140
+
This sample assumes you're creating a single network interface on the default virtual network `ASEVNET` that is associated with the default resource group `ASERG`. If needed, you could specify an alternate virtual network, or create multiple network interfaces. For more information, see [Add a network interface to a VM via the Azure portal](azure-stack-edge-gpu-manage-virtual-machine-network-interfaces-portal.md).
@@ -195,14 +197,14 @@ Follow these steps to create a VM from a managed disk:
195
197
196
198
## Delete VM and resources
197
199
198
-
This article used only one resource group to create all the VM resource. Deleting that resource group will delete the VM and all the associated resources.
200
+
This article used only one resource group to create all the VM resource. Deleting that resource group deletes the VM and all the associated resources.
199
201
200
202
1. First view all the resources created under the resource group.
201
203
202
204
```powershell
203
205
Get-AzureRmResource -ResourceGroupName <Resource group name>
0 commit comments