Skip to content

Commit 71d7ab2

Browse files
authored
Merge pull request #253176 from robswain/910050-vm-sizing
ADO bug 910050 - update AP5GC resource usage
2 parents a4d995f + 2f34978 commit 71d7ab2

File tree

1 file changed

+21
-13
lines changed

1 file changed

+21
-13
lines changed

articles/private-5g-core/azure-stack-edge-virtual-machine-sizing.md

Lines changed: 21 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -5,27 +5,35 @@ author: robswain
55
ms.author: robswain
66
ms.service: private-5g-core
77
ms.topic: reference
8-
ms.date: 01/27/2023
8+
ms.date: 09/29/2023
99
---
1010

1111
# Azure Stack Edge virtual machine sizing
1212

13-
The following table contains information about the VMs that Azure Private 5G Core (AP5GC) uses when running on an Azure Stack Edge (ASE) device. You can use this information, for example, to check how much space you'll have remaining on your ASE device after installing Azure Private 5G Core.
13+
The following table lists the hardware resources that Azure Private 5G Core (AP5GC) uses when running on supported Azure Stack Edge (ASE) devices.
1414

15-
| VM detail | Flavor name | vCPUs | Memory (GB) | Disk size (GB) | VM function |
15+
| VM detail | Flavor name | vCPUs | Memory (GiB) | Disk size (GB) | VM function |
1616
|---|---|---|---|---|---|
17-
| Management Control Plane VM | Standard_F4s_v1 | 4 | 4 | Ephemeral - 80 | Management Control Plane to create Kubernetes clusters |
18-
| AP5GC Cluster Control Plane VM | Standard_F4s_v1 | 4 | 4 | Ephemeral - 128 | Control Plane of the Kubernetes cluster used for AP5GC |
19-
| AP5GC Cluster Node VM | Standard_F16s_HPN | 16 | 32 | Ephemeral - 128 </br> Persistent - 102 GB | AP5GC workload node |
20-
| Control plane upgrade reserve | | 4 | 4 | 0 | Used by ASE during upgrade of the control plane VM |
21-
| **Total requirements** | | **28** | **44** | **Ephemeral - 336** </br> **Persistent - 102** </br> **Total - 438** | |
17+
| Management Control Plane VM | Standard_F4s_v1 | 4 | 4 | Ephemeral - 80 | Management Control Plane to create Kubernetes clusters |
18+
| AP5GC Cluster Control Plane VM | Standard_F4s_v1 | 4 | 4 | Ephemeral - 128 | Control Plane of the Kubernetes cluster used for AP5GC |
19+
| AP5GC Cluster Node VM | Standard_F16s_HPN | 16 | 32 | Ephemeral - 128 </br> Persistent - 102 GB | AP5GC workload node |
20+
| Control plane upgrade reserve | | 0 (see note) | 4 | 0 | Used by ASE during upgrade of the control plane VM |
21+
| **Total requirements** | | **24** | **44** | **Ephemeral - 336** </br> **Persistent - 102** </br> **Total - 438** | |
2222

23-
## Remaining usable resource on Azure Stack Edge Pro
23+
> [!NOTE]
24+
> An additional four vCPUs are used during ASE upgrade. We do not recommend reserving these additional vCPUs because the ASE control plane software can contend with other workloads.
2425
25-
The following resources are available within ASE after deploying AP5GC. You can use these resources, for example, to deploy additional virtual machines or storage accounts.
26+
## Remaining usable resources
27+
28+
The following table lists the resources available on supported ASE devices after deploying AP5GC. You can use these resources to deploy additional virtual machines or storage accounts, for example.
2629

2730
| Resource | Pro with GPU | Pro 2 - 64G2T | Pro 2 - 128G4T1GPU | Pro 2 - 256G6T2GPU |
2831
|----------|--------------|---------------|--------------------|--------------------|
29-
| vCPUs | 12 | 4 | 4 | 4 |
30-
| Memory | 56 GB | 3 GB | 51 GB | 163 GB |
31-
| Storage | ~3.75 TB | ~280 GB | ~1.1 TB | ~2.0 TB |
32+
| vCPUs | 16 | 8 | 8 | 8 |
33+
| Memory | 52 GiB | 4 GiB | 52 GiB | 180 GiB |
34+
| Storage | ~ 3.75 TB | ~ 280 GB | ~ 1.1 TB | ~ 2.0 TB |
35+
36+
For the full device specifications, see:
37+
38+
- [Technical specifications and compliance for Azure Stack Edge Pro with GPU](/azure/databox-online/azure-stack-edge-gpu-technical-specifications-compliance)
39+
- [Technical specifications and compliance for Azure Stack Edge Pro 2](/azure/databox-online/azure-stack-edge-pro-2-technical-specifications-compliance)

0 commit comments

Comments
 (0)