Skip to content

Added article on multi site designs in metal-stack - #328

Draft
Sven-Ric wants to merge 5 commits into
mainfrom
doc/multi-site
Draft

Added article on multi site designs in metal-stack#328
Sven-Ric wants to merge 5 commits into
mainfrom
doc/multi-site

Conversation

@Sven-Ric

Copy link
Copy Markdown
Contributor

Description

WIP article on multi site architectures in metal-stack.

TODO

  • technical details
  • add diagrams

Used AI-Tools ✨

Research supported by fable 5

@metal-robot metal-robot Bot added the area: documentation Affects the documentation area. label Jul 21, 2026
@netlify

netlify Bot commented Jul 21, 2026

Copy link
Copy Markdown

Deploy Preview for metal-stack-io ready!

Name Link
🔨 Latest commit 3c05490
🔍 Latest deploy log https://app.netlify.com/projects/metal-stack-io/deploys/6a6b1411130e6200089538e4
😎 Deploy Preview https://deploy-preview-328--metal-stack-io.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@mwindower mwindower left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for setting this up! I have first review comments and suggestions.

Comment thread docs/05-Concepts/03-Network/04-supported-network-designs-and-topologies.md Outdated
Comment thread docs/05-Concepts/03-Network/04-supported-network-designs-and-topologies.md Outdated
Comment thread docs/05-Concepts/03-Network/04-supported-network-designs-and-topologies.md Outdated
Comment on lines +31 to +37
This is the default and most common pattern. Each zone hosts its own metal-stack partition, and partitions are fully independent.

No EVPN or VXLAN overlay is stretched between zones. Each partition operates a self-contained CLOS fabric with its own VNI space, BGP underlay, and exit switches. Private networks are allocated within exactly one partition, so a project that spans multiple zones receives a distinct private network per zone. All inter-zone communication is routed at Layer 3 across the exit switches, which exchange routes with external routing domains.

Partitions share no network state. Failure isolation is strict, and even the complete loss of one partition leaves the remaining zones unaffected. In return, cross-zone redundancy must be implemented at the application layer. Stateless services can be announced from multiple zones via anycast addresses, while stateful services require replication or state persistence outside a single zone.

![Independent partitions with one self-contained fabric per zone](multi-site-independent-partitions.svg)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would also mention here that each partition has its own storage system.


The EVPN fabric is stretched across multiple data-center locations, forming a single partition.

A single VXLAN overlay spans all zones, which share one VRF and VNI space. Each zone hosts its own leaf switches, and the zones are interconnected at the spine or exit-switch level. The validated design covers three data centers whose interconnect forms a ring, which for three sites is equivalent to a full mesh. Interconnect topologies for more than three data centers are not defined. All data centers must lie within 20 km of each other, with latency below 1 ms, and all transport links must carry jumbo frames (MTU 9216) for VXLAN encapsulation.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The storage system is here distributed over several locations.


### Design 3 - Zone Aware Setup (Roadmap)

This design targets a middle ground between independent partitions and the metro setup. Multiple independent partitions exist in different locations and EVPN is not stretched between them. Instead, the exit switches interconnect selected VNIs across partition boundaries, for example via EVPN Multi-Site DCI or SRv6. A private network in one partition thereby becomes reachable from another partition without traversing external networks.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add Route-Leaking with a DCI-VRF as third implementation example there.

Sven-Ric and others added 3 commits July 30, 2026 11:05
…opologies.md

Co-authored-by: mwindower <markus.fensterer@gmail.com>
…opologies.md

Co-authored-by: mwindower <markus.fensterer@gmail.com>
…opologies.md

Co-authored-by: mwindower <markus.fensterer@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: documentation Affects the documentation area.

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants