[Fabric] Fabric Simulator Master Issue

[aliuTT]

Master issue for creating infra that simulates inter/intra mesh routing and the control plane traffic management needed for rerouting. To help with debugging, we should have serialization for the following:

• Physical ethernet connections: cluster_desc.yaml (already have this)
• Routing Tables
• Routing Buffers and VCs

Control Plane:

• Serialize routing tables
• Generate intermesh and intramesh routing tables, based on cluster_desc.yaml
• Host logic to detect link failures, we can simulate this by removing connections from cluster_desc.yaml
• Update routing table when links fail, may need it for rebalancing traffic

Routing Buffers and VCs:

• Serialize routing buffer, VCs
• Simulate packet traffic and test for deadlock situations

Visualization:

• Visualization for live links, based on generated cluster_desc.yaml
• Visualization for intermesh and intramesh routing tables
• Visualization for Routing Buffers and VCs

[davorchap]

• separate the sim into: 1) data-plane , which simulates our meshes and 2) control plane, which is the same if we're in sim or real HW
• for a full data center scale with lots of meshes, we need a way to for ground truth connectivity described (intra- / inter- mesh) -- including all of redundancy connections, the spec should allow to specify distinction between preferred connection and redundancy connection
• serialization should allow us capturing traffic from the sim and downloading to HW and "resuming" in HW, and vice verse, capturing in HW and resuming in sim
• sim of the data-plane should allow seamless external disruptor hooks -- so that we can disrupt the data-plane sim with "pulling of the cables" , and sim pausing , control plane re-rerouting and updating the data-plane