Reference architecture

Reference architecture: two-node switchless Azure Local

The smallest highly available Azure Local design. Two machines, storage links cabled directly between them, a switch pair for everything else and a witness outside the site.

What this architecture covers

Design decisions

  • Storage intent on direct links between the two machines, no storage switches
  • Management and compute intent on a redundant switch pair
  • A witness outside the site so one machine can fail safely
  • Two-way mirror storage, sized for half of raw capacity
  • Out-of-band management on its own isolated network
What you receive
  • The architecture adapted to your site in a design document
  • A cabling diagram and port map
  • A failure test plan

Billed at $150.00 per hour. Ask Keith for an estimate.

Diagram

The layers, top to bottom.

AzureAzure ArcKey VaultWitnessMonitorWorkloadsVirtual machinesAKSAVD hostsClusterMachine 1Machine 2StorageDirect links, RDMATwo-way mirrorNetworkSwitch ASwitch BFirewallManagementOut-of-band controllers
Field notes

What we check first.

Each storage link is its own subnet

Direct links are point to point. We address and test them individually.

Witness reachability

The witness must be reachable by both machines over a path that does not depend on either one.

Maintenance means no redundancy

With one machine out for updates, the other is a single point of failure. We schedule updates with that in mind.

How an engagement runs

Four steps, written down.

I
Scope

A call with Keith

You describe the goal, the estate and the deadline. Keith turns it into a written scope with an hour estimate at the hourly rate.

II
Design

A written design by Gus

Gus reviews the environment and gives you a written design with each decision and its reason.

III
Build

Hands-on implementation

Gus implements in your tenant and your racks, remotely or on site, with every change logged as it is made.

IV
Hand over

Documents and a named contact

You receive the as-built record and the runbooks. Keith stays on as your account and project manager.

Questions

Asked before every engagement.

When is this the wrong design?

When you expect to grow past two machines, or need to survive two simultaneous failures. A switched design with three or more machines fits better.

Does it support GPUs and AKS?

Yes, within the capacity of two machines and the supported GPU configurations.

What does the consulting cost?

Consulting is billed at $150.00 per hour. Keith sends a written hour estimate after the scoping call, and work starts when you approve it.

Rate and contacts

One rate. Two people.

Consulting is billed at $150.00 per hour. Keith runs sales, project management and your account. Gus does the architecture, the design and the implementation.

Hourly rate
$150.00

per consulting hour, for every consulting service

Sales, project management and account management

Keith

keith@apexvanguard.ai
Architecture, design and implementation

Gus

gus@gusitllc.com

Independent practice, not affiliated with Microsoft. Azure Local consulting is part of the infrastructure consulting practice of Gus IT LLC, an independent firm. It is not affiliated with, endorsed by or sponsored by Microsoft Corporation, Dell Technologies, Fortinet or any other vendor named on this site. Microsoft, Azure, Azure Local, Azure Stack HCI, Azure Arc, AKS, Azure Virtual Desktop, Hyper-V and Windows Server are trademarks of Microsoft Corporation. Dell, PowerEdge, PowerSwitch and iDRAC are trademarks of Dell Inc. Microsoft Entra, Active Directory, SQL Server, FSLogix and BitLocker are also trademarks of Microsoft Corporation. Fortinet and FortiGate are trademarks of Fortinet, Inc. VMware and vSphere are trademarks of Broadcom Inc. Kubernetes is a registered trademark of The Linux Foundation. PostgreSQL is a trademark of the PostgreSQL Community Association of Canada. Linux is the registered trademark of Linus Torvalds. All other marks belong to their respective owners and are used for description only. Product capabilities follow each vendor's documentation and change between releases; we confirm the current state during scoping.