ADD: Application and Data-Driven Controller Design Yikai Lin *, Yuru Shao, Xiao Zhu, Junpeng Guo, Kira Barton, Z. Morley Mao *[email protected] | [email protected] 3. System Design 1. Motivation and Problems 2. Approach Decouple application logic from network data retrieval and storage 4. Use case – Anomaly Detection • With ADD, an anomaly detection app can easily utilize data from different sources. • Application logic and data retrieval are completely decoupled. • Our prototype anomaly detection app based on ADD can detect anomalies 30+ seconds faster than a comparable commercial program (more details in the paper). How can we enable general and efficient data access for SDN applications? • Consolidates requests to eliminate redundant retrieval • (Logically) centralizes data storage to eliminate redundant storage • Uniform encoding of data across different sources to allow generic interface designs However, collecting data with existing controllers means: 1. Apps independently & continuously interact w/ devices. 2. Apps maintain their own copies of collected data. 3. App logic is tightly coupled w/ specific devices/protocols. => redundant data retrieval & storage => unscalable • Network composition is becoming more heterogeneous. • SDN apps need fine-grained visibility to provide service customization and support network slicing. Data Flow of a Legacy SDN Controller Data Flow of an ADD Controller Implications: 1. Applications focus on “what data are needed” and “what to do with them”. 2. Uniform programming model: apps subscribe to both events and data. Packet metadata Traffic metadata Firewall Legacy Controller Anomaly Detection DPI Packet metadata Traffic metadata Firewall ADD Controller Anomaly Detection DPI Programming Model w/ Legacy Controller Programming Model w/ ADD Controller • Applications register their data interests (what to collect) with ADD. • ADD collects and stores data automatically. • Applications subscribe to data/events and react as programmed. Application Plane ADD Controller Generic Northbound Interface Generic Southbound Interface Anomaly Detection Routing … Data Plane Application Plane Legacy Controller Northbound Interface Southbound Interface Anomaly Detection Routing … Data Plane Router Switch … Router Switch … Request Consolidation + (Logically) Centralized Storage + Uniform Data Representation Message Forwarding Redundant Storage Redundant Retrieval

ADD: Application and Data-Driven Controller Designweb.eecs.umich.edu/~yurushao/pubs/SOSR2019_ADD_poster.pdf · ADD: Application and Data-Driven Controller Design Yikai Lin*, Yuru

Download PDF Report

Upload
lamque
View
217
Download
0

Embed Size (px)

Citation preview

Page 1: ADD: Application and Data-Driven Controller Designweb.eecs.umich.edu/~yurushao/pubs/SOSR2019_ADD_poster.pdf · ADD: Application and Data-Driven Controller Design Yikai Lin*, Yuru

ADD: Application and Data-Driven Controller DesignYikai Lin*, Yuru Shao, Xiao Zhu, Junpeng Guo, Kira Barton, Z. Morley Mao

*[email protected] | [email protected]

3. System Design1. Motivation and Problems

2. Approach

Decouple application logic from network data retrieval and storage

4. Use case – Anomaly Detection

• With ADD, an anomaly detection app can easily utilize data from different sources.• Application logic and data retrieval are completely decoupled.• Our prototype anomaly detection app based on ADD can detect anomalies 30+ seconds

faster than a comparable commercial program (more details in the paper).

How can we enable general and efficient data access for SDN applications?

• Consolidates requests to eliminate redundant retrieval• (Logically) centralizes data storage to eliminate

redundant storage• Uniform encoding of data across different sources to

allow generic interface designs

However, collecting data with existing controllers means:1. Apps independently & continuously interact w/ devices.2. Apps maintain their own copies of collected data.3. App logic is tightly coupled w/ specific devices/protocols.=> redundant data retrieval & storage => unscalable

• Network composition is becoming more heterogeneous.• SDN apps need fine-grained visibility to provide service

customization and support network slicing.

Data Flow of a Legacy SDN Controller Data Flow of an ADD Controller

Implications: 1. Applications focus on “what data are needed”

and “what to do with them”.2. Uniform programming model: apps subscribe

to both events and data.

Packet metadata

Traffic metadata

Firewall

LegacyController

Anomaly DetectionDPI

Packet metadata

Traffic metadata

Firewall

ADDController

Anomaly DetectionDPI

Programming Model w/ Legacy Controller Programming Model w/ ADD Controller

• Applications register their data interests (what to collect) with ADD.• ADD collects and stores data automatically.• Applications subscribe to data/events and react as programmed.

ApplicationPlane

ADDController

Generic Northbound Interface

Generic Southbound Interface

Anomaly Detection Routing …

Data Plane

ApplicationPlane

LegacyController

Northbound Interface

Southbound Interface

Anomaly Detection Routing …

Data Plane Router Switch … Router Switch …