Building Open Source-Based Cloud Solutions with OpenDaylight. Colin Dixon, Brocade/OpenDaylight Lisa Caywood, OpenDaylight

Transcription

1 Building Open Source-Based Cloud Solutions with OpenDaylight Colin Dixon, Brocade/OpenDaylight Lisa Caywood, OpenDaylight

2 Part of a New OPEN Networking Stack Networking Apps ORCHESTRATION (NFVO,...) Mgmt / Analytics App ECOMP Rest API SDN Platform YANG OpenFlow Netconf Open NOS HW HW OVSDB s / Cont. BGP Legacy HW Custom Optical

3 OpenDaylight Now OpenDaylight fundamentally changed the Linux Foundation s world. It s been wildly successful. It s the de facto standard open source SDN controller for the industry today. - Dave Ward, Cisco CTO *SDxCentral, 9/7/16 Mature, Open Governance 800+ Contributors Over 100 deployments Leading use cases identified Dozens of ODL-based solutions Mature code base Focus on performance, scale and extensibility

4 Boron Features and Capabilities Integration - industry frameworks Operational tooling OPNFV OpenStack enhancement CORD/vCO ECOMP ONF/Atrium Cardinal health monitoring Data analytics (TSDR & Centinel) OCP (Open radio I/F) Documentation App developer tooling Common SDN toolchains Net Virtualization + SFC: OF + OVSDB + OVS/FD.io Mgmt plane programmability: BGP + PCEP + MPLS + NETCONF YANG-IDE toolkit NetIDE for cross-oss controller interoperability NeXt UI toolkit Singleton app HA Documentation

5 OpenDaylight Boron in Open Clouds The glue that holds together L2-7 networking functions Coordinates physical and virtual resources Network, compute, storage Network virtualization with service function chaining OpenStack-based network virtualization Virtualized Central Office (vco; AKA CORD)

6 OpenDaylight with OpenStack

7 OpenDaylight Boron

8 OpenStack/OpenDaylight Integration Multiple Neutron implementations Target different use cases, southbound drivers FD.io/VPP OVS Open Overlay Router (née LISPmob) Provide distributed implementations of scalable network virtualization for OpenStack

9 OpenStack/OpenDaylight Integration L2: ML2 plugin L3: ODL L3 plugin services QoS L2GW FWaaS ODL driver ODL L3 Plugi n ODL driver Mechanism Manager ODL driver Type Manager SR-IOV FWaaS L2Gateway QoS LBaaS BGPVPN networking-sfc trunk Service Plugins ML2 Plugin ODL mech driver... VXLAN TypeDriver VLAN TypeDriver GRE TypeDriver Neutron Server networking-odl

10 OpenStack and OpenDaylight Integration Network/Control Node Controller node OpenDaylight* Neutron Neutron Northbound ML2 Plugin Networking-odl Management Network Data Network ML2 DB ovsdb/netvirt Compute Node Yang Model OVS Networking Node DHCP Agent OVS Internet Public Network Router

11 OpenDaylight in vco and ROBO

12 What does Central Office do? Subscriber management capabilities: Gateway, authentication and authorization, event and subscriber information logging Optical Line Termination (OLT) for PON/GPON (Passive Optical Net.) Service functions: self-service portals, NAT, FW, routing, IP addr mgmt, QoS, quotas, video caching, mail and file stores A Virtualized Central Office (vco): Uses general-purpose compute, storage and network capabilities to deliver the above services Added agility (spin up s vs. rack and stack hardware) Cost savings (via increased automation and commodity servers)

13 vco Data Center Architecture Physical elements are divided into Network: provides fabric/underlay Servers: provides computer/storage for s N o r t h S o u t h Fabric/Underlay (Network) Servers/s (Compute, Storage) WAN East West WAN

14 vco Data Center Architecture Controllers and orchestrators use overlay networks to form service chains of s N o r t h S o u t h WAN East West WAN

15 vco Data Center Software Architecture OSS/BSS Policy (NIC, NEMO, GBP, Neutron) Service Overlay Fabric Chaining Network SDN Controller (OpenDaylight) O (ECOMP, Open-O, OSM, ) Spec (TOSCA) Catlog M (Tacker, Cloudify, ) VIM (OpenStack, Kubernetes, ) Fabric/Underlay (Network) Servers/s (Compute, Storage)

16 ROBO: Using vco Blueprint in Enterprises - vco for Enterprises to provide for Remote/Branch offices - - Maybe offered by ISPs as a service Integrating with public cloud will likely involved some form of vco (either aas or Enterprise-deployed) Hybrid Cloud will almost certainly involve vco vcoaas from ISP Private Cloud Remote Office Public Cloud Branch Office vco to connect backends Main Office

17 Think Beyond the Controller Product Enabling solution component

18 Thank you