⚠️ Disclaimer: This tool is provided as-is, without Microsoft support. Odin is an experimental project that accelerates skills and knowledge ramp up for Azure Local, and helps IT architects validate cluster design configurations.
ODIN Sizer for Azure Local
Version 0.18.01 |
Calculate cluster hardware requirements based on your workload scenarios and their resiliency and capacity requirements. This tool provides example hardware configurations only. Please consult with your preferred hardware OEM partner for detailed guidance and recommendations on their Azure Local solution offerings.
Visitors:—
Designs Generated:—
ARM Deployments:—
Sizes Calculated:—
Workload Scenario
Add workloads to calculate your Azure Local cluster requirements.
No workloads added yet
Click a workload type above to get started
Recommended Cluster Configuration
Configure your cluster topology and storage settings.
Tip: For business or mission-critical workloads, it is recommended to implement two separate Azure Local clusters, to enable workload HA/DR capabilities between two locations, or consider a Rack-Aware Cluster configuration type.
We highly recommend using Three-way Mirror for the highest level of resiliency and performance.
Tip: Minimum N+1 capacity must be reserved for Compute and Memory when applying updates (ability to drain a node). Single Node clusters will always incur workload downtime during updates.
Physical Node(s) - Example Hardware Configuration
Define the physical hardware specifications for each node.
CPU Configuration
Memory Configuration
GPU Configuration
⚠️ Selected GPU count exceeds the maximum supported per node for this GPU model. The count has been capped.
Advanced Settings
Storage Configuration
All-Flash configuration is recommended for increased performance and resiliency.
Disk Configuration (Capacity)
S2D Repair Reservation
Cache Disks
Cache disk type: NVMe
Capacity Disks
Capacity disk type: SSD
S2D Repair Reservation
Requirements Summary
Continue to add additional workloads, if required. Once complete, open the Designer wizard pre-configured with this cluster and hardware sizer settings.
Total vCPUs0
Total Memory0 GB
Total Storage0 TB
Total Workloads0
Workload Per-Node Requirements (with N+1)
Physical Cores0
Memory0 GB
Raw Storage0 TB
Usable Storage0 TB
Capacity Usage for Workload
Azure Local hyperconverged instance size0 / 16
(includes N+1 node count, for servicing and redundancy)
Compute (vCPUs) - Consumed0%
0 / 0 vCPUs
Memory - Consumed0%
0 / 0 GB
Usable Storage - Consumed0%
0 / 0 TB
GPU (Physical Units) - Consumed0%
0 / 0 GPUs (across N−1 effective nodes)
🚫One or more resources (Compute, Memory, Storage, or GPU) are at or above 90% utilization. This is not a recommended configuration — increase per-node hardware specs, add more nodes, or reduce workloads before proceeding to the Designer.
⚠️
🚫Storage configuration exceeds Azure Local supported limits. Export is blocked until the configuration is corrected.
Estimates based on component TDP ratings. Actual power varies by workload and OEM hardware design. Consult your preferred OEM hardware partner for accurate power and rack planning.
Azure Local Instance - Sizing Notes
Add workloads to see sizing recommendations
Add Workload
Select Azure Region
Choose the Azure region for your Azure Local deployment. This will be set in the Designer wizard.
Autonomous Cloud Endpoint
Enter the Autonomous Cloud FQDN for the ALDO management cluster. This endpoint is used by disconnected operations for the local Azure control plane.