- The document discusses an OpenDaylight update presented by Luis Gomez, including topics around release streamlining, community reports, priorities, and use cases. - Key releases mentioned are Carbon, Oxygen, and Fluorine. Managed vs. self-managed projects and maturity adjustments to the project model are covered. - Community contribution stats and goals to expand contribution, improve documentation, and enhance the release model are highlighted. Technical goals around stability, Java upgrades, and release automation are also summarized.

1. OpenDaylight Update
Luis Gomez, Lumina Networks
ODL TSC member, committer and contributor

2. Topics
• Release Streamline
• Community Report
• Priorities
• Use Cases

3. Release Streamline

4. Service Abstraction Layer/Core
OpenDaylight Carbon Release
OVSDB NETCONF
PCMM/
COPS
LISP PCEP SNMPSXPOpenFlow
USC
Control Plane Functions
OpenDaylight APIs REST/RESTCONF/NETCONF/AMQP
Data Store (Config & Operational) Messaging (Notifications / RPCs)
LACP
AAA Authorization Filter
Network Abstractions
(Policy/Intent)
Graphical User Interface Application and Toolkit (DLUX / NeXT UI)
IoT
Http/CoAPOF-Config
Embedded Controller Applications
Independent Network Applications
• AAA
• Host Tracker
• Infrastructure Utilities
• L2 Switch
• LISP Service
• Link Aggregation Control
Protocol
• OpenFlow Forwarding
Rules Manager
• OpenFlow Stats Manager
• OpenFlow Switch Manager
• Topology Processing
• OVSDB Neutron
• SN Integration Aggregator
• Service Function Chaining
• Time Series Data Repository
• Unified Secure Channel Mgr
• User Network Interface Mgr
• Virtual Tenant Network Mgr
• Cardinal
• Controller Shield
• DOCSIS Abstraction
• Eman
• Genius
• NetIDE
• NetVirt
• Neutron Northbound
• ALTO Protocol Manager
• Fabric as a Service
• Group Based Policy
Service
• NEMO
• Network Intent
Composition
OCPBGP

5. OpenDaylight Platform (Yangtools, MD-SAL)
OpenDaylight Oxygen Release
OVSDBNETCONFLISPPCEP SNMPOpenFlow USC
OpenDaylight APIs (REST/RESTCONF/NETCONF)
Data Store (Config & Operational) Messaging (Notifications / RPCs)
OF-Config
Orchestration Applications
P4 BGP
Network Services And ApplicationsPlatform Services
• Authentication, Authorization and
Accounting
• Data Export Import
• Infrastructure Utilities
• JSON-RPC Extension
• Time Series Data Repository
• Application-Layer Traffic Optimization
• Bit Indexed Explicit Replication
• Container Orchestration Engine
• Genius Framework
• Group Based Policy
• Honeycomb/Virtual Bridge Domain
• LISP Service
• Neutron Service
SXP PCMM COPS
• Network Modeling Engine
• Network Virtualization
• OpenFlow L2Switch
• PacketCable Service
• Service Function Chaining
• Unified Secured Channel Manager
• Virtual Tenant Network
Control Plane Applications Other Applications (e.g. Vendor UI)

6. OpenDaylight Platform (Yangtools, MD-SAL)
OpenDaylight Fluorine Release
OVSDBNETCONFLISPPCEPOpenFlow
OpenDaylight APIs (REST/RESTCONF/NETCONF)
Data Store (Config & Operational) Messaging (Notifications / RPCs)
Orchestration Applications
BGP
Network Services And ApplicationsPlatform Services
• Authentication, Authorization and Accounting
• Data Export Import
• Infrastructure Utilities
• Service Utilities
• ODL Tools
• Container Orchestration Engine
• Genius Framework
• LISP Service
• Neutron Service
• Network Virtualization
• Service Function Chaining
SXP
Control Plane Applications Other Applications (e.g. Vendor UI)

7. Project Maturity Adjustments
• Only successful, well consumed projects survive.
• Less contributors with more focus.
• Quality over quantity trend.

8. Managed vs Self-Managed Model
• Managed projects have a solid foundation and healthy community.
• Self-Managed are the opposite, either because the project is very
new or it is not very consumed.
• Managed projects have 3 checkpoints in a release cycle and they
are part of the ODL official release (every 6 months).
• Self-Managed projects do not have any requirement, they can
release at any time and be part of the ODL official distribution if
they choose so.

9. Community Report

10. Contribution
Source: Bitergia (https://opendaylight.biterg.io)

11. Affiliation (18-Q1)
Source: Bitergia (https://opendaylight.biterg.io)

12. Priorities

13. Community Goals
• Expand Contribution Base, specially on Kernel projects
• Reach downstream communities and companies
• Improve Release Model
• Managed vs Self-managed
• Improve First-Impression Documentation
• Appoint team to update common docs
• Infrastructure Efficiency
• Remove low used build/test jobs
• Cross-Project CI/CD
• OPNFV integration

14. Technical Goals
• Cluster Stability
• More test and more bug fixes
• Java Upgrade Strategy
• New java release every 6 months
• Improve Developer documentation
• Update tutorials
• Create Release automation tools
• Patch E2E verification jobs
• Self-Managed release tools

15. Use Cases

16. Network Abstraction
Management Interfaces
(Netconf, REST, OVSDB)
White Box
Device
Traditional
Network device
Control Interfaces
(OpenFlow, BGP, PCEP)
OpenDaylight
Orchestration/OSS/Cloud plugin
Network Services API
(Path, Tunnel, L2/L3/L4 Service, Service Assurance, etc)

17. Data Center Networking

18. ONAP project