โ ๏ธ 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.20.67 |
Calculate instance 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.
Workload Scenarios
Add workloads to calculate your Azure Local instance requirements.
START HERE
△
Start by adding a workload
Click one of the workload buttons above to size your Azure Local instance
Configure your instance topology and storage settings.
Tip: For business or mission-critical workloads, it is recommended to implement two separate Azure Local instances, to enable workload HA/DR capabilities between two locations, or consider a Rack-Aware Cluster deployment 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 instances 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
Hardware Requirements Summary
Continue to add additional workloads, if required. Once complete, open the Designer wizard pre-configured with this instance 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.
Power calculations, verbose information and assumptions
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.
💡 Tip: Left-click and hold to rotate ยท Scroll to zoom ยท Right-click and hold to move
Server Node Edge Appliance ToR Switch Edge Switch BMC Switch Core Router / Firewall Mgmt/Compute SMB Trunk LAG FC Switch SAN Appliance /
Interactive 3D preview of the estimated rack layout. Each server node occupies 2U, ToR switches occupy 1U each. The cables from each node to the ToR switches are not shown. Rack-aware deployments show balanced distribution of nodes across two cabinets, in real deployments these can be in separate rooms or datacenter locations. โ ๏ธ This is an approximate representation only, contact your preferred hardware OEM partner for detailed physical space requirements for their Azure Local solutions.
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.
✓ Valid FQDN format
๐ Import Configuration
๐
Import a previously exported ODIN Sizer configuration
Select a .json file that was exported using the Export JSON button. This will restore all workloads, hardware settings, and MANUAL overrides.
โ๏ธ
Import hardware specs from an existing Azure Local machine
Navigate to any machine (node) in your instance in the Azure Portal → JSON View → Copy the full JSON and paste it below. The exact CPU model, core count, and memory will be extracted.
๐Privacy: All processing is performed entirely in your browser. No instance configuration data is stored, transmitted, or sent to any external service. Sanitize any sensitive information before pasting.
๐ง
Configuration Imported
๐พ
Configure Storage
Set the disk count, disk size, and storage type to match your cluster's physical disks.
๐ฆ
Add Workloads
Add your VMs, AKS Arc clusters, and AVD sessions to see how the existing hardware handles them.
๐
MANUAL Overrides
Imported values are locked as MANUAL โ auto-scaling won't override them.
๐
Review Capacity
Check utilization bars and sizing notes to see if your hardware fits the workloads.