Network emulation is a technique for testing the performance of real applications and validating the correctness of configurations over a virtual network. Different from simulators, a network emulator mirrors the network which connects end-systems, not the end-systems themselves. A network emulator example is Crystalnet, which is published in SOSP 2017.
In this project, we will build a network emulator to emulate a data center network. Production data center networks typically use Clos topology and BGP/ECMP for routing. We will use public image of SONiC, an open source cross-platform switch OS. On the top of the emulated data center network, we will develop tools to automatically generate network configurations, and diagnosis tools to debug network faults, e.g., Pingmesh.
Roles in this project include datacenter network emulator, network configuration generator, and network diagnosis tool(s).
- The datacenter network emulator emulates a data center network. Specifically, it runs Fat Tree topology which is a special case of Clos topology aand uses SONiC image for switch OS.
- Network configuration generator automatically generates network configurations. In this project, it will generate BGP/ECMP routing rules.
- Network diagnosis tools are to debug network faults. We will use Pingmesh to test the connectivity of all pairs of end-hosts to diagnose the correctness of BGP protocol configuration.
The Scope places a boundary around the solution by detailing the range of features and functions of the project. This section helps to clarify the solution scope and can explicitly state what will not be delivered as well.
It should be specific enough that you can determine that e.g. feature A is in-scope, while feature B is out-of-scope.
This section provides a high-level outline of the solution.
Global Architectural Structure Of the Project:
This section provides a high-level architecture or a conceptual diagram showing the scope of the solution. If wireframes or visuals have already been done, this section could also be used to show how the intended solution will look. This section also provides a walkthrough explanation of the architectural structure.
Design Implications and Discussion:
This section discusses the implications and reasons of the design decisions made during the global architecture design.
This section discusses the minimum acceptance criteria at the end of the project and stretch goals.
Release planning section describes how the project will deliver incremental sets of features and functions in a series of releases to completion. Identification of user stories associated with iterations that will ease/guide sprint planning sessions is encouraged. Higher level details for the first iteration is expected.
Remember that you can always add features at the end of the semester, but you can't go back in time and gain back time you spent on features that you couldn't complete.
For more help on markdown, see https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent