Skip to content

Commit ea1bcff

Browse files
ShawnJacksonShawnJackson
authored
Merge pull request #174206 from paulth1/virtual-machines-series-retirement
edit pass: Virtual machines series retirement
2 parents b1ace92 + fc5c7d3 commit ea1bcff

File tree

2 files changed

+77
-47
lines changed

2 files changed

+77
-47
lines changed

‎articles/virtual-machines/h-series-retirement.md

Lines changed: 44 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: H-series-retirement
3-
description: H-series retirement starting September 1, 2021
2+
title: H-series retirement
3+
description: H-series retirement started September 1, 2021.
44
author: vermagit
55
ms.service: virtual-machines
66
ms.subservice: vm-sizes-hpc
@@ -9,44 +9,66 @@ ms.date: 08/02/2021
99
ms.author: amverma
1010
---
1111

12-
# Migrate your H and H_Promo series virtual machines by August 31, 2022
13-
As Microsoft Azure has introduced newer generations of High Performance Computing (HPC), General Purpose, and Memory Optimized virtual machines, we recommend migrating workloads from original H-series (inclusive of H-series promo) virtual machines to our newer offerings.
12+
# Migrate your H and H-series Promo virtual machines by August 31, 2022
1413

15-
Azure [HC](hc-series.md), [HBv2](hbv2-series.md), [HBv3](hbv3-series.md), [Dv4](dv4-dsv4-series.md), [Dav4](dav4-dasv4-series.md), [Ev4](ev4-esv4-series.md), and [Eav4](eav4-easv4-series.md) virtual machines have greater memory bandwidth, improved networking capabilities, and better cost/performance across a broad variety of HPC workloads. Consequently, we are retiring our H-series Azure Virtual Machine sizes (H8, H8m, H16, H16r, H16m, H16mr, H8 Promo, H8m Promo, H16 Promo, H16r Promo, H16m Promo, and H16mr Promo) on 31 August 2022.
14+
Microsoft Azure has introduced newer generations of high-performance computing (HPC), general purpose, and memory-optimized virtual machines (VMs). For this reason, we recommend that you migrate workloads from the original H-series and H-series Promo VMs to our newer offerings.
1615

17-
## How does the H-series migration affect me?
16+
Azure [HC](hc-series.md), [HBv2](hbv2-series.md), [HBv3](hbv3-series.md), [Dv4](dv4-dsv4-series.md), [Dav4](dav4-dasv4-series.md), [Ev4](ev4-esv4-series.md), and [Eav4](eav4-easv4-series.md) VMs have greater memory bandwidth, improved networking capabilities, and better cost and performance across various HPC workloads. On August 31, 2022, we're retiring the following H-series Azure VM sizes:
1817

19-
After 31 August 2022, any remaining H-series virtual machine subscriptions stated above will be set to a deallocated state, will stop working, and will no longer incur billing charges.
18+
- H8
19+
- H8m
20+
- H16
21+
- H16r
22+
- H16m
23+
- H16mr
24+
- H8 Promo
25+
- H8m Promo
26+
- H16 Promo
27+
- H16r Promo
28+
- H16m Promo
29+
- H16mr Promo
2030

21-
The current VM size retirement only impacts the VM sizes in the [H-series](h-series.md), including H-series promo.
31+
## How does the H-series migration affect me?
2232

23-
## What actions should I take?
33+
After August 31, 2022, any remaining H-series VM subscriptions in the preceding list will be set to a deallocated state. They'll stop working and no longer incur billing charges.
2434

25-
You will need to resize or deallocate your H-series virtual machines. We recommend migrating workloads from original H-series (inclusive of H-series promo) virtual machines to our newer offerings.
35+
The current VM size retirement only affects the VM sizes in the [H series](h-series.md), which includes the H-series Promo.
2636

27-
For HPC workloads, [HC](hc-series.md), [HBv2](hbv2-series.md), and [HBv3](hbv3-series.md) VMs offer substantially higher levels of HPC workload performance and cost efficiency due to large improvements in CPU core architecture, higher memory bandwidth, larger L3 caches, and enhanced InfiniBand networking hardware and software support as compared to H-series. As a result, HC, HBv2, and HBv3-series will in general offer substantially better performance per unit of cost (maximizing performance for a fixed amount of spend) and cost per performance (minimizing cost for a fixed amount of performance).
37+
## What actions should I take?
2838

29-
For General Purpose workloads, [Dv4](dv4-dsv4-series.md), [Dav4](dav4-dasv4-series.md), and Dv5 VMs offer the same or better CPU performance at identical or larger core counts, a comparable amount of memory per physical CPU core, better Azure Networking capabilities, and lower overall cost.
39+
You'll need to resize or deallocate your H-series VMs. We recommend that you migrate workloads from the original H-series VMs and the H-series Promo VMs to our newer offerings.
3040

31-
For Memory Optimized workloads, [Ev4](ev4-esv4-series.md), [Eav4](eav4-easv4-series.md), and Ev5 VMs offer the same or better CPU performance at identical or larger core counts, a comparable amount of memory per physical CPU core, better Azure Networking capabilities, and lower overall cost.
41+
**HPC workloads:** [HC](hc-series.md), [HBv2](hbv2-series.md), and [HBv3](hbv3-series.md) VMs offer substantially higher levels of HPC workload performance and cost efficiency because of:
3242

33-
[H-series](h-series.md) VMs (inclusive of H-series Promo) will not be retired until September 2022, so we are providing this guide in advance to give customers a long window to assess, plan, and execute their migration.
43+
- Large improvements in CPU core architecture.
44+
- Higher memory bandwidth.
45+
- Larger L3 caches.
46+
- Enhanced InfiniBand networking hardware and software support as compared to H series.
3447

48+
As a result, HC, HBv2, and HBv3 series will in general offer substantially better performance per unit of cost (maximizing performance for a fixed amount of spend) and cost per performance (minimizing cost for a fixed amount of performance).
3549

36-
### Migration Steps
37-
1. Choose a series and size for migration.
38-
2. Get quota for the target VM series
39-
3. Resize the current H-series VM size to the target size
50+
**General purpose workloads:** [Dv4](dv4-dsv4-series.md), [Dav4](dav4-dasv4-series.md), and Dv5 VMs offer the same or better CPU performance at identical or larger core counts, a comparable amount of memory per physical CPU core, better Azure networking capabilities, and lower overall cost.
4051

52+
**Memory-optimized workloads:** [Ev4](ev4-esv4-series.md), [Eav4](eav4-easv4-series.md), and Ev5 VMs offer the same or better CPU performance at identical or larger core counts, a comparable amount of memory per physical CPU core, better Azure networking capabilities, and lower overall cost.
4153

42-
### Breaking Changes
43-
If you use H-series VM sizes that expose an InfiniBand networking interface (such as those with an ‘r’ in the VM size name) and you want your new VM sizes to also support InfiniBand networking, you will no longer be able to use legacy OS images with built-in InfiniBand driver support (CentOS 7.4 and prior, Windows Server 2012). Instead, use modern OS images such as those on the Azure Marketplace that support modern operating systems (CentOS 7.5 and newer, Windows Server 2016 and newer) and standard OFED drivers. See the [supported software stack](hbv3-series.md#get-started), including supported OS for the respective VM sizes.
54+
[H-series](h-series.md) and H-series Promo VMs won't be retired until September 2022. We're providing this guide in advance to give you a long window to assess, plan, and execute your migration.
4455

56+
### Migration steps
4557

46-
### Get quota for the target VM family
58+
1. Choose a series and size for migration.
59+
1. Get a quota for the target VM series.
60+
1. Resize the current H-series VM size to the target size.
61+
62+
### Breaking changes
63+
64+
If you use H-series VM sizes that expose an InfiniBand networking interface, such as those sizes with an "r" in the VM size name, and you want your new VM sizes to also support InfiniBand networking, you'll no longer be able to use legacy OS images with built-in InfiniBand driver support (CentOS 7.4 and prior, Windows Server 2012).
65+
66+
Instead, use modern OS images such as those available in Azure Marketplace that support modern operating systems (CentOS 7.5 and newer, Windows Server 2016 and newer) and standard OFED drivers. See the [supported software stack](hbv3-series.md#get-started), which includes the supported OS for the respective VM sizes.
67+
68+
### Get a quota for the target VM family
4769

4870
Follow the guide to [request an increase in vCPU quota by VM family](../azure-portal/supportability/per-vm-quota-requests.md).
4971

72+
### Resize the current VM
5073

51-
### Resize the current virtual machine
5274
You can [resize the virtual machine](resize-vm.md).

‎articles/virtual-machines/hb-series-retirement.md

Lines changed: 33 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: HB-series-retirement
3-
description: HB-series retirement starting September 1, 2021
2+
title: HB-series retirement
3+
description: HB-series retirement started September 1, 2021.
44
author: vermagit
55
ms.service: virtual-machines
66
ms.subservice: vm-sizes-hpc
@@ -10,46 +10,54 @@ ms.author: amverma
1010
---
1111

1212
# Migrate your HB-series virtual machines by August 31, 2024
13-
As Microsoft Azure has introduced HBv2 and HBv3-series virtual machines for high performance computing (HPC), we recommend migrating workloads from original HB-series virtual machines to our newer offerings.
1413

15-
Azure [HBv2](hbv2-series.md) and [HBv3](hbv3-series.md) virtual machines have greater memory bandwidth, improved remote direct memory access (RDMA) networking capabilities, larger and faster local solid-state drives, and better cost/performance across a broad variety of HPC workloads. Consequently, we are retiring our HB-series Azure Virtual Machine sizes on 31 August 2024.
14+
Microsoft Azure has introduced HBv2 and HBv3-series virtual machines (VMs) for high-performance computing (HPC). For this reason, we recommend that you migrate workloads from original HB-series VMs to our newer offerings.
1615

17-
## How does the HB-series migration affect me?
16+
Azure [HBv2](hbv2-series.md) and [HBv3](hbv3-series.md) VMs have greater memory bandwidth, improved remote direct memory access (RDMA) networking capabilities, larger and faster local solid-state drives, and better cost and performance across various HPC workloads. As a result, we're retiring our HB-series Azure VM sizes on August 31, 2024.
17+
18+
## How does the HB-series migration affect me?
19+
20+
After August 31, 2024, any remaining HB-size VM subscriptions will be set to a deallocated state. They'll stop working and no longer incur billing charges.
1821

19-
After 31 August 2024, any remaining HB size virtual machines subscriptions will be set to a deallocated state, will stop working, and will no longer incur billing charges.
2022
> [!NOTE]
21-
> This VM size retirement only impacts the VM sizes in the HB-series. This retirement announcement does not apply to the newer HBv2, HBv3 and HC series virtual machines.
23+
> This VM size retirement only affects the VM sizes in the HB series. This retirement announcement doesn't apply to the newer HBv2, HBv3, and HC-series VMs.
2224
23-
## What actions should I take?
25+
## What actions should I take?
2426

25-
You will need to resize or deallocate your H-series virtual machines. We recommend migrating workloads from original H-series (inclusive of H-series promo) virtual machines to our newer offerings.
27+
You'll need to resize or deallocate your H-series VMs. We recommend that you migrate workloads from the original H-series VMs and the H-series Promo VMs to our newer offerings.
2628

27-
[HBv2](hbv2-series.md), and [HBv3](hbv3-series.md) VMs offer substantially higher levels of HPC workload performance and cost efficiency due to large improvements in CPU core architecture, higher memory bandwidth, larger L3 caches, and enhanced InfiniBand networking as compared to HB-series. As a result, HBv2 and HBv3-series will in general offer substantially better performance per unit of cost (i.e. maximizing performance for a fixed amount of spend) as well as cost per performance (i.e. minimizing cost for a fixed amount of performance).
29+
[HBv2](hbv2-series.md) and [HBv3](hbv3-series.md) VMs offer substantially higher levels of HPC workload performance and cost efficiency because of:
2830

29-
All regions containing HB-series VMs contain HBv2 and HBv3-series virtual machines, so existing workloads running on HB-series VMs can be migrated without concern for geographic placement or for access to additional services in those regions.
31+
- Large improvements in CPU core architecture.
32+
- Higher memory bandwidth.
33+
- Larger L3 caches.
34+
- Enhanced InfiniBand networking as compared to HB series.
3035

31-
[HB-series](hb-series.md) VMs will not be retired until September 2024, so we are providing this guide in advance to give customers a long window to assess, plan, and execute their migration.
36+
As a result, HBv2 and HBv3 series will in general offer substantially better performance per unit of cost (maximizing performance for a fixed amount of spend) and cost per performance (minimizing cost for a fixed amount of performance).
3237

33-
### Recommendations for Workload Migration from HB-series Virtual Machines
38+
All regions that contain HB-series VMs contain HBv2 and HBv3-series VMs. Existing workloads that run on HB-series VMs can be migrated without concern for geographic placement or for access to more services in those regions.
3439

35-
| Current VM Size | Target VM Size | Difference in Specification |
36-
|---|---|---|
37-
|Standard_HB60rs |Standard_HB120rs_v2 <br> Standard_HB120rs_v3 <br> Standard_HB120-64rs_v3 |Newer CPU: AMD Rome and MiIan (+20-30% IPC) <br> Memory: Up to 2x more RAM <br> Memory Bandwidth: Up to 30% more memory bandwidth <br> InfiniBand: 200 Gb HDR (2x higher bandwidth) <br> Max data disks: Up to 32 (+8x) |
38-
|Standard_HB60-45rs |Standard_HB120-96rs_v3 <br> Standard_HB120-64rs_v3 <br> Standard_HB120-32rs_v3 |Newer CPU: AMD Rome and MiIan (+20-30% IPC) <br> Memory: Up to 2x more RAM <br> Memory Bandwidth: Up to 30% more memory bandwidth <br> InfiniBand: 200 Gb HDR (2x higher bandwidth) <br> Max data disks: Up to 32 (+8x) |
39-
|Standard_HB60-30rs |Standard_HB120-32rs_v3 <br> Standard_HB120-16rs_v3 |Newer CPU: AMD Rome and MiIan (+20-30% IPC) <br> Memory: Up to 2x more RAM <br> Memory Bandwidth: Up to 30% more memory bandwidth <br> InfiniBand: 200 Gb HDR (2x higher bandwidth) <br> Max data disks: Up to 32 (+8x) |
40-
|Standard_HB60-15rs |Standard_HB120-16rs_v3 |Newer CPU: AMD Rome and MiIan (+20-30% IPC) <br> Memory: Up to 2x more RAM <br> Memory Bandwidth: Up to 30% more memory bandwidth <br> InfiniBand: 200 Gb HDR (2x higher bandwidth) <br> Max data disks: Up to 32 (+8x) |
40+
[HB-series](hb-series.md) VMs won't be retired until September 2024. We're providing this guide in advance to give you a long window to assess, plan, and execute your migration.
4141

42+
### Recommendations for workload migration from HB-series VMs
43+
44+
| Current VM size | Target VM size | Difference in specification |
45+
|---|---|---|
46+
|Standard_HB60rs |Standard_HB120rs_v2 <br> Standard_HB120rs_v3 <br> Standard_HB120-64rs_v3 |Newer CPU: AMD Rome and MiIan (+20-30% IPC) <br> Memory: Up to 2x more RAM <br> Memory bandwidth: Up to 30% more memory bandwidth <br> InfiniBand: 200 Gb HDR (2x higher bandwidth) <br> Max data disks: Up to 32 (+8x) |
47+
|Standard_HB60-45rs |Standard_HB120-96rs_v3 <br> Standard_HB120-64rs_v3 <br> Standard_HB120-32rs_v3 |Newer CPU: AMD Rome and MiIan (+20-30% IPC) <br> Memory: Up to 2x more RAM <br> Memory bandwidth: Up to 30% more memory bandwidth <br> InfiniBand: 200 Gb HDR (2x higher bandwidth) <br> Max data disks: Up to 32 (+8x) |
48+
|Standard_HB60-30rs |Standard_HB120-32rs_v3 <br> Standard_HB120-16rs_v3 |Newer CPU: AMD Rome and MiIan (+20-30% IPC) <br> Memory: Up to 2x more RAM <br> Memory bandwidth: Up to 30% more memory bandwidth <br> InfiniBand: 200 Gb HDR (2x higher bandwidth) <br> Max data disks: Up to 32 (+8x) |
49+
|Standard_HB60-15rs |Standard_HB120-16rs_v3 |Newer CPU: AMD Rome and MiIan (+20-30% IPC) <br> Memory: Up to 2x more RAM <br> Memory bandwidth: Up to 30% more memory bandwidth <br> InfiniBand: 200 Gb HDR (2x higher bandwidth) <br> Max data disks: Up to 32 (+8x) |
4250

43-
### Migration Steps
44-
1. Choose a series and size for migration.
45-
2. Get quota for the target VM series
46-
3. Resize the current HB-series VM size to the target size
51+
### Migration steps
4752

53+
1. Choose a series and size for migration.
54+
1. Get a quota for the target VM series.
55+
1. Resize the current HB-series VM size to the target size.
4856

49-
### Get quota for the target VM family
57+
### Get a quota for the target VM family
5058

5159
Follow the guide to [request an increase in vCPU quota by VM family](../azure-portal/supportability/per-vm-quota-requests.md).
5260

61+
### Resize the current VM
5362

54-
### Resize the current virtual machine
5563
You can [resize the virtual machine](resize-vm.md).

0 commit comments

Comments
 (0)