|
| 1 | +# DC-BB Interconnect Study |
| 2 | + |
| 3 | +Assessment of Data Center (DC) to Backbone (BB) interconnect topologies across two sites. |
| 4 | + |
| 5 | +## Network Model |
| 6 | + |
| 7 | +``` |
| 8 | +Site A Site B |
| 9 | +┌─────────────────┐ ┌─────────────────┐ |
| 10 | +│ Data Center │ │ Data Center │ |
| 11 | +│ (rows x cols) │ │ (rows x cols) │ |
| 12 | +└────────┬────────┘ └────────┬────────┘ |
| 13 | + │ │ |
| 14 | + ▼ ▼ |
| 15 | +┌─────────────────┐ ┌─────────────────┐ |
| 16 | +│ Backbone │◄──────────────►│ Backbone │ |
| 17 | +│ (planes x cols) │ Inter-site │ (planes x cols) │ |
| 18 | +└─────────────────┘ └─────────────────┘ |
| 19 | +``` |
| 20 | + |
| 21 | +## Assumptions |
| 22 | + |
| 23 | +### Data Center (DC) Layer |
| 24 | + |
| 25 | +- Modeled as a matrix with rows and columns |
| 26 | +- Rows represent independent rows in the DC spine layer |
| 27 | +- Columns represent devices per row |
| 28 | +- Traffic originates/terminates at or behind DC layer nodes |
| 29 | +- Supported shapes: 16x36, 24x64 |
| 30 | + |
| 31 | +### Backbone (BB) Layer |
| 32 | + |
| 33 | +- Modeled as a matrix with planes and columns (nodes per plane) |
| 34 | +- Planes are independent within a site (no cross-plane connectivity intra-site) |
| 35 | +- BB attaches to DC spine layer |
| 36 | +- Supported shapes: 64x4, 32x4, 16x4, 8x4, 16x1, 16x2 |
| 37 | + |
| 38 | +### Inter-site Connectivity |
| 39 | + |
| 40 | +- Only BB layers are interconnected between sites |
| 41 | +- Connectivity is plane-to-plane (plane N at Site A connects to plane N at Site B) |
| 42 | +- Planes within a site are NOT connected to each other |
| 43 | + |
| 44 | +### Asymmetry Support |
| 45 | + |
| 46 | +- DC shapes can differ between sites |
| 47 | +- BB shapes can differ between sites (both plane count and nodes-per-plane) |
| 48 | +- When BB plane counts differ, only common planes (min of both) have inter-site links |
| 49 | + |
| 50 | +## Topology Naming |
| 51 | + |
| 52 | +Format: `dc{R}x{C}_bb{P}x{N}_bb{P}x{N}_dc{R}x{C}_{pattern}` |
| 53 | + |
| 54 | +- DC-A: Site A Data Center (rows x cols) |
| 55 | +- BB-A: Site A Backbone (planes x nodes) |
| 56 | +- BB-B: Site B Backbone (planes x nodes) |
| 57 | +- DC-B: Site B Data Center (rows x cols) |
| 58 | +- pattern: Interconnect pattern (one_to_one, full_mesh, etc.) |
| 59 | + |
| 60 | +Examples: |
| 61 | + |
| 62 | +- `dc16x36_bb32x4_bb32x4_dc16x36_one_to_one` - symmetric 32-plane BB |
| 63 | +- `dc16x36_bb16x4_bb16x4_dc16x36_full_mesh` - symmetric 16-plane BB |
| 64 | +- `dc16x36_bb32x4_bb16x4_dc24x64_one_to_one` - asymmetric configuration |
| 65 | + |
| 66 | +## Usage |
| 67 | + |
| 68 | +```bash |
| 69 | +# List available topologies |
| 70 | +python3 run.py --list |
| 71 | + |
| 72 | +# Run specific topology with seeds |
| 73 | +python3 run.py dc16x36_bb32x4_bb32x4_dc16x36_one_to_one --seeds 42 43 44 |
| 74 | + |
| 75 | +# Run with seed range |
| 76 | +python3 run.py dc16x36_bb32x4_bb32x4_dc16x36_one_to_one --seeds 42:50 |
| 77 | + |
| 78 | +# Force re-run (ignore cache) |
| 79 | +python3 run.py dc16x36_bb32x4_bb32x4_dc16x36_one_to_one --force |
| 80 | + |
| 81 | +# Compute metrics only (from existing results) |
| 82 | +python3 run.py --metrics |
| 83 | + |
| 84 | +# Dry run (generate merged scenario without running) |
| 85 | +python3 run.py dc16x36_bb32x4_bb32x4_dc16x36_one_to_one --dry-run |
| 86 | +``` |
| 87 | + |
| 88 | +## Output |
| 89 | + |
| 90 | +Results saved to `results/{topology}/`: |
| 91 | + |
| 92 | +- `summary.json` - aggregated failure analysis metrics |
| 93 | +- `{topology}__seed{N}/` - per-seed raw ngraph results |
| 94 | + |
| 95 | +## Interconnect Patterns |
| 96 | + |
| 97 | +- **one_to_one**: Each DC row connects to a fixed subset of BB planes |
| 98 | +- **full_mesh**: Every DC row connects to all BB planes |
| 99 | +- **balanced_sparse**: DC rows connect to subset of planes with rotation |
| 100 | +- **balanced_dense**: Higher connectivity with skip pattern |
0 commit comments