Recommended
Recommended
More Related Content
Similar to Distributed Mininet with Symbiosis
Similar to Distributed Mininet with Symbiosis (20)
Recently uploaded
Recently uploaded (20)
Distributed Mininet with Symbiosis
- 1. Distributed Mininet with Symbiosis Rong Rong, Jason Liu Florida International University, Miami, Florida, USA ICC’17, Paris, France, May 22, 2017 Supported by NSF CNS-1563883, DOD W911NF-13-1-0157, DOE LANL/LDRD, and USF/FC2 SEED
- 2. Outline • Motivation • Symbiotic Network Simulation • Distributed Mininet with Symbiosis • Experiments and Case Studies • Conclusions
- 3. A Quick Look at Network Experiment Methods 3 WINLAB ORBIT • PhysicalTestbeds • Real experiments • Programmable • Multiple users • Relatively small • Limited diversity
- 4. A Quick Look at Network Experiment Methods 4 GTNeTSSSFNet And more … • PhysicalTestbeds • Simulation • Flexible • Scalable • Diverse • Lack credibility • Significant development effort
- 5. A Quick Look at Network Experiment Methods 5 • PhysicalTestbeds • Simulation • Emulation • Real apps or real operations • Flexibility (from virtualization) • Good but still limited in scale • Flexible but limited scenarios ModelNet
- 6. 6 OpenVSwitch Linux namespace Mininet is an emulation testbed for OpenFlow Bob Lantz, Brandon Heller, and Nick McKeown. 2010. A net- work in a laptop: rapid prototyping for software-defined networks. In Proceedings of the 9th ACM Workshop on Hot Topics in
- 7. 7 OpenVSwitch Linux namespace Distributed Mininet (Maxinet Approach) P. Wette, M. Draxler,A. Schwabe, F. Wallaschek, M. Zahraee, and H. Karl, “Maxinet: Distributed emulation of software-defined networks,” in Proceedings of the 2014 IFIP NetworkingConference, 2014, pp. 1–9.
- 8. Capture large-scale network behavior and global traffic conditions Simulation and Emulation 8 Network Simulation • Full-scale network model • Detailed topology and protocols Network Emulation • Real execution environment (operating system, network stack, software tools) • Unmodified applications Represent real application traffic behavior
- 9. Real-time Simulation • Parallel Real-time Immersive network Modeling Environment (PRIME) • Run parllel simulation in real time, interact with real networks • Direct apps testing in large simulated network • PrimoGENI: at-scale hybrid network experimentation on GENI • Hybrid experiments with simulated, emulated, and physical components • Flexible configuration, real-time visualization and steering • May distribute across geographically distributed sites • Problem: tight coupling simulation and emulation is bottleneck 9
- 10. Symbiotic Approach in a Nutshell 10 R2R1 H4 H2 H3 H1 SimulationEmulation H1 H3 R1 R2 H2 H4 R3 R3 emulated flows simulated flows SimulationEmulation effect of simulated flows effect of emulated flows
- 11. Steady-State Queuing Model 11 Assuming M/D/1 Queue Single-link Segment
- 12. Does ItWork? • Well, steady-state does not work! • Closed-form solution for transient effect is rather elusive, even if assuming Poisson arrivals • We invent a “control nob” to dynamically adjust μ* from measurements 12
- 13. Adjust forTransient Effect 13 excess service rate avg pkt delay in emulation avg pkt delay in simulation excess queue length • The adjustment forces emulation to “track” the simulated network conditions
- 14. PreviousValidation Results • Low, medium, heavy traffic conditions • Various proportions of emulated vs. simulated traffic • Mixed arrivals: exponential, constant, real traces 14 10% utilization 50% utilization 90% utilization
- 15. 15 OpenVSwitch Linux namespace Distributed Mininet with Symbiosis Can we keep traffic within the same Mininet instances if we can?
- 16. Distributed Mininet with Symbiosis 16
- 17. Practical Considerations • Simulation Controller receives ”traffic demand“ from emulated hosts (using strace) and reproduces the flows in simulation accordingly (using implemented tcp variants) • Simulation Controller receives periodic queue updates from emulation (using traffic monitor): flow arrival rate, drop probability, queuing delay • Simulation Controller sends traffic control information to emulation, which controls the real flows (using tc) Simulation Controller Mininet Instance Mininet Instance Mininet Instance Mininet Instance Mininet Instance Mininet Instance
- 19. A Case Study: Shrew Attack • Attacker sends bursts of data at a regular interval to an over-committed bottleneck link[1] • When burst intervals synchronize with RTO ofTCP connections sharing the link, they can trigger TCP timeouts and consequently strangle throughput • Difficult to detect since avg. traffic rate of the attack is low 19 [1] A. Kuzmanovic and E. W. Knightly, “Low-rateTCP-targeted denial of service attacks: The shrew vs. the mice and elephants,” SIGCOMM 2003, pp. 75–86. Victim Attacker Common Bottleneck Link
- 20. 20 One “Good” Flow over 10 Mb/s Bottleneck Link
- 22. Summary • Emulation experiment is limited by scale • Mininet has processing and memory limitation • Maxinet can support large experiments, but has limitation on cross- machine throughput • Real-time simulation combines simulation and emulation, but is also limited by the cross-system traffic • Network Symbiosis decouples them and reduces cross-machine communication (remove data traffic and keep control traffic) • Symbiosis has limitations: • Cross-system traffic is not allowed: need to combine with real-time method • Dynamic traffic is not allowed: limited to studying long term traffic 22
- 23. ThankYou!
Editor's Notes
- Some parallelized
- Planetlab has ~1000 nodes, but shared among many users Fixed setup
- Symbiosis infers mutual beneficial relations between two entities Real application testing under large-sale diverse network conditions
- Emulated hosts refer to machines running real systems and real applications Emulated traffic refers to real network traffic, supposedly flowing on the simulated network Real traffic needs to zip through segments, intermixing with simulated traffic