Dynamic Analytics Extended to all layers Utilizing P4

Transcription

1 Dynamic Analytics Extended to all layers Utilizing P4 Tom Tofigh, AT&T Nic VIljoen, Netronome

2 This Talk is about Why P4 should be extended to other layers Interoperability - Utilizing common framework allows the development of a true networking language that is easy to learn Eliminates vendor dependence at all levels of the network, switches, Routers, NICs CPU Open Interfaces - Following the P4 model allows the use of simple open interfaces such as custom actions-democratization of the data plane and open micro services The P4/C extensions model should be very simple, and could exist across data plane while it does not affect base data plane functionality

3 Autonomous Run Time Control and Reconfigure Observability blocks 1- Programmable vprobe 2- Real time Instrumentation of probes 3- SDN based Actuation & Control 4- Real Time Feed back Loop Measure Actuate 2 Analyze

4 Why P4 should pay more Attention to Real time Observability Internal TE Apps Root Cause Analytics Apps Observability Abstraction Resource state dissemination/collection Ability to collect state of resources/elements Ability to observe probes adaptively and on Demand Programming abstraction Ability to program traffic forwarding rules/policies Ability to program the Probes Control blocks SDN On Demand Observability Request Framework Higher Level P4 Portal Abstraction North-Bound APIs Program the Data Plane Forwading/ Observability/Utilization/Behaviors Extended Abstraction: Topology, Nodes, Ports, Links + Deep Observability ( VPNs, QOE, Services, Objects, Call Drops) Configuration abstraction Ability to configure the resources bases on policies Ability to configure the appropriate Probes for real time needs Observability Abstraction Open-Flow Ext. Programing Data Point Collection Triggers Forwarding Plane, Network Functions, Dynamic Probes & Sensors, Compliable Analytics ( Switches, Routers, NICs, SOCs, NE, NFVs) P4 Compilation & Configuration Abstraction Date Path Infrastructures

5 Data Plane Analytics / Monitoring for Network s Today s Monitoring platforms are mostly based on switches and compute nodes (CPU)-limited processing, processing power (CPU) INT Network Switch Switch: INT, NAM etc Compute: DPI, TCPDUMP Emerging Open Platforms (disaggregated, sliced ) effectively requires deep, broad, interconnected monitoring Require real time & closed feedback loop with Applications in Controls Shallow Packet Inspection DPI Flows Flow SmartNIC CPU Machine Learning (future) Packet

6 Example; Extending P4 to SmartNIC to support Deeper Observability Next Generation Mobile Edge Networks will be both disaggregated and sliced CPU and NIC are only points able to monitor all flows CPU compute cycles are stretched SmartNIC could provide significant spare computational cycles and provide adjunct HW speed to the rest of the network functions Extending P4 to (L0-L7) could Drive unified customizable observability & Vendor Independence Could enable the service providers with real time feedback loops with controllers

7 Disaggregation and Slicing Extending P4 to other Layers Rack Based Middleboxes COTS Server Based Whitebox-with service based slicing EPC TOR MME SGW Inter VM traffic highly significant vepc vpgw vsgw vmme PGW SmartNIC

8 Observability in Real Time and On Demand Static Observability method doesn t work Difficult to predict all probe & measurement tasks in advance at design time Pre-allocate resources for all potential tasks in data path is prohibitively expensive Data path full reconfiguration for new task is too slow and can cause service interrupt Dynamic incremental reconfigurations are needed moving towards 5G Networks Anytime, anywhere, any action with dynamic resource allocation Hitless data path modification Allow multiple parallel tasks App App App SDN Controller (e.g., ONOS) Runtime (control) Config. (e.g. P4) Runtime (control) Config. (e.g. P4) Runtime (control & reconfig.) Common Probe Block Fixed function device Programmable device Dynamic Programmable Device Convention SDN P4 mode P4/C mode

9 Common Probe Block (CPB) - Conceptual CPB RX Ports Probe Behavior Type (Code) CPB TX Ports Probes (n) Trigger (n) Correlate (n) Dynamic Probe Instruction Set Compiler What you want your Probe to Collect, Trigger, and Correlate Probe Match Variables Block Action Timers Block Service Chain setting. Probe Action Variables

10 Higher Level P4 Programming Abstraction for Deep Observability P4 Control P4 programmable Blocks / Primitives Match Compute Action Parser Parser Profiles Profiles Classification Classification Methods DPIs ML-Algorithm ML-Algorithm Active Test Agents e Test A Collection Usage & Methods Action Methods Tag & Cookies Tags Insertions & Cookie Insertions TE TE Functions Functions Synchronized Synchronized Delivery Delivery Actions Methods

11 Final Remarks P4 can play a key role for deep observability at all layers of network stacks QoE Flow jitter, latency measurement Packet drop rate Root Cause Analysis Dynamic analytics dynamic P4 Models Security DDoS detection Deep packet inspection Stateful flow monitoring present compile analyze disseminate Customer Care Optimization Custom Observability Flow tracing Root cause analysis Load estimation Traffic matrix calculation Elephant flow identification collect Open Networks configure

12 Dynamic Analytics in SmartNICs Utilizing P4-Implementation Monitoring Network s

13 The SmartNIC Fully Programmable Allows for total flexibility in the Dataplane-P4 for flexible data plane elements or custom tagging, probes for monitoring and OVS (or vrouter) as well. All of this can be done through the use of a many threaded many core architecture that allows effective partition Why P4 P4 is incredibly flexible and allows innovation in the data plane- SmartNICs and switches can communicate in a distributed fashion A unifying language by which network elements can interact is very powerful Combining this with custom blocks allows for innovation to be harnessed vprobe Compute OVS/ vrouter SmartNIC P4

14 The Netronome Approach-500+ Threads

15 Use Case: Classifying and Monitoring Network s Isolating s No longer can one simply isolate a problem to a specific box -There are multiple VNFs within one COTS server Therefore it is essential to be able to monitor by VNF and by slice Flexible/Dynamic Monitoring Different s require different monitoring at different locations in the network Being able to dynamically change how different flows/slices are monitored will allow a significant improvement in the granularity of monitoring Predictive Reaction: Improved Monitoring may allow networks to react to problems before they are readily apparent Aim for general reactive loop of <12s (for latency sensitive slices such as mission critical IoT)

16 Challenges in Monitoring Network s Demo Setup Compute Node 1 Tag Packets According to 10Gbps Link Route According to 1 Compute Node 2 SmartNIC SmartNIC 2 3 Highly Aggregated Data Monitor in different ways according to slice and traffic 3 vprobe Dynamic change in flow rules vprobe Key: VNF

17 Final Remarks SmartNICs are not a replacement for other types of monitoring/p4 data plane elements Rather, they compliment and target other types of monitoring and applications This is an example of the power of a fully programmable SmartNIC in the data plane allowing for flexible adaptation to new concepts