1. OASIS Deployment: VideoCollective
George Porter
Mel Tsai
Li Yin
Overview
RouterVM
VideoCollective
RouterVM is the core of our PNE design—a general platform for deploying edge services
Although the VM structure is well-defined, it does not depend on a particular hardware architecture, making it amenable to software, NP-based, and asic-based realizations
A virtual line card is instantiated for every port required by the application
A virtual backplane shuttles packets between line cards
A control CPU handles routing protocols and management tasks
When required, compute engines perform complex, high-latency processing on flows
Blue components are “standard” and are instantiated by default. Yellow components are added and configured on a per-application basis
Filters are the key to the flexibility of RouterVM
PNE
Video server
Disk
Web
Flow
load-balancing
NAT
Apple’s Open-source
Video streaming server
SAN Load-balancing,
vSAN, mirroring
EECS
Net
Programmable Network Elements (PNEs) provide a general platform for deploying edge services
To test their versatility and performance characteristics, we are deploying them in a real-world environment
VideoCollective is a multimedia delivery service housed in OASIS’s experimental testbed
Users will be able to view and share content
Video streaming is a simple, well-understood application that has strict performance requirements
Our PNE design must support web/HTTP, video (MPEG-4), audio (MP3), and SAN (iSCSI) traffic efficiently
Phase 1: Video Delivery
Phase 2: Shared Now Playing List
Phase 2: In-network Revision Control
Upload and share files with groups
Group-based views into video files via vSANs
PNEs map overwrites of files to fresh portions of disk
Allows users to “dial” to any time period to see content as it existed at that time (similar to CVS)
View “Now Playing” list of video files (MPEG-4)
Stream content to desktop in Soda Hall
Drives PNE functionality:
Drives Storage functionality:
Drives PNE and Storage functionality:
Network Address Translation (NAT)
Per-flow load balancing over servers
SAN Storage virtualization (content management, performance, and reliability)
Tuning SAN performance
vSAN enhancement to SAN (each group “sees” their own private SAN via packet rewriting and indirection)
In-network SAN target selection
State requirements increase as a function of file overwrites
The PNE’s virtualization function must become paramaterizable
Drives a tighter coupling between in-network processing elements and offboard servers