Skip to content

Commit d12052e

Browse files
huypubhuypub
authored
Merge pull request #165083 from MicrosoftDocs/release-preview-disk-pools
Release preview disk pools--scheduled release at 10AM of 7/09
2 parents 8d1f887 + 263ade3 commit d12052e

21 files changed

+881
-4
lines changed

‎articles/azure-vmware/attach-disk-pools-to-azure-vmware-solution-hosts.md

Lines changed: 164 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,164 @@
1+
---
2+
title: Attach disk pools to Azure VMware Solution hosts (Preview)
3+
description: Learn how to attach a disk pool surfaced through an iSCSI target as the VMware datastore of an Azure VMware Solution private cloud. Once the datastore is configured, you can create volumes on it and attach them to your VMware instance.
4+
ms.topic: how-to
5+
ms.date: 07/13/2021
6+
7+
#Customer intent: As an Azure service administrator, I want to scale my AVS hosts using disk pools instead of scaling clusters. So that I can use block storage for active working sets and tier less frequently accessed data from vSAN to disks. I can also replicate data from on-premises or primary VMware environment to disk storage for the secondary site.
8+
9+
---
10+
11+
# Attach disk pools to Azure VMware Solution hosts (Preview)
12+
13+
[Azure disk pools](../virtual-machines/disks-pools.md) offer persistent block storage to applications and workloads backed by Azure Disks. You can use disks as the persistent storage for Azure VMware Solution for optimal cost and performance. For example, you can scale up by using disk pools instead of scaling clusters if you host storage-intensive workloads. You can also use disks to replicate data from on-premises or primary VMware environments to disk storage for the secondary site. To scale storage independent of the Azure VMware Solution hosts, we support surfacing [ultra disks](../virtual-machines/disks-types.md#ultra-disk) and [premium SSD](../virtual-machines/disks-types.md#premium-ssd) as the datastores.
14+
15+
>[!IMPORTANT]
16+
>Azure disk pools on Azure VMware Solution (Preview) is currently in public preview.
17+
>This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
18+
>For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
19+
20+
Azure managed disks are attached to one iSCSI controller virtual machine deployed under the Azure VMware Solution resource group. Disks get deployed as storage targets to a disk pool, and each storage target shows as an iSCSI LUN under the iSCSI target. You can expose a disk pool as an iSCSI target connected to Azure VMware Solution hosts as a datastore. A disk pool surfaces as a single endpoint for all underlying disks added as storage targets. Each disk pool can have only one iSCSI controller.
21+
22+
The diagram shows how disk pools work with Azure VMware Solution hosts. Each iSCSI controller accesses managed disk using a standard Azure protocol, and the Azure VMware Solution hosts can access the iSCSI controller over iSCSI.
23+
24+
25+
:::image type="content" source="media/disk-pools/azure-disks-attached-to-managed-iscsi-controllers.png" alt-text="Diagram showing how disk pools work with Azure VMware Solution hosts." border="false":::
26+
27+
28+
## Supported regions
29+
30+
You can only connect the disk pool to an Azure VMware Solution private cloud in the same region. For a list of supported regions, see [Regional availability](/azure/virtual-machines/disks-pools#regional-availability). If your private cloud is deployed in a non-supported region, you can redeploy it in a supported region. Azure VMware Solution private cloud and disk pool colocation provide the best performance with minimal network latency.
31+
32+
33+
## Prerequisites
34+
35+
- Scalability and performance requirements of your workloads are identified. For details, see [Planning for Azure disk pools](../virtual-machines/disks-pools-planning.md).
36+
37+
- [Azure VMware Solution private cloud](deploy-azure-vmware-solution.md) deployed with a [virtual network configured](deploy-azure-vmware-solution.md#step-3-connect-to-azure-virtual-network-with-expressroute). For more information, see [Network planning checklist](tutorial-network-checklist.md) and [Configure networking for your VMware private cloud](tutorial-configure-networking.md).
38+
39+
- If you select ultra disks, use Ultra Performance for the Azure VMware Solution private cloud and then [enable ExpressRoute FastPath](/azure/expressroute/expressroute-howto-linkvnet-arm#configure-expressroute-fastpath).
40+
41+
- If you select premium SSDs, use Standard (1 Gbps) for the Azure VMware Solution private cloud.
42+
43+
- Disk pool as the backing storage deployed and exposed as an iSCSI target with each disk as an individual LUN. For details, see [Deploy an Azure disk pool](../virtual-machines/disks-pools-deploy.md).
44+
45+
>[!IMPORTANT]
46+
> The disk pool must be deployed in the same subscription as the VMware cluster, and it must be attached to the same VNET as the VMware cluster.
47+
48+
## Attach a disk pool to your private cloud
49+
You'll attach to a disk pool surfaced through an iSCSI target as the VMware datastore of an Azure VMware Solution private cloud.
50+
51+
>[!IMPORTANT]
52+
>While in **Public Preview**, only attach a disk pool to a test or non-production cluster.
53+
54+
1. Check if the subscription is registered to `Microsoft.AVS`:
55+
56+
```azurecli
57+
az provider show -n "Microsoft.AVS" --query registrationState
58+
```
59+
60+
If it's not already registered, then register it:
61+
62+
```azurecli
63+
az provider register -n "Microsoft.AVS"
64+
```
65+
66+
1. Check if the subscription is registered to `CloudSanExperience` AFEC in Microsoft.AVS:
67+
68+
```azurecli
69+
az feature show --name "CloudSanExperience" --namespace "Microsoft.AVS"
70+
```
71+
72+
- If it's not already registered, then register it:
73+
74+
```azurecli
75+
az feature register --name "CloudSanExperience" --namespace "Microsoft.AVS"
76+
```
77+
78+
The registration may take approximately 15 minutes to complete and you can check the current status it:
79+
80+
```azurecli
81+
az feature show --name "CloudSanExperience" --namespace "Microsoft.AVS" --query properties.state
82+
```
83+
84+
>[!TIP]
85+
>If the registration is stuck in an intermediate state for longer than 15 minutes to complete, unregister and then re-register the flag:
86+
>
87+
>```azurecli
88+
>az feature unregister --name "CloudSanExperience" --namespace "Microsoft.AVS"
89+
>az feature register --name "CloudSanExperience" --namespace "Microsoft.AVS"
90+
>```
91+
92+
1. Check if the `vmware `extension is installed:
93+
94+
```azurecli
95+
az extension show --name vmware
96+
```
97+
98+
- If the extension is already installed, check if the version is **3.0.0**. If an older version is installed, update the extension:
99+
100+
```azurecli
101+
az extension update --name vmware
102+
```
103+
104+
- If it's not already installed, install it:
105+
106+
```azurecli
107+
az extension add --name vmware
108+
```
109+
110+
3. Create and attach an iSCSI datastore in the Azure VMware Solution private cloud cluster using `Microsoft.StoragePool` provided iSCSI target:
111+
112+
```azurecli
113+
az vmware datastore disk-pool-volume create --name iSCSIDatastore1 --resource-group MyResourceGroup --cluster Cluster-1 --private-cloud MyPrivateCloud --target-id /subscriptions/11111111-1111-1111-1111-111111111111/resourceGroups/ResourceGroup1/providers/Microsoft.StoragePool/diskPools/mpio-diskpool/iscsiTargets/mpio-iscsi-target --lun-name lun0
114+
```
115+
116+
>[!TIP]
117+
>You can display the help on the datastores:
118+
>
119+
> ```azurecli
120+
> az vmware datastore -h
121+
> ```
122+
123+
124+
4. Show the details of an iSCSI datastore in a private cloud cluster:
125+
126+
```azurecli
127+
az vmware datastore show --name MyCloudSANDatastore1 --resource-group MyResourceGroup --cluster -Cluster-1 --private-cloud MyPrivateCloud
128+
```
129+
130+
5. List all the datastores in a private cloud cluster:
131+
132+
```azurecli
133+
az vmware datastore list --resource-group MyResourceGroup --cluster Cluster-1 --private-cloud MyPrivateCloud
134+
```
135+
136+
## Delete an iSCSI datastore from your private cloud
137+
138+
When you delete a private cloud datastore, the disk pool resources don't get deleted. There's no maintenance window required for this operation.
139+
140+
1. Power off the VMs and remove all objects associated with the iSCSI datastores, which includes:
141+
142+
- VMs (remove from inventory)
143+
144+
- Templates
145+
146+
- Snapshots
147+
148+
2. Delete the private cloud datastore:
149+
150+
```azurecli
151+
az vmware datastore delete --name MyCloudSANDatastore1 --resource-group MyResourceGroup --cluster Cluster-1 --private-cloud MyPrivateCloud
152+
```
153+
154+
## Next steps
155+
156+
Now that you've attached a disk pool to your Azure VMware Solution hosts, you may want to learn about:
157+
158+
- [Managing an Azure disk pool](../virtual-machines/disks-pools-manage.md ). Once you've deployed a disk pool, there are various management actions available to you. You can add or remove a disk to or from a disk pool, update iSCSI LUN mapping, or add ACLs.
159+
160+
- [Deleting a disk pool](/azure/virtual-machines/disks-pools-deprovision#delete-a-disk-pool). When you delete a disk pool, all the resources in the managed resource group are also deleted.
161+
162+
- [Disabling iSCSI support on a disk](/azure/virtual-machines/disks-pools-deprovision#disable-iscsi-support). If you disable iSCSI support on a disk pool, you effectively can no longer use a disk pool.
163+
164+
- [Moving disk pools to a different subscription](../virtual-machines/disks-pools-move-resource.md). Move an Azure disk pool to a different subscription, which involves moving the disk pool itself, contained disks, managed resource group, and all the resources.

‎articles/azure-vmware/deploy-azure-vmware-solution.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,9 @@ In the planning phase, you defined whether to use an *existing* or *new* Express
3232

3333
:::image type="content" source="media/connect-expressroute-vnet-workflow.png" alt-text="Diagram showing the workflow for connecting Azure Virtual Network to ExpressRoute in Azure VMware Solution." border="false":::
3434

35+
>[!IMPORTANT]
36+
>[!INCLUDE [disk-pool-planning-note](includes/disk-pool-planning-note.md)]
37+
3538
### Use a new ExpressRoute virtual network gateway
3639

3740
>[!IMPORTANT]

‎articles/azure-vmware/includes/disk-pool-planning-note.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
title: Disk pool planning note for vNet
3+
description: Important note about the importance of deploying a vNet closer to Azure VMware Solution hosts.
4+
ms.topic: include
5+
ms.date: 07/14/2021
6+
7+
# used in:
8+
# articles\azure-vmware\attach-disk-pools-to-azure-vmware-solution.md
9+
# articles\azure-vmware\tutorial-network-checklist.md
10+
# articles\azure-vmware\includes\production-ready-deployment-steps.md
11+
---
12+
13+
14+
If you plan to scale your Azure VMware Solution hosts using [Azure disk pools](../../virtual-machines/disks-pools.md), it's crucial to deploy the vNet close to your hosts with an ExpressRoute virtual network gateway. The closer the storage is to your hosts, the better the performance.

‎articles/azure-vmware/index.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -156,6 +156,8 @@ landingContent:
156156
url: deploy-traffic-manager-balance-workloads.md
157157
- text: Configure alerts and work with metrics
158158
url: configure-alerts-for-azure-vmware-solution.md
159+
- text: Attach disk pools to Azure VMware Solution hosts
160+
url: attach-disk-pools-to-azure-vmware-solution-hosts.md
159161

160162
# card 6 == backup and restore
161163
- title: Backup with Azure Backup Server

‎articles/azure-vmware/media/disk-pools/azure-disks-attached-to-managed-iscsi-controllers.png

179 KB
Loading

‎articles/azure-vmware/production-ready-deployment-steps.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -87,10 +87,10 @@ This network segment is used primarily for testing purposes during the initial d
8787

8888
## Define the virtual network gateway
8989

90-
>[!IMPORTANT]
91-
>You can connect to a virtual network gateway in an Azure Virtual WAN, but it is out of scope for this quick start.
90+
An Azure VMware Solution private cloud requires an Azure Virtual Network and an ExpressRoute circuit.
9291

93-
An Azure VMware Solution private cloud requires an Azure Virtual Network and an ExpressRoute circuit.
92+
>[!IMPORTANT]
93+
>[!INCLUDE [disk-pool-planning-note](includes/disk-pool-planning-note.md)] You can connect to a virtual network gateway in an Azure Virtual WAN, but it is out of scope for this quick start.
9494
9595
Define whether you want to use an *existing* OR *new* ExpressRoute virtual network gateway. If you decide to use a *new* virtual network gateway, you'll create it after you create your private cloud. It's acceptable to use an existing ExpressRoute virtual network gateway, and for planning purposes, make note of which ExpressRoute virtual network gateway you'll use.
9696

‎articles/azure-vmware/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,8 @@
100100
href: deploy-traffic-manager-balance-workloads.md
101101
- name: Configure alerts and work with metrics
102102
href: configure-alerts-for-azure-vmware-solution.md
103+
- name: Attach disk pools to Azure VMware Solution hosts
104+
href: attach-disk-pools-to-azure-vmware-solution-hosts.md
103105
- name: Backup with Azure Backup Server
104106
items:
105107
- name: Set up Backup Server

‎articles/azure-vmware/tutorial-configure-networking.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,9 @@ ms.date: 04/23/2021
88

99
# Tutorial: Configure networking for your VMware private cloud in Azure
1010

11-
An Azure VMware Solution private cloud requires an Azure Virtual Network. Because Azure VMware Solution doesn't support your on-premises vCenter, extra steps for integration with your on-premises environment are needed. Setting up an ExpressRoute circuit and a virtual network gateway is also required.
11+
An Azure VMware Solution private cloud requires an Azure Virtual Network. Because Azure VMware Solution doesn't support your on-premises vCenter, extra steps are needed for integration with your on-premises environment. Setting up an ExpressRoute circuit and a virtual network gateway is also required.
12+
13+
[!INCLUDE [disk-pool-planning-note](includes/disk-pool-planning-note.md)]
1214

1315
In this tutorial, you learn how to:
1416

‎articles/azure-vmware/tutorial-network-checklist.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,9 @@ When deploying a private cloud, you receive IP addresses for vCenter and NSX-T M
3030

3131
The private cloud logical networking comes with pre-provisioned NSX-T. A Tier-0 gateway and Tier-1 gateway are pre-provisioned for you. You can create a segment and attach it to the existing Tier-1 gateway or attach it to a new Tier-1 gateway that you define. NSX-T logical networking components provide East-West connectivity between workloads and provide North-South connectivity to the internet and Azure services.
3232

33+
>[!IMPORTANT]
34+
>[!INCLUDE [disk-pool-planning-note](includes/disk-pool-planning-note.md)]
35+
3336
## Routing and subnet considerations
3437
The Azure VMware Solution private cloud is connected to your Azure virtual network using an Azure ExpressRoute connection. This high bandwidth, low latency connection allows you to access services running in your Azure subscription from your private cloud environment. The routing is Border Gateway Protocol (BGP) based, automatically provisioned, and enabled by default for each private cloud deployment.
3538

‎articles/virtual-machines/TOC.yml

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -968,6 +968,23 @@
968968
href: disks-shared.md
969969
- name: Enable shared disks
970970
href: disks-shared-enable.md
971+
- name: Disk pools
972+
items:
973+
- name: Overview
974+
displayName: Disk pools overview
975+
href: disks-pools.md
976+
- name: Plan for disk pools
977+
href: disks-pools-planning.md
978+
- name: Deploy a disk pool
979+
href: disks-pools-deploy.md
980+
- name: Move a disk pool to a different subscription
981+
href: disks-pools-move-resource.md
982+
- name: Manage a disk pool
983+
href: disks-pools-manage.md
984+
- name: Deprovision a disk pool
985+
href: disks-pools-deprovision.md
986+
- name: Troubleshoot a disk pool
987+
href: disks-pools-troubleshoot.md
971988
- name: Encryption
972989
items:
973990
- name: Disk encryption overview

0 commit comments

Comments
 (0)