Inves&ga&ng Intent API for Service Chaining. Andy Veitch NetCracker (NEC)

Transcription

1 Inves&ga&ng Intent API for Service Chaining Andy Veitch NetCracker (NEC)

2 Goals Define and develop Intent NBI for service chaining Define for mul&ple underlying implementa&ons avoid network details Develop for a known use case network access services Learn Iden&fy holes and areas to address Provide recommenda&ons for SDO Advance open source Open Daylight NIC work Limit scope

3 Intent NBI Applica&ons Describes what the applica&on wants No prescrip&ve informa&on nothing about how the service is to be fulfilled May be hierarchical services composed of other services Goal also to enable portability and interoperability deliver services irrespec&ve of underlying technology Appl. 1 Appl. 2 Appl. 3 Appl. 4 Appl. N Intent NBI Black Box Orchestra&on and Control SBI Adapta&on Layer NetConf OpenFlow Custom NBI I2RS DOCSIS SDOs and open source projects with ac&ve intent work IETF (SUPA BoF, NeMo?) ONF Open Daylight (NIC, GBP) ONOS OpenStack (Congress, GBP) OPNFV hpps://wiki.opnfv.org/_media/mee&ngs/hares- opnfv- movie- usecases.pdf

4 Build on Open Daylight NIC model for Intent NIC included in ODL Lithium release Ini&al intent grammar defined designed for augmenta&on Uses Yang models to represent Intent NBI defini&ons Use Virtual Tenant Networks current project in ODL NIC Target NBI to be independent of underlying technology

5 What is VTN? OpenDaylight Virtual Tenant Network (VTN) VTN is a logical abstrac&on plane separa&on from physical plane Provides mul&- tenant virtual networks on an OpenFlow SDN controller hpps://wiki.opendaylight.org/view/ OpenDaylight_Virtual_Tenant_Network_(VTN):Main

6 VTN Example interface vlink Logical Network vbridge vbridge vbridge vtunnel vbridge VTN vrouter vtep vbypass vtep VTN(Underlay) Controller 1 Controller 2 Controller 3 Inter-DC DC 1 DC 2 network DC 3 Physical Network

7 VTN Support for Flow Filtering and Traffic Redirec&on Apply flow filtering (a FEC) on any vnode e.g. vbridge, vrouter Intent redirect traffic to different node base on traffic type Example Configura&on Server-A vbridge1 Tenant1 Server-B vterminal1 Server-C vtn Tenant1 { vbridge vbridge1 { flow- filter in { sequence- number 1 { match flow- list match- list- a ac&on redirect redirect- des&na&on vnode vterminal1 interface if1 } (snip) }

8 Open Daylight NIC Network Intent Composi&on Intent Model Subject Ac*ons Condi*ons Constraints Similar (if not the same as) English grammar Subject, verb, object, predicate Subject Labels to iden&fy groups of endpoints (affinity) Ac&ons Ini&al set arrived at from ini&al use cases ALLOW, BLOCK, AUDIT, LOG. INSPECT, BANDWIDTH, REDIRECT, INJECT, LATENCY, LOSS, PROTECT, SECURE, QOS Constraints Constrain how an intent is to be implemented Described in abstract terms, no network or deployment specifics Include- subject intent instance must involve a given subject Exclude- subject intent instance must NOT involve a given subject Condi&ons Defines when Intent is to be ac&ve See presenta&on at hpp:// the- intent NIC project wiki page a hpps://wiki.opendaylight.org/view/network_intent_composi&on:main

9 Open Daylight NIC Network Intent Composi&on Designed to be augmented Modules can augment Subjects, Ac&ons, Constraints, Condi&ons Modules can implement renderers translate intents to network model changes

10 Virtual Home Networks - Challenges Operational Concerns Virtualized Functions Back-office integration Customer Portal Analytics Multiple Routers Mobile STB Linear & DVR Security firewall routing provisioning BW on Demand Network Address Translation Parental controls Router E.g. Firewall E.g. Routing APIs Tablet Router Cable Gateway Subscriber Home Encapsulation Control Protocols Virtualization Platform Phil MSO PC Cable Television Laboratories, Inc Do not share this material with anyone other than CableLabs Members, and vendors under CableLabs NDA if applicable. 10

11 Forwarding of Network Traffic to Deliver Services150 VNFs are in the operator s data centers the Cloud The specific type and configura&on of each VNF is based on the intent, context and relevant policies Data Center / Value Added Services Child Parental Control Firewall DLNA Media Server Tablet Flow Filter Adult Notebook Computer Access Switch Modem CPE Or Access Internet Family TV / Media Center DLNA Client

12 Intent NBI for Service Chaining Top Level Intent (GUI) Policies and <user xyz> context Provide user xyz the Family Gold service and add DDoS service Family Gold composed of services children access, adult access, media access, broadband access (100Mbps) Intent NBI for each component service Provide user xyz children access, etc. Children access service composed of Parental Control and Firewall service - Iden&fy affinity group of child endpoints (MAC addresses) (Match) Iden&fy home media center endpoint (group) ( (Match) Set of NIC Intent input Redirect child group to parental- control and and firewall to internet Redirect adult group to firewall and to internet Layers of abstrac&on and models Top level NBI to lowest layer implementa&on Redirect media group to media server Create 100Mbs connec&on to xyz VTN setup configure filters, VTN virtual infrastructure vcpe Parental Control FW Media Server DPI Analy?cs VTN

13 ETSI Network Services and Virtual Network Func&on Forwarding Graphs (VNFFG) Difficult to map layers of intent no support today for composi&on of services single layer of abstrac&on Networks services can include mul&ple VNFFGs choose op&on based on condi&ons and policies must have all possible VNFFGs defined Could model NS, VNFFG, etc. as Yang Not Intent NSD Base Element ETSI GS NFV- MAN 001 V1.1.1 ( ) Id Vendor version vnfd vnffg vid lifecycle_event vnf_dependency monitoring_parameter service_deployment_flavour auto_scale_policy Connec?on_point pnfd nsd_security Leaf (1) Leaf (1) Leaf (1) Reference(1..N) Reference(0..N) Reference(0..N) Leaf(0..N) Leaf(0..N) Leaf(0..N) Element(1..N) Leaf(0..N) Element(1..N) Reference(0..N) Leaf(0..1)

14 Architectural View BSS / Applica?ons Intent NBI Intent NBI Layers Including NIC NBI Parser and Renderers End- 2- End Service Orchestrator Policies and Context Intent NBI Os- Ma- Nfvo Provide informa?on about Network Services capabili?es and op?ons Choose op?ons and configura?on vales, control NFVO SDN Controller NFVO (MANO, ETSI) Access and Transport Networks Virtual Network, Network Services SDN Controller

15 Conclusions / Future work Vocabulary and seman&cs must be aligned among coopera&ng souware agents Mandatory to support portability / interoperability It can be difficult to define across domains IETF should con&nue work to define modeling build commercial experience and open source Should SUPA be moved to WG, same comment regarding policies Composi&on of services is very important to support code reuse layers of NBI and models ETSI should consider these requirements and need for flexibility Con&nue work to develop chaining NBI FWIW Open Daylight summit next week presenta&on on chaining on ODL VTN