Download presentation
Presentation is loading. Please wait.
1
Tokyo OpenStack® Summit
2
Carrier-grade Solution for Dynamic Service Function Chaining using OpenDaylight
Shlomi Alfasi / Oct 2015
3
Agenda SFC Use Case Subscriber Aware SFC
HPE Carrier Grade SFC - What it takes to make ODL Carrier SDN
4
The term "service function chaining" is used to describe the definition and instantiation of an ordered list of instances of service functions (such as firewalls, load balancers, etc.) , and the subsequent "steering" of traffic flows through those service functions. IETF RFC 7498
5
Service Function Chaining – Use Case
UE Access Services Service Functions Mobile Backhaul Internet PGW Content Filtering Video Optimization Firewall Caching CPE xDSL Internal Appl. Platforms BNG CPE FTTH Header Enrichment TCP Optimization e.g. IMS LI OLT CPE CATV CMTS Based on: IETF – SFC Use Cases in Mobile Networks draft-ietf-sfc-use-case-mobility
6
Traditional Approach Using PNFs
Service Functions Video Optimization TCP Optimization Caching Content Filtering Header Enrichment Lawful Interception PNF A1 PNF B1 PNF C1 PNF D1 PNF E1 PNF F1 PGW Firewall Services implemented using PNFs (Physical Network Functions) Each PNF implements a specific service PNFs are used in-line Each PNF receives all traffic flows (full BW capacity) Each PNF needs to be aware of flows that needs processing Flows not registered for service should be bypasses PNF failure stops the entire traffic Each PNF needs to include High Availability mechanisms – higher cost
7
ODL SFC and NSH Approach
Classifier SFF1 SFF2 (terminateing) SF1 SF2 Outer Transport Payloa d SFC Enca p SFF – forwarder based on NSH headers (may be interconnected by overlay network) SFC-aware Network Functions – NF’s that may utilize and preserve the NSH headers SFC-proxy – Can (re)build NSH headers prior to SFF’s for traffic coming from SFC-unaware domain
8
ODL SFC and NSH Headers NSH headers allow:
Service definition and in-band metadata for arbitrary packets Do not defined transport mechanism Practical challenges NF’s normally do not support NSH (and certainly not their preservation) Can be mitigated by SFC-proxies Standard OpenFlow 1.5 does not support NSH headers Will probably be added in the future
9
SFC Subscriber Aware Approach
10
Subscriber Aware Approach
TCP Optimization Video Optimization Content Filtering Analytics Collection TCP Optimizer #1 Video Optimizer #1 URL Filter #1 Analytics Collector #1 PGW VNF TCP Optimizer #2 Video Optimizer #2 URL Filter #2 Analytics Collector #2 FW VNF TCP Optimizer #3 Video Optimizer #3 URL Filter #3 Analytics Collector #3 Node Node Openstack Networks Controller #1 Controller #3 OpenFlow Switch #1 OpenFlow Switch #3 Network Infrastructure HW Switches HW Switches Purple Subscriber registered to following service: PGW – TCP Opt – Video Opt – URL Filter – FW Red Subscriber registered to following service: PGW – TCP Opt – Content Fitering - FW
11
Subscriber Aware Approach - Data Flow
TCP Optimization Video Optimization Content Filtering TCP Optimizer #2 Video Optimizer #1 URL Filter #2 FW VNF PGW VNF SDN Controllers subscriber Switch #1 subscriber Switch #2 Controllers Openstack Networks ContexNet Node ContexNet Node Tunnel Switch #1 Tunnel Switch #2 Network Infrastructure HW Switches HW Switches 3 Layers of networks: physical networks, Openstack networks, overlay networks Data flow example of a single step, on different servers (need to use HW switch)
12
SFC – Carrier Challenges
Millions of subscribers in every location High number of changes 10’s of thousands per seconds Multi data center Redundancy requirements: VNF, ODL, SW, Network (Control and Datapath) Remote N+1 hot backup High variety of service chains VNF serves multiple chains Physical Network Function need to be included Support VNF without NSH Header
13
Advantages of Subscriber Aware Approach
Providing unprecedented visibility into the network across elements interconnected using the SDN fabric Enabling delivery of personalized services by leveraging functions in the network Increasing security by identifying and isolating flows as needed Dynamically allocating network resources on a per subscriber/user basis Automatically provisioning traffic forwarding path through the service chain Supporting elasticity of functions Providing capabilities, such as load balancing, high availability, and monitoring, eliminate the need for these functions duplicated in each VNF
14
HPE ODL-based Carrier SDN Solution What it takes to make ODL Carrier SDN
15
HPE Carrier SDN Architecture
Orchestration System Management ContexMgmt ContexView Performance Analytics ContexBroker ContexNode ContexNode REST API Distributed Mapping System ContexMap ContexMap Mapping Node Mapping Node Federated Controller ContexControl ContexControl SDN Controller SDN Controller ContexSwitch ContexSwitch Overlay Network OpenFlow Switch OpenFlow Switch Outerlay Network
16
HPE Carrier Grade ODL - High Availability
Redundant alternative integration points Per Node leader elections ensure efficient and consistent control Orchestration AAA ContexBroker ContexBroker Every ContexNet element is protected in N+1 all active groups Multiple underlay paths for inter-ContexNode connectivity Preprovisioned standby service chain paths protect against NF failure
17
Controller Scalability
VNF 200 K OF/s 1000 OpenFlow entities 1000 VNF Interfaces 8 JVM’s 8 Control VM’s Control Nodes 500 Map Nodes 100 K LISP TPS Multiple nodes Multiple controller VM’s per node Multiple controller JVM’s per VM (each with limited memory optimizing GC) Distributed and highly available state between controllers Assignment of VNF to OpenFlow switch may be dynamic
18
Thank you
Similar presentations
