Skip to content

Commit a1f63c4

Browse files
Merge pull request #300698 from paulopiyo777/paulopiyo777-space-optimized-skus
[operator-nexus/4.5] Update public documentation with new storage-optimized SKUs
2 parents 3aab26c + 8d07c4e commit a1f63c4

File tree

2 files changed

+13
-2
lines changed

2 files changed

+13
-2
lines changed

articles/operator-nexus/concepts-nexus-kubernetes-placement.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ each NKS VM launches.
2828
Nexus first identifies the set of potential bare metal servers that meet all of
2929
the resource requirements of the NKS VM SKU. For example, if the user
3030
specified an `NC_G48_224_v1` VM SKU for their agent pool, Nexus collects the
31-
bare metal servers that have available capacity for 48 vCPU, 224Gi of RAM, etc.
31+
bare metal servers that have available capacity for 48 vCPU, 224 GiB of RAM, etc.
3232

3333
Nexus then examines the `AvailabilityZones` field for the Agent Pool or Control
3434
Plane being scheduled. If this field isn't empty, Nexus filters the list of
@@ -79,7 +79,7 @@ The example Operator Nexus environment has these specifications:
7979

8080
* Eight racks of 16 bare metal servers
8181
* Each bare metal server contains two [Non-Uniform Memory Access][numa] (NUMA) cells
82-
* Each NUMA cell provides 48 CPU and 224Gi RAM
82+
* Each NUMA cell provides 48 CPU and 224 GiB RAM
8383

8484
[numa]: https://en.wikipedia.org/wiki/Non-uniform_memory_access
8585

@@ -318,3 +318,7 @@ it is not guaranteed that this will be exactly one-full and one-half NUMA cells.
318318
This means that an `NC_G24_112_v1` may or may not be able to schedule on a machine
319319
running an `NC_E70_336_v1` depending on how the `NC_E70_336_v1` VM is scheduled
320320
across the NUMA-cells.
321+
322+
## Storage-optimized VM SKUs
323+
324+
`NC_L46_224_v1` and `NC_L54_224_v1` are SKUs designed to enhance local storage utilization and scalability by allowing a Nexus Kubernetes node to allocate up to 1.6 TiB of disk space. This is to support workloads that require more than the typical 300 GiB allocated by other SKUs.

articles/operator-nexus/reference-nexus-kubernetes-cluster-sku.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,13 @@ The general purpose and performance optimized VM SKUs can be used for both worke
6464
| NC_E94_448_v1 | 94 | 448 | 300 | 1.7.3, 2.0 |
6565
| NC_E70_336_v1 | 70 | 336 | 300 | 1.7.3, 2.0 |
6666

67+
## Storage optimized VM SKUs
68+
69+
| VM SKU Name | vCPU | Memory (GiB) | Root Disk (GiB) | Compatible Compute SKUs |
70+
|---------------|------|--------------|-----------------|---------------------|
71+
| NC_L54_224_v1 | 54 | 224 | 1638 | 2.0 |
72+
| NC_L46_224_v1 | 46 | 224 | 1638 | 2.0 |
73+
6774
## Next steps
6875

6976
Try these SKUs in the Azure Operator Nexus Kubernetes cluster. For more information, see [Quickstart: Deploy an Azure Operator Nexus Kubernetes cluster](./quickstarts-kubernetes-cluster-deployment-bicep.md).

0 commit comments

Comments
 (0)