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/virtual-machine-scale-sets/quick-create-portal.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,9 +12,6 @@ ms.custom: mimckitt, mode-ui
12
12
13
13
# Quickstart: Create a Virtual Machine Scale Set in the Azure portal
14
14
15
-
> [!CAUTION]
16
-
> This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and plan accordingly. For more information, see the [CentOS End Of Life guidance](~/articles/virtual-machines/workloads/centos/centos-end-of-life.md).
17
-
18
15
**Applies to:**:heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Uniform scale sets
19
16
20
17
> [!NOTE]
@@ -56,7 +53,7 @@ First, create a public Standard Load Balancer by using the portal. The name and
56
53
57
54
58
55
## Create Virtual Machine Scale Set
59
-
You can deploy a scale set with a Windows Server image or Linux image such as RHEL, CentOS, Ubuntu, or SLES.
56
+
You can deploy a scale set with a Windows Server image or Linux image such as RHEL, Ubuntu, or SLES.
60
57
61
58
1. Type **Scale set** in the search box. In the results, under **Marketplace**, select **Virtual Machine Scale Sets**. Select **Create** on the **Virtual Machine Scale Sets** page, which opens the **Create a Virtual Machine Scale Set** page.
62
59
1. In the **Basics** tab, under **Project details**, make sure the correct subscription is selected and select *myVMSSResourceGroup* from resource group list.
# Tutorial: Automatically scale a Virtual Machine Scale Set with the Azure CLI
14
14
15
-
> [!CAUTION]
16
-
> This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and plan accordingly. For more information, see the [CentOS End Of Life guidance](~/articles/virtual-machines/workloads/centos/centos-end-of-life.md).
17
-
18
15
When you create a scale set, you define the number of VM instances that you wish to run. As your application demand changes, you can automatically increase or decrease the number of VM instances. The ability to autoscale lets you keep up with customer demand or respond to application performance changes throughout the lifecycle of your app. In this tutorial you learn how to:
> This article references CentOS, a Linux distribution that reached the end of support. Consider your use and plan accordingly. For more information, see the [guidance for CentOS end of support](~/articles/virtual-machines/workloads/centos/centos-end-of-life.md).
15
-
16
13
The following lists provide up-to-date information on which OS images are tagged as supported for remote NVM Express (NVMe).
17
14
18
15
> [!IMPORTANT]
@@ -29,7 +26,6 @@ For more information about enabling the NVMe interface on virtual machines creat
Copy file name to clipboardExpand all lines: articles/virtual-machines/extensions/hpc-compute-infiniband-linux.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,9 +15,6 @@ author: ju-shim
15
15
16
16
# InfiniBand Driver Extension for Linux
17
17
18
-
> [!CAUTION]
19
-
> This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and plan accordingly. For more information, see the [CentOS End Of Life guidance](~/articles/virtual-machines/workloads/centos/centos-end-of-life.md).
20
-
21
18
This extension installs InfiniBand OFED drivers on InfiniBand and SR-IOV-enabled ('r' sizes) [HB-series](../sizes-hpc.md) and [N-series](../sizes-gpu.md) VMs running Linux. Depending on the VM family, the extension installs the appropriate drivers for the Connect-X NIC. It does not install the InfiniBand ND drivers on the non-SR-IOV enabled [HB-series](../sizes-hpc.md) and [N-series](../sizes-gpu.md) VMs.
22
19
23
20
Instructions on manual installation of the OFED drivers are available in [Enable InfiniBand on HPC VMs](enable-infiniband.md#manual-installation).
@@ -33,7 +30,6 @@ This extension supports the following OS distros, depending on driver support fo
33
30
| Distribution | Version | InfiniBand NIC drivers |
description: Learn about the HBv2-series VM size in Azure.
4
4
services: virtual-machines
5
5
ms.custom:
@@ -15,9 +15,6 @@ author: padmalathas
15
15
16
16
# HBv2 series virtual machine overview
17
17
18
-
> [!CAUTION]
19
-
> This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and plan accordingly. For more information, see the [CentOS End Of Life guidance](~/articles/virtual-machines/workloads/centos/centos-end-of-life.md).
20
-
21
18
**Applies to:**:heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets :heavy_check_mark: Uniform scale sets.
22
19
23
20
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.
@@ -31,7 +28,7 @@ NUMA domains within VM OS = 4
31
28
C-states = Enabled
32
29
```
33
30
34
-
As a result, the server boots with 4 NUMA domains (2 per socket) each 32 cores in size. Each NUMA has direct access to 4 channels of physical DRAM operating at 3200 MT/s.
31
+
As a result, the server boots with 4 NUMA domains (2 per socket). Each domain is 32 cores in size. Each NUMA has direct access to 4 channels of physical DRAM operating at 3,200 MT/s.
35
32
36
33
To provide room for the Azure hypervisor to operate without interfering with the VM, we reserve 8 physical cores per server.
37
34
@@ -64,7 +61,7 @@ Process pinning works on HBv2-series VMs because we expose the underlying silico
description: Learn about the HBv3-series VM size in Azure.
4
4
services: virtual-machines
5
5
ms.custom:
@@ -14,9 +14,6 @@ author: padmalathas
14
14
15
15
# HBv3-series virtual machine overview
16
16
17
-
> [!CAUTION]
18
-
> This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and plan accordingly. For more information, see the [CentOS End Of Life guidance](~/articles/virtual-machines/workloads/centos/centos-end-of-life.md).
19
-
20
17
**Applies to:**:heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets :heavy_check_mark: Uniform scale sets
21
18
22
19
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:
@@ -28,7 +25,7 @@ NUMA domains within VM OS = 4
28
25
C-states = Enabled
29
26
```
30
27
31
-
As a result, the server boots with 4 NUMA domains (2 per socket) each 32 cores in size. Each NUMA has direct access to 4 channels of physical DRAM operating at 3200 MT/s.
28
+
As a result, the server boots with 4 NUMA domains (2 per socket). Each domain is 32 cores in size. Each NUMA has direct access to 4 channels of physical DRAM operating at 3,200 MT/s.
32
29
33
30
To provide room for the Azure hypervisor to operate without interfering with the VM, we reserve 8 physical cores per server.
34
31
@@ -124,8 +121,8 @@ When paired in a striped array, the NVMe SSD provides up to 7 GB/s reads and 3 G
Copy file name to clipboardExpand all lines: articles/virtual-machines/linux/imaging.md
+5-9Lines changed: 5 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,14 +14,11 @@ ms.reviewer: cynthn
14
14
15
15
# Bringing and creating Linux images in Azure
16
16
17
-
> [!CAUTION]
18
-
> This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and plan accordingly. For more information, see the [CentOS End Of Life guidance](~/articles/virtual-machines/workloads/centos/centos-end-of-life.md).
This overview covers the basic concepts around imaging and how to successfully build and use Linux images in Azure. Before you bring a custom image to Azure, you need to be aware of the types and options available to you.
23
20
24
-
This article will talk through the image decision points and requirements as well as explain key concepts so that you can follow this and be able to create your own custom images to your specification.
21
+
This article talks through the image decision points and requirements as well as explain key concepts so that you can follow this and be able to create your own custom images to your specification.
25
22
26
23
## Difference between managed disks and images
27
24
@@ -36,18 +33,18 @@ Azure images can be made up of multiple OS disks and data disks. When you use a
36
33
37
34
## Generalized and specialized
38
35
39
-
Azure offers two main image types, generalized and specialized. The terms generalized and specialized are originally Windows terms which migrated in to Azure. These types define how the platform will handle the VM when it turns it on. Both types have advantages, disadvantages, and prerequisites. Before you get started, you need to know what image type you will need. Below summarizes the scenarios and type you would need to choose:
36
+
Azure offers two main image types, generalized and specialized. The terms generalized and specialized are originally Windows terms which migrated in to Azure. These types define how the platform handles the VM when it turns it on. Both types have advantages, disadvantages, and prerequisites. Before you get started, you need to know what image type you need. Below summarizes the scenarios and type you would need to choose:
| Create an image that can be configured for use by multiple VMs. You can set the hostname, add an admin user, and perform other tasks during first boot. | Generalized | Azure Compute Gallery or stand-alone managed images |
44
41
| Create an image from a VM snapshot or a backup. | Specialized |Azure Compute Gallery or a managed disk |
45
-
| Quickly create an image that does not need any configuration for creating multiple VMs. |Specialized |Azure Compute Gallery |
42
+
| Quickly create an image that doesn't need any configuration for creating multiple VMs. |Specialized |Azure Compute Gallery |
46
43
47
44
48
45
### Generalized images
49
46
50
-
A generalized image is an image that requires setup to be completed on first boot. For example, on first boot you set the hostname, admin user, and other VM-specific configurations. This is useful when you want the image to be reused multiple times and when you want to pass in parameters during creation. If the generalized image contains the Azure agent, the agent will process the parameters and signal back to the platform that the initial configuration has completed. This process is called [provisioning](./provisioning.md).
47
+
A generalized image is an image that requires setup to be completed on first boot. For example, on first boot you set the hostname, admin user, and other VM-specific configurations. This is useful when you want the image to be reused multiple times and when you want to pass in parameters during creation. If the generalized image contains the Azure agent, the agent processes the parameters and signal back to the platform that the initial configuration has completed. This process is called [provisioning](./provisioning.md).
51
48
52
49
Provisioning requires that a provisioner is included in the image. There are two provisioners:
53
50
-[Azure Linux Agent](../extensions/agent-linux.md)
@@ -57,7 +54,7 @@ These are [prerequisites](./create-upload-generic.md) for creating an image.
57
54
58
55
59
56
### Specialized images
60
-
These are images that are completely configured and don't require VM or special parameters. The platform will just turn the VM on and you will need to handle uniqueness within the VM, like setting a hostname, to avoid DNS conflicts on the same VNET.
57
+
These are images that are completely configured and don't require VM or special parameters. The platform will just turn on the VM, and you need to handle uniqueness within the VM, like setting a hostname, to avoid DNS conflicts on the same VNET.
61
58
62
59
Provisioning agents aren't required for these images, however you may want to have extension handling capabilities. You can install the Linux Agent but disable the provisioning option. Even though you don't need a provisioning agent, the image must fulfill [prerequisites](./create-upload-generic.md) for Azure Images.
63
60
@@ -100,7 +97,6 @@ Azure supports Hyper-V Generation 1 (Gen1) and Generation 2 (Gen2). Gen2 is the
100
97
If you still need to create your own image, ensure it meets the [image prerequisites](./create-upload-generic.md) and upload to Azure. Distribution specific requirements:
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments