OVSDB/Neutron Support in Lithium and Beyond ODL Technical Work Stream Call February 23, 2015
Background OpenStack Neutron has been a target use case for ODL since the beginning OpenDOVE, OVSDB and VTN all provided Neuton interfaces in Hydrogen Continues to be important Raised at the board and TSC levels Considerable developer/community/user interest
OpenStack/ODL Community Success OpenStack/ODL community relationship is key for ODL s success and shaping Neutron Do not expect OpenStack to come to ODL. ODL must show up in OpenStack community as peers. Key: listen to community needs Many alternatives means ODL needs to be easy to use, meet OpenStack s needs, and requires active advocacy/evangelism/engagement to rise to the top. Assuming we are better or know better is road to irrelevance Bottom line: Collaboration and community
Relevant Projects in ODL Newly created Neutron northbound project API stubs; recently factored out of controller Projects implementing Neutron OVSDB OpenDOVE (only in Hydrogen) VTN Plugin to OpenContrail LISP flow mapping (planned for Lithium) Group Based Policy (planned for Lithium)
Relevant Projects in ODL Newly created Neutron northbound project API stubs; recently factored out of controller Projects implementing Neutron OVSDB OpenDOVE (only in Hydrogen) VTN Plugin to OpenContrail LISP flow mapping (planned for Lithium) Group Based Policy (planned for Lithium)
OpenDaylight + OpenStack ODL + OpenStack The OVSDB project houses the ODL OpenStack CI for the default ODL Neutron plugin Large, diverse influx of people into OVSDB recently Brocade, Cisco, HP, Inocybe, Intel, Red Hat This is big progress in just the last month or so This is a the current plan to use OVSDB as a way to help OpenStack/ODL integration
OpenStack Community Engagement ODL developers need to engage OpenStack community Starting to happen (Yay!) This includes teams outside of Neutron like infra/qa Engagement at the upcoming OpenStack Summit important
OVSDB Tasks for Lithium Abstract network virt. from OVSDB library and plugin Remove AD-SAL dependencies Support existing OVSDB plugin interface for VTN Add MD-SAL southbound plugin Migrate network virt. to MD-SAL southbound plugin Test and improve scale, stability and performance Close feature gap with Neutron and OpenStack OVS plugin, e.g., L3, LBaaS, FWaaS, VPNaaS
OVSDB Tasks for Lithium Abstract network virt. from OVSDB library and plugin Remove AD-SAL dependencies Support existing OVSDB plugin interface for VTN Add MD-SAL southbound plugin Migrate network virt. to MD-SAL southbound plugin Test and improve scale, stability and performance Close feature gap with Neutron and OpenStack OVS plugin, e.g., L3, LBaaS, FWaaS, VPNaaS
Neutron Tasks for Lithium Migrate Neutron to its own project Rework bundles and features to better represent the Neutron implementation Triage existing bugs Add YANG model and MD-SAL provider Ed, Ryan and Flavio have been doing a great job tackling these tasks already
ODL Stackforge Migrate ODL ML2 plugin to it s own repo Leverage the plugin functionality in devstack, so new plugin (aka networking-odl) is seamlessly integrated with local.conf Enable Tempest tests Integrate with OVSDB Jenkins jobs to enable robust integration testing
Future Work Items Close feature gap with Neutron and OpenStack OVS plugin, e.g., L3, LBaaS, FWaaS, VPNaaS Migrate network virt. northbound to use MD-SAL Neutron Migrate network virt. from OVS specific to tunnel management and traffic direction (into tunnels)
OVSDB Evolution In reality, this may be optimistic Near future ~= Lithium, Lithium ~= Beryllium?
Opportunities to Help MD-SAL migration MD-SAL southbound plugin Future work items: advanced services, MD- SAL neutron, tunnel-like southbound OpenStack engagement, understanding the communities needs and how ODL can help