Skip to content

Commit 0a3e081

Browse files
v-dirichardsv-dirichards
authored
Merge pull request #266505 from ChaseCrum/CEOL-15
Batch insert EOL notice
2 parents b659c9a + 9ca8f9b commit 0a3e081

10 files changed

+117
-90
lines changed

‎articles/virtual-machines/custom-data.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,9 @@
1212

1313
# Custom data and cloud-init on Azure Virtual Machines
1414

15+
> [!CAUTION]
16+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
17+
1518
**Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets
1619

1720
You might need to inject a script or other metadata into a Microsoft Azure virtual machine (VM) at provisioning time. In other clouds, this concept is often called *user data*. Microsoft Azure has a similar feature called *custom data*.

‎articles/virtual-machines/enable-nvme-interface.md

Lines changed: 90 additions & 90 deletions
Original file line numberDiff line numberDiff line change
@@ -8,20 +8,20 @@ ms.subservice: sizes
88
ms.topic: how-to #Required; leave this attribute/value as-is.
99
ms.date: 10/30/2023
1010
ms.custom: template-how-to-pattern
11-
12-
1311
---
1412

1513
# Enabling NVMe and SCSI Interface on Virtual Machine
1614

15+
> [!CAUTION]
16+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
1717
1818
NVMe stands for nonvolatile memory express, which is a communication protocol that facilitates faster and more efficient data transfer between servers and storage systems. With NVMe, data can be transferred at the highest throughput and with the fastest response time. Azure now supports the NVMe interface on the Ebsv5 and Ebdsv5 family, offering the highest IOPS and throughput performance for remote disk storage among all the GP v5 VM series.
1919

2020
SCSI (Small Computer System Interface) is a legacy standard for physically connecting and transferring data between computers and peripheral devices. Although Ebsv5 VM sizes still support SCSI, we recommend switching to NVMe for better performance benefits.
2121

2222
## Prerequisites
2323

24-
A new feature has been added to the VM configuration, called DiskControllerType, which allows customers to select their preferred controller type as NVMe or SCSI. If the customer doesn't specify a DiskControllerType value then the platform will automatically choose the default controller based on the VM size configuration. If the VM size is configured for SCSI as the default and supports NVMe, SCSI will be used unless updated to the NVMe DiskControllerType.
24+
A new feature has been added to the VM configuration, called DiskControllerType, which allows customers to select their preferred controller type as NVMe or SCSI. If the customer doesn't specify a DiskControllerType value then the platform will automatically choose the default controller based on the VM size configuration. If the VM size is configured for SCSI as the default and supports NVMe, SCSI will be used unless updated to the NVMe DiskControllerType.
2525

2626
To enable the NVMe interface, the following prerequisites must be met:
2727

@@ -66,7 +66,7 @@ By meeting the above five conditions, you'll be able to enable NVMe on the suppo
6666
### Windows
6767

6868
- [Azure portal - Plan ID: 2019-datacenter-core-smalldisk](https://portal.azure.com/#create/Microsoft.smalldiskWindowsServer2019DatacenterServerCore)
69-
- [Azure portal - Plan ID: 2019-datacenter-core-smalldisk-g2](https://portal.azure.com/#create/Microsoft.smalldiskWindowsServer2019DatacenterServerCore2019-datacenter-core-smalldisk-g2)
69+
- [Azure portal - Plan ID: 2019-datacenter-core-smalldisk-g2](https://portal.azure.com/#create/Microsoft.smalldiskWindowsServer2019DatacenterServerCore2019-datacenter-core-smalldisk-g2)
7070
- [Azure portal - Plan ID: 2019 datacenter-core](https://portal.azure.com/#create/Microsoft.WindowsServer2019DatacenterServerCore)
7171
- [Azure portal - Plan ID: 2019-datacenter-core-g2](https://portal.azure.com/#create/Microsoft.WindowsServer2019DatacenterServerCore2019-datacenter-core-g2)
7272
- [Azure portal - Plan ID: 2019-datacenter-core-with-containers-smalldisk](https://portal.azure.com/#create/Microsoft.smalldiskWindowsServer2019DatacenterServerCorewithContainers)
@@ -97,7 +97,7 @@ By meeting the above five conditions, you'll be able to enable NVMe on the suppo
9797

9898

9999
## Launching a VM with NVMe interface
100-
NVMe can be enabled during VM creation using various methods such as: Azure portal, CLI, PowerShell, and ARM templates. To create an NVMe VM, you must first enable the NVMe option on a VM and select the NVMe controller disk type for the VM. Note that the NVMe diskcontrollertype can be enabled during creation or updated to NVMe when the VM is stopped and deallocated, provided that the VM size supports NVMe.
100+
NVMe can be enabled during VM creation using various methods such as: Azure portal, CLI, PowerShell, and ARM templates. To create an NVMe VM, you must first enable the NVMe option on a VM and select the NVMe controller disk type for the VM. Note that the NVMe diskcontrollertype can be enabled during creation or updated to NVMe when the VM is stopped and deallocated, provided that the VM size supports NVMe.
101101

102102
### Azure portal View
103103

@@ -118,95 +118,95 @@ NVMe can be enabled during VM creation using various methods such as: Azure port
118118
```json
119119

120120

121-
{
122-
    "apiVersion": "2022-08-01",
123-
    "type": "Microsoft.Compute/virtualMachines",
124-
    "name": "[variables('vmName')]",
125-
    "location": "[parameters('location')]",
126-
    "identity": {
127-
        "type": "userAssigned",
128-
        "userAssignedIdentities": {
129-
            "/subscriptions/ <EnterSubscriptionIdHere> /resourcegroups/ManagedIdentities/providers/Microsoft.ManagedIdentity/userAssignedIdentities/KeyVaultReader": {}
130-
        }
131-
    },
132-
    "dependsOn": [
133-
        "[resourceId('Microsoft.Network/networkInterfaces/', variables('nicName'))]"
134-
    ],
135-
    "properties": {
136-
        "hardwareProfile": {
137-
            "vmSize": "[parameters('vmSize')]"
138-
        },
139-
        "osProfile": "[variables('vOsProfile')]",
140-
        "storageProfile": {
141-
            "imageReference": "[parameters('osDiskImageReference')]",
142-
            "osDisk": {
143-
                "name": "[variables('diskName')]",
144-
                "caching": "ReadWrite",
145-
                "createOption": "FromImage"
146-
            },
147-
            "copy": [
148-
                {
149-
                    "name": "dataDisks",
150-
                    "count": "[parameters('numDataDisks')]",
151-
                    "input": {
152-
                        "caching": "[parameters('dataDiskCachePolicy')]",
153-
                        "writeAcceleratorEnabled": "[parameters('writeAcceleratorEnabled')]",
154-
                        "diskSizeGB": "[parameters('dataDiskSize')]",
155-
                        "lun": "[add(copyIndex('dataDisks'), parameters('lunStartsAt'))]",
156-
                        "name": "[concat(variables('vmName'), '-datadisk-', copyIndex('dataDisks'))]",
157-
                        "createOption": "Attach",
158-
                        "managedDisk": {
159-
                            "storageAccountType": "[parameters('storageType')]",
160-
                            "id": "[resourceId('Microsoft.Compute/disks/', concat(variables('vmName'), '-datadisk-', copyIndex('dataDisks')))]"
161-
                        }
162-
                    }
163-
                }
164-
            ],
165-
            "diskControllerTypes": "NVME"
166-
        },
167-
        "securityProfile": {
168-
            "encryptionAtHost": "[parameters('encryptionAtHost')]"
169-
        },
170-
                          
171-
        "networkProfile": {
172-
            "networkInterfaces": [
173-
                {
174-
                    "id": "[resourceId('Microsoft.Network/networkInterfaces', variables('nicName'))]"
175-
                }
176-
            ]
177-
        },
178-
        "availabilitySet": {
179-
            "id": "[resourceId('Microsoft.Compute/availabilitySets', parameters('availabilitySetName'))]"
180-
        }
181-
    },
182-
    "tags": {
183-
        "vmName": "[variables('vmName')]",
184-
185-
      "location": "[parameters('location')]",
186-
187-
                "dataDiskSize": "[parameters('dataDiskSize')]",
188-
189-
                "numDataDisks": "[parameters('numDataDisks')]",
190-
191-
                "dataDiskCachePolicy": "[parameters('dataDiskCachePolicy')]",
192-
193-
                "availabilitySetName": "[parameters('availabilitySetName')]",
194-
195-
                "customScriptURL": "[parameters('customScriptURL')]",
196-
197-
                "SkipLinuxAzSecPack": "True",
198-
199-
                "SkipASMAzSecPack": "True",
200-
201-
                "EnableCrashConsistentRestorePoint": "[parameters('enableCrashConsistentRestorePoint')]"
202-
203-
            }
121+
{
122+
    "apiVersion": "2022-08-01",
123+
    "type": "Microsoft.Compute/virtualMachines",
124+
    "name": "[variables('vmName')]",
125+
    "location": "[parameters('location')]",
126+
    "identity": {
127+
        "type": "userAssigned",
128+
        "userAssignedIdentities": {
129+
            "/subscriptions/ <EnterSubscriptionIdHere> /resourcegroups/ManagedIdentities/providers/Microsoft.ManagedIdentity/userAssignedIdentities/KeyVaultReader": {}
130+
        }
131+
    },
132+
    "dependsOn": [
133+
        "[resourceId('Microsoft.Network/networkInterfaces/', variables('nicName'))]"
134+
    ],
135+
    "properties": {
136+
        "hardwareProfile": {
137+
            "vmSize": "[parameters('vmSize')]"
138+
        },
139+
        "osProfile": "[variables('vOsProfile')]",
140+
        "storageProfile": {
141+
            "imageReference": "[parameters('osDiskImageReference')]",
142+
            "osDisk": {
143+
                "name": "[variables('diskName')]",
144+
                "caching": "ReadWrite",
145+
                "createOption": "FromImage"
146+
            },
147+
            "copy": [
148+
                {
149+
                    "name": "dataDisks",
150+
                    "count": "[parameters('numDataDisks')]",
151+
                    "input": {
152+
                        "caching": "[parameters('dataDiskCachePolicy')]",
153+
                        "writeAcceleratorEnabled": "[parameters('writeAcceleratorEnabled')]",
154+
                        "diskSizeGB": "[parameters('dataDiskSize')]",
155+
                        "lun": "[add(copyIndex('dataDisks'), parameters('lunStartsAt'))]",
156+
                        "name": "[concat(variables('vmName'), '-datadisk-', copyIndex('dataDisks'))]",
157+
                        "createOption": "Attach",
158+
                        "managedDisk": {
159+
                            "storageAccountType": "[parameters('storageType')]",
160+
                            "id": "[resourceId('Microsoft.Compute/disks/', concat(variables('vmName'), '-datadisk-', copyIndex('dataDisks')))]"
161+
                        }
162+
                    }
163+
                }
164+
            ],
165+
            "diskControllerTypes": "NVME"
166+
        },
167+
        "securityProfile": {
168+
            "encryptionAtHost": "[parameters('encryptionAtHost')]"
169+
        },
170+
                          
171+
        "networkProfile": {
172+
            "networkInterfaces": [
173+
                {
174+
                    "id": "[resourceId('Microsoft.Network/networkInterfaces', variables('nicName'))]"
175+
                }
176+
            ]
177+
        },
178+
        "availabilitySet": {
179+
            "id": "[resourceId('Microsoft.Compute/availabilitySets', parameters('availabilitySetName'))]"
180+
        }
181+
    },
182+
    "tags": {
183+
        "vmName": "[variables('vmName')]",
184+
185+
      "location": "[parameters('location')]",
186+
187+
                "dataDiskSize": "[parameters('dataDiskSize')]",
188+
189+
                "numDataDisks": "[parameters('numDataDisks')]",
190+
191+
                "dataDiskCachePolicy": "[parameters('dataDiskCachePolicy')]",
192+
193+
                "availabilitySetName": "[parameters('availabilitySetName')]",
194+
195+
                "customScriptURL": "[parameters('customScriptURL')]",
196+
197+
                "SkipLinuxAzSecPack": "True",
198+
199+
                "SkipASMAzSecPack": "True",
200+
201+
                "EnableCrashConsistentRestorePoint": "[parameters('enableCrashConsistentRestorePoint')]"
202+
203+
            }
204204

205205
        }
206206
```
207-
208207

209-
>[!TIP]
208+
209+
>[!TIP]
210210
> Use the same parameter **DiskControllerType** if you are using the PowerShell or CLI tools to launch the NVMe supported VM.
211211
212212
## Next steps

‎articles/virtual-machines/fsv2-series.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,9 @@ ms.author: priyashan
1111

1212
# Fsv2-series
1313

14+
> [!CAUTION]
15+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
16+
1417
**Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets :heavy_check_mark: Uniform scale sets
1518

1619
The Fsv2-series run on the 3rd Generation Intel® Xeon® Platinum 8370C (Ice Lake), the Intel® Xeon® Platinum 8272CL (Cascade Lake) processors, or the Intel® Xeon® Platinum 8168 (Skylake) processors. It features a sustained all core Turbo clock speed of 3.4 GHz and a maximum single-core turbo frequency of 3.7 GHz. Intel® AVX-512 instructions are new on Intel Scalable Processors. These instructions provide up to a 2X performance boost to vector processing workloads on both single and double precision floating point operations. In other words, they're really fast for any computational workload.

‎articles/virtual-machines/generalize.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,9 @@ ms.custom: portal
1212

1313
# Remove machine specific information by deprovisioning or generalizing a VM before creating an image
1414

15+
> [!CAUTION]
16+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
17+
1518
Generalizing or deprovisioning a VM is not necessary for creating an image in an [Azure Compute Gallery](shared-image-galleries.md#generalized-and-specialized-images) unless you specifically want to create an image that has no machine specific information, like user accounts. Generalizing is still required when creating a managed image outside of a gallery.
1619

1720
Generalizing removes machine specific information so the image can be used to create multiple VMs. Once the VM has been generalized or deprovisioned, you need to let the platform know so that the boot sequence can be set correctly.

‎articles/virtual-machines/hb-hc-known-issues.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ author: ju-shim
1313

1414
# Known issues with HB-series and N-series VMs
1515

16+
> [!CAUTION]
17+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
18+
1619
**Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets :heavy_check_mark: Uniform scale sets
1720

1821
This article attempts to list recent common issues and their solutions when using the [HB-series](sizes-hpc.md) and [N-series](sizes-gpu.md) HPC and GPU VMs.

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ author: ju-shim
1313

1414
# HB-series virtual machines overview
1515

16+
> [!CAUTION]
17+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
18+
1619
**Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets :heavy_check_mark: Uniform scale sets
1720

1821
Maximizing high performance compute (HPC) application performance on AMD EPYC requires a thoughtful approach memory locality and process placement. Below we outline the AMD EPYC architecture and our implementation of it on Azure for HPC applications. We will use the term “pNUMA” to refer to a physical NUMA domain, and “vNUMA” to refer to a virtualized NUMA domain.

‎articles/virtual-machines/hbv2-series-overview.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,9 @@ author: ju-shim
1515

1616
# HBv2 series virtual machine overview
1717

18+
> [!CAUTION]
19+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
20+
1821
**Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets :heavy_check_mark: Uniform scale sets
1922

2023
Maximizing high performance compute (HPC) application performance on AMD EPYC requires a thoughtful approach memory locality and process placement. Below we outline the AMD EPYC architecture and our implementation of it on Azure for HPC applications. We use the term **pNUMA** to refer to a physical NUMA domain, and **vNUMA** to refer to a virtualized NUMA domain.

‎articles/virtual-machines/hbv3-series-overview.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,9 @@ author: ju-shim
1414

1515
# HBv3-series virtual machine overview
1616

17+
> [!CAUTION]
18+
> This article references CentOS, a Linux distribution that is nearing End Of Life (EOL) status. Please consider your use and planning accordingly.
19+
1720
**Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets :heavy_check_mark: Uniform scale sets
1821

1922
An [HBv3-series](hbv3-series.md) server features 2 * 64-core EPYC 7V73X CPUs for a total of 128 physical "Zen3" cores with AMD 3D V-Cache. Simultaneous Multithreading (SMT) is disabled on HBv3. These 128 cores are divided into 16 sections (8 per socket), each section containing 8 processor cores with uniform access to a 96 MB L3 cache. Azure HBv3 servers also run the following AMD BIOS settings:

0 commit comments

Comments
 (0)