⚠️ 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.22.65 |

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

💻 VMs ⎈ AKS Arc 🖥 AVD 🧠 Foundry Local 🔎 Edge RAG 🎬 AI Video Indexer 💻 GitHub Enterprise Local
View an example 3D visualization of the hardware below

Recommended Instance Configuration

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.
Tip: Minimum N+1 capacity must be reserved for Compute and Memory when applying updates (ability to drain a machine). Single Machine instances will always incur workload downtime during updates.

Physical Machine(s) - Example Hardware Configuration

Define the physical hardware specifications for each machine.

Info: Sizer hardware scaling weighting logic

CPU Configuration

Memory Configuration

GPU Configuration

Advanced Settings

Storage Configuration

Disk Configuration (Capacity)

S2D Repair Reservation

Hardware Utilization Information

Number of workloads: 0
Compute (vCPUs) required: 0
Memory required: 0 GB
Storage (usable) required: 0 TB

Physical Machines Hardware Requirements:

- includes N+1 machines (for HA and update resiliency), compute uses a 4:1 vCPU overcommit ratio

How is this calculated?

Physical Cores 0
Memory 0 GB
Raw Storage 0 TB
Usable Storage 0 TB

Percentage capacity used/available for defined workloads:

Azure Local hyperconverged instance size 0 / 16
(includes N+1 machine count, for servicing and redundancy)
Compute (vCPUs) - Consumed 0%
0 / 0 vCPUs
Memory - Consumed 0%
0 / 0 GB
Usable Storage - Consumed 0%
0 / 0 TB

Estimated Power, Heat & Rack Space per Instance

Per-Machine Power (est.) —
Total Instance Power (est.) —
Annual Energy (est.) —
ⓘ Input: —
Total BTU/hr (est.) —
Rack Units (est.) —
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.

Azure Local Instance - Sizing Notes

  • Add workloads to see sizing recommendations