Open Stack Open Day LIGHT Close to PRODUCTION

Open. Stack* & Open. Day. LIGHT* Close to PRODUCTION Dr. Malini Bhandaru – Architect, Principal Engineer, Intel Isaku Yamahata – Cloud Network Architect, Intel ODL Northbound PTL, Open. Stack-Neutron-ODL core May 2016

Agenda Introduction Open. Stack* + Open. Daylight* Six Months back Today Future GIVE IT A TRY!!! Stability, Scalability, Feature Parity, Security, Performance 2

Quick Introduction: Open. Stack, ODL Open. Stack (OS)*: Open source cloud operating system Iaa. S allocates shared resource pool (compute, storage and networking). Goals: Agile self service (end-user), reduced total cost of ownership (operator) http: //www. openstack. org/ Open. Daylight (ODL)*: A Software Defined Network (SDN) controller Goals: Agile tenant isolated network provisioning and control with SLAs support Virtual Network Functions https: //www. opendaylight. org

User Industry Segments: Telco (73%), Finance, Entertainment, and Energy • Self Service • Network Function Virtualization • Resource Optimization • Visibility and Control https: //www. opendaylight. org/news/blogs/2016/02/2 016 -survey-shows-more-and-diverse-sdn-use-casesbeing-deployed-open-sdn-power Traffic Engineering [VALUE] % Network Monitoring, 27% Management & Analytics [VALUE]% Network Service Creation [VALUE]% NFV & Cloud

Open. Stack* and Open. Daylight* Networking-odl ODL neutron northbound Management Network Data Network Control node Neutron Open. Daylight* Compute Node VM OVS Network Node dhcp agent OVS Internet Public Network Router

OS + ODL Six Months Back

Open. Stack* + ODL == Six Months Back • Brittle integration • Lacked Neutron High Availability (HA) support • Incomplete and unstable API – Limited test coverage • Develop/Test tedious Intel Open source Technology Center (OTC)

OS Mitaka + ODL Beryllium TODAY

What’s new with OS-Mitaka + ODL-Be? Open. Stack* (Mitaka release networking-odl) Open. Daylight* (Beryllium release) V 2 driver: neutron HA Stabilization/hardening OVS-DPDK* Lightweight test framework L 2 GW BGPVPN Testing 30 tempest API Test bug fixes Increased Neutron Northbound API coverage 47% 65% Data Plane Development Kit == DPDK*

Smoother Integration • Security Group Rules only accepted TCP, UDP, ICMP, and ICMP 6 Extended to other protocols - strings and short integers https: //git. opendaylight. org/gerrit/#/c/36010/ https: //git. opendaylight. org/gerrit/#/c/33932/ 10

Neutron HA WOES

Open. Stack* and Open. Daylight* Networking-odl ODL neutron northbound Control node Database Neutron Open. Daylight* MD-SAL Management Network Data Network Compute Node VM OVS Network Node dhcp agent OVS Internet Public Network Router

Neutron-ODL Interface Issues • Neutron-ODL ML 2 interface was single threaded and blocking • Performance issue • Inadequate DB synchronization with Multiple Neutron-Servers • Race conditions and inconsistencies • Lack of Switch independent mapping of physical interfaces and networks • Need for static configuration files 13

Lack of DB Synchronization Race Conditions and inconsistencies Courtesy: https: //wiki. opendaylight. org/images/8/8 d/Experiences_with_Neutron. pdf 14

Synch on next Neutron Event - Repeat Errors Courtesy: https: //wiki. opendaylight. org/images/8/8 d/Experiences_with_Neutron. pdf 15

Neutron HA DB Neutron Networking-ODL Syncer Operation Log Load. Balancer (HAProxy) Open. Daylight* MD-SAL Open. Daylight* Neutron Northbound Open. Stack* Service Provider Openflow* Enhanced component OVSDB New component Compute Node ODL-Boron – HA focus VM OVS Compute Node VM OVS

EASE DEV & TEST Both Open. Stack* and Open. Day. Light* Savvy? Have lots of Time on your hands? Have lots of Hardware resources?

Lightweight Test Framework Now Test Open. Stack* Open. Stack Neutron Networking-ODL mech driver Neutron and Open. Daylight interop ODL Open. Stack Neutron Networking-ODL mech driver Test Harness: Simulates ODL without Open. Daylight installation Neutron test without ODL Contact: rui. zang@intel. com Allows neutron side test without ODL

Approach • Record live Open. Stack test calls and results • Modify send. Json method to replay calls • Simulate Network errors / timeout, connection failure etc • Replay all calls and compare responses to expectations • Periodically check for API drifts, major and minor versions 19

Configuring Lightweight Test http: //git. openstack. org/cgit/openstack/networking-odl/tree/devstack/settings#n 10 # Each service you enable has the following meaning: # odl-neutron - Add this config flag if Opendaylight controller and Open. Stack controller are on different nodes. # odl-server - Add this config flag if Opendaylight controller and Open. Stack Controller are on the same node. # odl-compute - Add this config flag for Open. Stack Compute. # odl-lightweight-testing - Add this config flag for testing neutron ODL ML 2 driver and networking-odl # without a real running Opendaylight instance

Lightweight Test Framework Future We will be able to test API test Test ODL side without Open. Stack! Tempest Neutron client mock Neutron ODL-Neutron interop ODL mech driver without Open. Stack Nova/Neutron VIF Driver ODL OVS Tempest runs only with ODL-Boron focus

Today Open. Stack* Mitaka Open. Daylight* Beryllium • Neutron-ODL driver overhaul • Northbound API improvements • Supports High Availability (HA) • Light weight test framework • Increased test coverage • Bug fixes galore • Networking L 2 Gateway • Networking BGP VPN 22

Test DASHBOARD

Open. Stack + ODL Tempest Tests Open. Stack code change velocity greater. Running tempest tests only when ODL patches are submitted catches conflicts late. Intel runs daily: § (OS-master x ODL-master) , (OS-liberty x ODL_master) § API, Basic Operations, Advanced Operations, IPV 6 § L 2 and L 3 tests http: //opendaylighttests. github. io/odltest/ 24

OS + ODL Tempest Tests 25

API Tests 26

Failed Test Details test_create_list_port_with_extra_dhcp_options[id-d 2 c 17063 -37674 a 24 -be 4 f-a 23 dbfa 133 c 9] 27

Bridging Networks L 2 GW support Neutron API extension that can be used to express and manage L 2 Gateway components. In the simplest terms L 2 Gateways are meant to bridge two or more networks together to make them look at a single L 2 broadcast domain, possibly a physical network. BGPVPN Intel facilitated the discussions, and helped review the design and implementation. 28

Future – In progress • ODL HA Control Plane • ODL Lightweight testing • Scale Testing – using docker containers Scale Data Plane • Reduce hardware needs, • Ease automation • Enhance coverage - HA/DVR/Rally/Tempest/OVS/Linux. Bridge • Generic Port Binding • Qo. S support in ODL 29

Summary OS Mitaka + ODL Be Neutron HA Increased testing Bug fixes galore External Network access GIVE IT A SPIN!!! Stability, Scalability, Feature Parity, Security, Performance 30

References https: //www. opendaylight. org/use-cases/ http: //git. openstack. org/openstack/neutron-lbaas https: //git. openstack. org/openstack/networking-odl light weight testing: https: //review. openstack. org/#/c/225037/24 https: //www. youtube. com/watch? v=l 7 QRO 2 GU 9 P 8 http: //docs. openstack. org/developer/ networking-l 2 gw/ http: //docs. openstack. org/developer/networking-bgpvpn/ https: //wiki. opendaylight. org/images/8/8 d/Experiences_with_Neutron. pdf http: //www. slideshare. net/mirantis/openstack-architecture-43160012

Legal Notices and Disclaimers Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software or service activation. Learn more at intel. com, or from the OEM or retailer. No computer system can be absolutely secure. Tests document performance of components on a particular test, in specific systems. Differences in hardware, software, or configuration will affect actual performance. Consult other sources of information to evaluate performance as you consider your purchase. For more complete information about performance and benchmark results, visit http: //www. intel. com/performance. No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document. Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade. Intel and the Intel logo are trademarks of Intel Corporation in the United States and other countries. *Other names and brands may be claimed as the property of others. © 2016 Intel Corporation. 32