Skip to content

Commit 7b802e6

Browse files
author
Julia Shimanskiy
committed
Decom notice for A8-A11 vms on 3 docs
1 parent bf1c56c commit 7b802e6

File tree

3 files changed

+10
-0
lines changed

3 files changed

+10
-0
lines changed

articles/virtual-machines/sizes-general.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,9 @@ General purpose VM sizes provide balanced CPU-to-memory ratio. Ideal for testing
3535

3636
Example D-series use cases include enterprise-grade applications, relational databases, in-memory caching, and analytics.
3737

38+
> [!NOTE]
39+
> The A8 – A11 VMs are planned for retirement on 3/2021. For more information, see [HPC Migration Guide](https://azure.microsoft.com/resources/hpc-migration-guide/).
40+
3841
## Other sizes
3942

4043
- [Compute optimized](sizes-compute.md)

articles/virtual-machines/sizes-hpc.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,10 @@ Azure H-series virtual machines (VMs) are designed to deliver leadership-class p
4242
4343
- **Virtual network** – An Azure [virtual network](https://azure.microsoft.com/documentation/services/virtual-network/) is not required to use the compute-intensive instances. However, for many deployments you need at least a cloud-based Azure virtual network, or a site-to-site connection if you need to access on-premises resources. When needed, create a new virtual network to deploy the instances. Adding compute-intensive VMs to a virtual network in an affinity group is not supported.
4444
- **Resizing** – Because of their specialized hardware, you can only resize compute-intensive instances within the same size family (H-series or compute-intensive A-series). For example, you can only resize an H-series VM from one H-series size to another. In addition, resizing from a non-compute-intensive size to a compute-intensive size is not supported.
45+
46+
> [!NOTE]
47+
> The A8 – A11 VMs are planned for retirement on 3/2021. For more information, see [HPC Migration Guide](https://azure.microsoft.com/resources/hpc-migration-guide/).
48+
4549
## RDMA-capable instances
4650

4751
A subset of the compute-intensive instances (A8, A9, H16r, H16mr, HB and HC) feature a network interface for remote direct memory access (RDMA) connectivity. Selected N-series sizes designated with 'r' such as the NC24rs configurations (NC24rs_v2 and NC24rs_v3) are also RDMA-capable. This interface is in addition to the standard Azure network interface available to other VM sizes.

articles/virtual-machines/sizes-previous-gen.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -165,6 +165,9 @@ The A8-A11 and H-series sizes are also known as *compute-intensive instances*. T
165165

166166
<sup>1</sup>For MPI applications, dedicated RDMA backend network is enabled by FDR InfiniBand network, which delivers ultra-low-latency and high bandwidth.
167167

168+
> [!NOTE]
169+
> The A8 – A11 VMs are planned for retirement on 3/2021. For more information, see [HPC Migration Guide](https://azure.microsoft.com/resources/hpc-migration-guide/).
170+
168171
<br>
169172

170173
### D-series

0 commit comments

Comments
 (0)