NETWORK FUNCTIONS VIRTUALIZATION (NFV) FORCES-BASED ABSTRACTION LAYER

Transcription

1 NETWORK FUNCTIONS VIRTUALIZATION (NFV) FORCES-BASED ABSTRACTION LAYER Evangelos Haleplidis Jamal Hadi Salim Joel Halpern ) Odysseas Koufopavlou Spyros Denazis (sdena@upatras.gr)

2 Goal Define and Deploy Network Functions (NFs) (NFVrelated) White paper clearly defines problem statement NF Abstraction model to enable common handling of NFs Integrate deployed NFs into datapath (SDN-related) Required for faster and reliable deployment of NFs Requires separation of control/forwarding plane Can we do both with the same framework?

3 (Enter) ForCES Framework Network Element (NE) Control Plane Control Control Control Element (CE) Element (CE) Element (CE) Network Element (NE) Packet Processing Entity Constitutes of CEs & s Multiple CEs to s for HA CEs/s Physical or Virtual ForCES protocol Forwarding Plane Forwarding Forwarding Forwarding Element () Element () Element () NE components distributed Local (within one box) Geographical distributed (LAN/WAN/Internet)

4 ForCES & SDN (obvious correlation) Application Application SDN SDN NorthBound API Network Operating System SouthBound API Control Plane NorthBound API Network Operating CE System SouthBound API ForCES Control Plane Network Devices Forwarding Plane Network Devices Forwarding Plane

5 ForCES model - 1 Graph of Logical Functional Blocks Control Element (CE) Graph can be dynamic if supported by implementation ForCES Hardware/Software Physical/Virtual Fine grained operations P LFB1 LFB3 P+M LFB2 LFB4 Object-oriented approach Classes Instances Etc LFB3 Forwarding Element () LFB4 P: Packet M: Metadata

6 ForCES model - 2 Datatypes definition LFB Definition Components Capabilities Events LFB Model defined in XML Datatype definition C-like datatypes Atomic (uint, string, etc ) Compound (Structs/Arrays) Alias Building blocks for custom-defined datatypes. Component definition Operational parameters ACL (Read/Write) Capability definition Event definition Target/Condition/Reports Subscription based

7 ForCES protocol CE Protocol Layer (ForCES protocol) Transport Layer (SCTP) Transport Layer (SCTP) Protocol Layer (ForCES protocol) ForCES Protocol & Transport Layer Base ForCES semantics and encapsulation (RFC 5810) Transport depends on underlying media. One is standardized (RFC 5812) others expected to be Semantics Simple Verbs Transactional capability (2PC) Various Execution modes Scalability via batching and command pipeline Security Traffic Sensitive Heartbeating High Availability

8 So? Why ForCES for NFV? Initial ForCES design for controlling forwarding engines BUT! Model is: Extensible/Powerful/Descriptive Unrelated to physical/virtual implementation Protocol is: Rich in features Agnostic to the model Conclusion: ForCES defines a base abstraction layer for any separation Can be applied where operational parameters are defined

9 ForCES & NFV ForCES NF definition Define a Network Function (NF) as either: An LFB (a) or a series of LFBs (b) (LFB chain) An LFB chain may go across s (new charter work) An (c) or a series of s (d) ( chain) Immediate gain: Manage operational parameters of NF Network Function Network Function Network Function Network Function LFB1 LFB1 LFB2 LFB3 (a) (b) (c) (d)

10 ForCES & NFV Overview ForCES model: Does not care if NF is virtualized or not Components are the operational parameters of the NF ForCES protocol (one for all): Instantiate/Destroy NFs (Define Hypervisor as an ) Connect LFBs within same (current proposed standard) or interconnect with other s (new charter work) NFs One protocol for both network device management & NF deployment and configuration

11 NFV ForCES Abstraction Layer App App App App Network Function Manager / Orchestrator ForCES Abstraction Layer Service Plane Management Control Plane ForCES Layer ForCES Layer ForCES Layer ForCES Layer Layeryer ForCES Layer Network Plane ForCES ForCES ForCES VM VM VM VM VM VM ForCES ForCES ForCES Network Network Devices Devices Network Devices Hypervisor Hypervisor ForCES ForCES ForCES VN VN F F F Network Network Devices Devices Network Network Devices Devices Network Devices ForCES Layer ForCES Network Devices Network Devices ForCES (for configuration) ForCES (for management) Open API (with ForCES semantics) ForCES can be used for both control and management. Dotted line is only for visual differentiation. Network Device: Any device connected to the network. From an NFV perspective a switch is a L2 NF.

12 ForCES & NFV Use Cases (1) On existing hardware, using ForCES Locate Network Devices that support the NF Instantiate and configure the operational parameters of the NF Integrate NF with the datapath by managing the network device

13 ForCES & NFV Use Cases (2) On virtual machines, using ForCES Boot-up required VMs with required NF based on profile Manager LFB (hypervisor) Initial configuration of NF Integrate Function with the datapath by managing the network device

14 ForCES & NFV Use Cases (3) Hybrid mode, using ForCES Part of NF could reside in hardware Part of NF could be boot-up in VM Interconnect to instantiate NF (new re-charter work) Integrate Function with the datapath by managing the network device LFB3 LFB3 P LFB1 P+M LFB2 Inter LFB P+M Inter LFB P+M LFB2 LFB4 LFB3 LFB4 Forwarding Element () (Hardware) LFB3 Forwarding Element () (VM) LFB4

15 IETF ForCES & ETSI NFV ISG Activities Standardize the operating parameters & a base LFB of Network Functions Coordination between with IETF ForCES working group and ETSI NFV ISG ForCES can be used for the northbound interface (orchestrator to apps) (not in recharter) Requires minor changes to ForCES protocol (for clean solution) Service chaining ForCES s & LFBs for s Bootstrapping & dynamic element insertion interfaces

16 Questions Thank you for listening

17 Backup 1 ForCES framework CE Manager Manager ForCES Network Element Control Plane CE CE Forwarding Plane Interface between CE & Manager Interface between CEs Data Path. Interface between s or external interface Interface between CEs & s. ForCES Protocol. Interface between Managers and Elements

18 Backup 2 SCTP TML CE Protocol Layer (ForCES protocol) Transport Layer (SCTP) HP MP LP Transport Layer (SCTP) Protocol Layer (ForCES protocol) Strict Priority Scheduling High Priority (HP): Strictly reliable channel Configs and Queries issued by CE Response by the Medium Priority (MP): Semi-reliable Event notifications from Low Priority (LP): Unreliable channel Packet Redirects and HBs

19 Backup 3 Inter-LFB (recharter work) Control Element (CE) Control Element (CE) LFB3 LFB3 P LFB1 P+M LFB2 Inter LFB P+M Inter LFB P+M LFB2 LFB4 LFB3 LFB4 LFB3 LFB4 Forwarding Element () Forwarding Element ()

20 Backup 4 ForCES & more SDN Application CE CE CE Application NorthBound API Network Operating CE System SouthBound API Control Plane SDN NorthBound API Network Operating CE System SouthBound API Control Plane SDN Network Devices Forwarding Plane Network Devices Forwarding Plane

21 Backup 5 Boot up profiled VM On virtual machines, using ForCES Boot-up required VMs with required NF based on profile Manager LFB (hypervisor-style) Array of and LFB instances that will be instantiated per Function and the connection graph Array of Locations for instantiation Array of instantiated Functions (Array of {Function, Location}). (Set the array == instantiate ) Initial configuration of NF Integrate Function with the datapath by managing the network device

22 Backup 6 Define a new NF Model LFB(s) (e.g. using UPatras ForCES DSL) Parse model and generate code (e.g. with Mojatatu SDK) Write specific hardware code (if missing) Instantiate/Deploy with Manager LFB