Data center fabric of a logistics company
Gullwing Freight’s data center as a spine-leaf fabric: four spines, a leaf pair per row, what one failed leaf takes down, and one rack slot by slot.
Views in this map
- 1 FabricFour spines, a leaf pair per row: every leaf is two hops from every other leaf.
- 2 Leaf C1 failsLeaf C1 dies. C2 carries row C, but five single-homed servers lose their only link.
- 3 Row CFour racks, each cabled to both leaves. Dashed servers have only one link.
- 4 Rack C03Rack C03 slot by slot: 20 of 42U used, two power feeds, one patch panel to the leaves.
Fabric ‹ › Leaf C1 fails ▸ Row C ▸ Rack C03
Flows to play
- Two servers talk across racksA write from rack A02 to Kafka in rack C03, leaf to spine to leaf. With leaf C1 down, it goes through C2.
- A write lands in two racksKafka copies each write to a broker in another rack, through the leaf. In the Row C view.
- Feed A tripsPower feed A goes out; every server in the rack keeps running on PDU B. In the Rack C03 view.
The model behind it
83 records of 12 types. Every box on the map is one of them, so the filters and the record panel read the same data.
Filters
Row and Hardware generation: pick a value and everything else fades.
See you in the canvas
Unlock your team’s collaborative super powers.