How uccmisl/godashbed works
Project type and purpose
• Project type: A network‐emulation testbed for HTTP Adaptive Streaming (HAS) and VoIP experimentation. It orchestrates Mininet, configures network conditions from trace files, launches HTTP/QUIC servers and clients (goDASH), and collects performance metrics.
• Use case: Researchers run repeatable DASH/VoIP experiments over emulated TCP/QUIC links, varying bandwidth, delay, queue disciplines, and number of clients.
File structure
• Top‐level scripts (goDashBed.py, hypercorn_*.py) implement the orchestration “control plane.”
• caddy‐config/ houses Caddyfile variants for WSGI servers (TCP and QUIC).
• config/configure.json holds runtime settings (URLs, modes).
• tc_*.sh and get_your_movies.sh are helper scripts for traffic shaping and content setup.
• traces/ holds CSV network‐trace inputs.
• urls/ defines Python modules listing MPD URLs for TCP vs. QUIC clients.
README for architectural clues
• Two server modes:
– WSGI Caddy (TCP/QUIC) using Caddyfiles in caddy-config
– ASGI Hypercorn/QuartTrio (TCP/QUIC) via hypercorn_goDASHbed scripts
• Clients: goDASH video clients + D-ITG voice clients, spawned in Mininet hosts.
• Mininet emulates topology, applies tc delay/fifo per trace.
Main components & their interactions
a. Orchestrator (Python scripts goDashBed.py / hypercorn_goDASHbed.py)
• Parses CLI flags, loads configure.json, picks traces and URL modules.
• Spawns Mininet topology, applies traffic‐control (tc_delay.sh, tc_fifo.sh) using trace CSV.
• Launches server processes on one Mininet host:
– Caddy (WSGI) or Hypercorn (ASGI) with appropriate transport (TCP/QUIC).
• Launches goDASH video clients and D-ITG VoIP clients on other Mininet hosts.
• Collects logs/metrics and repeats per numruns.
b. Network Emulator (Mininet)
• Single‐switch or linear topology, with a bottleneck link configured via tc.
• Hosts are logical VMs: one “server” host, multiple “client” hosts.
c. HTTP/QUIC Servers
• Content store at /var/www/html populated via get_your_movies.sh.
• Caddy server configured by caddy-config/Tesbed*/Caddyfilev2* for TLS certs and QUIC.
• Hypercorn/QuartTrio alternative (ASGI).
d. Clients
• Video clients (goDASH engine) fetch adaptive streams from the server using URLs from urls/mpdURL.py or mpdURLquic.py.
• VoIP clients (D-ITG) generate UDP traffic to server or external sink.
e. Configuration & Data
• configure.json drives runtime parameters (bandwidth, delay, URLs, server mode).
• traces/*.csv provide time‐series link capacities.
• urls/*.py list content URLs for client selection.
Architectural patterns & principles
• Orchestrator + worker pattern: single master script delegating tasks to network, server, and client workers.
• Plugin‐like transport abstraction: SERVER_MODE flag picks WSGI vs. ASGI; TM flag picks TCP vs. QUIC.
• Separation of concerns: network shaping, server hosting, client execution, logging are distinct modules.
– Group related files (urls/*.py, caddy-config/*) inside “Configuration” sub-area.
– Call out dependencies: godash (video engine), D-ITG (VoIP), Mininet.
– Annotate iterations: numruns and per-trace loops can be shown as loops on the Orchestrator.