ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
TimeTitleSpeakersTarget AudienceAbstractNotes
2
Sunday 9/23
3
8:00 AMWelcomeCasey CainEveryone
4
8:05 AMFluorine Retrospective and SM Projects StrategyAbhijit Kumbrare
Ariel Adam
Luis Gomez		EveryoneLessons from Fluorine as the first managed release.
Fluorine has been the first release where Self-Managed projects have followed a different development and release process. During this presentation we will discuss what went well and not that well in this process, things we can improve for Neon release and where do we ultimately see Self-Managed projects in OpenDaylight, more decoupled from platform distribution, creating their own distribution and marketing for their releases for example.		Retrospective Google Doc: https://docs.google.com/document/d/16ssjcNRzP_uQr1HMZCkb_lc8gLeYNfqrGAI6XEw9Gko
(wznoinsk) regarding release notes, what OpenStack done with their project/developer of the code writing a release note in a plain text is fairly impressive: https://docs.google.com/spreadsheets/d/1EqBfglaO-wt3QeBRHjYBNiloPcBnkjtD2xPyDhYilEc/edit#gid=0 , example code + release note commited at the same time: https://github.com/openstack/neutron/commit/f7064f2b6c6ba1d0ab5f9872b2d5ad7969a64e7b#diff-4a718cbe61be62a62f11cc8840be58fb which is automagically converted (no human involved) into: https://docs.openstack.org/releasenotes/neutron/rocky.html
Tahn is working on it already
5
10:15 AM
6
10:20 AMContinuation of SM Projects Strategy
7
11:15 AMNeon MRI Integration WindowRobert VargaEach OpenDaylight release starts with a core infrastructure update coming from odlparent, yangtools and (for the first time) mdsal. These changes tend to break downstream projects and therefore require action on their part. This session will provide an overview of the incoming changes, what is the current state of preparation and a general discussion on what needs to happen next.Build beryllium based ncmount distribution of ODLrelesae dashboard: https://jira.opendaylight.org/secure/Dashboard.jspa?selectPageId=10403
8
11:45 AMLunch
9
12:45 PMKernel Projects PlanningRobert VargaKernel ProjectsThis session will discuss high-level deliverables and timing of what the offset-0 projects have planned for Neon and a lookahead what the Sodium MRI Integration Window can potentially contain. This is an overall syncup on what the committers in kernel projects are planning to do, when and how.
10
1:30 AMCOE Project PlanningAnilhis session will discuss the various features and activities planned for COE in Neon. We will also have a retro on our work for Fluorine. Topic for discussion but not limited to the following:
- Support for non-OF southbound like Netconf
- Scale testing of COE
- Deployment models for COE
- COE CSIT - Current status and learnings
11
2:45 PMBreak
12
3:00 PMGenius Project PlanningHema
Faseela		This session will discuss high-level deliverables and timing of what GENIUS has planned for Neon. This slot will be used by the genius committers and contributors on having a retro on the Fluorine release, and on the things that can be improved for Neon. We will also be giving an overview of what is new in Genius for Neon.
13
xNetVirt Project PlanningSam
Vishal Thapar		This session will discuss high-level deliverables and timing of what NetVirt has planned for Neon. This slot will be used by the committers and contributors on having a retro on the Fluorine release, and on the things that can be improved for Neon. We will also be giving an overview of what is new for Neon.
14
5:30 PMEnd of Day
15
Monday 9/24
16
8:00 AMManaged transactionsStephenGenius and NetVirt use a managed transaction framework to ensure that transactions are always closed correctly, and also that they only use a single datastore. This abstracts a number of concerns around transactions, hopefully allowing future improvements to the way they're handled. I'm hoping to move this framework to MD-SAL to make it available everywhere. This session will explain how it's used and its benefits.
17
8:45 AMNeon CI Jobs StabilzationAbhijit Kumbrare
Ariel Adam		Discussing different approaches of how to stabilize the Neon CI jobs targeting failed jobs to be the exception :-)https://docs.google.com/document/d/16ssjcNRzP_uQr1HMZCkb_lc8gLeYNfqrGAI6XEw9Gko/edit#bookmark=id.ufrke8dkdo6t
18
9:30 AMBreak
19
9:45 AMODL Test DashboardLuis GomezThis presentation is about the new framework prepared by Dibya Das (ODL intern) to automatically generate dashboards from CSIT jobs (feature + perf tests) in Kibana.
20
10:30 AMODL Tools Overview & PlanningVishal & SamThis will cover ODLTools, a new project added in Fluorine to make it easier to Troubleshoot, Monitor and Analyze OpenDaylight deployments. We will also discuss features planned for Neon release
21
11:15 AMetcd as ODL datastoreMichaelCome learn where we're at regarding running OpenDaylight with etcd as datastore in the project currently hosted on https://github.com/vorburger/opendaylight-etcd
22
12:00 PMLunch
23
1:00 PMOpenDaylight technical utilities (infrautils and genius)MichaelLearn more about various technical utility goodies available from ODL projects infrautils and genius: Metrics, Caches, System Ready-ness & DiagStatus, Component Tests utilities including Dependency Injection without OSGi Blueprint, MDSAL Transaction & Listener helpers, RPC wrappers, Jobs, Web API, Code Quality tools - we got you covered!
24
1:45 PMOpenDaylight without Karaf and OSGiMichaelCome learn where we're at regarding running OpenDaylight Simple <https://github.com/vorburger/opendaylight-simple> - a distribution of OpenDaylight without the OSGi-based Karaf foundation which underpins the ODL distribution you know today. Benefits to the Ecosystem: OpenDaylight's developer ecosystem growth is hampered by its choice of the OSGi architecture and Karaf platform, which -as much "fun" as they are- are basically "exotic" in the larger picture of the millions of people who have prior development expierence on the Java platform, and who are typically used to a simpler both programming and deployment model. This proposed new simpler alternative architecture removes a number of pain points which OpenDaylight development and integration is facing today.
25
2:00 PMOpenDaylight as MicroService or Spring Boot application.JurajLearn more about various possibilities of using OpenDaylight components in different runtime environments without Karaf OSGi. <https://lighty.io/> now under EPL v1.0 opens path from OpenDaylight / karaf to vast Java ecosystem and mainstream frameworks. Let's explore <https://github.com/PantheonTechnologies/lighty-core> and example applications running in development stacks like simple Jetty/REST HTTP2 microservice, Spring Boot application, gRPC stack integrations, constrained ARM devices, data analytics - pushing model data into ElasticSearch and many more.
26
2:45 PMBreak
27
3:00 PMOpenDaylight Scale and Performance in OpenStackSaiThis session goes over the current state of performance and scale testing of OpenDaylight for OpenStack use cases.
28
3:45 PMFeedback on ODL netconfGuillaumeThis is a short discussion to present the various issues identified during the development of TransportPCE, especially when developing our functional tests with stubs and when putting the controller in front of real netconf devices (potentially buggy). This includes various netconf server implementations such as testtool, honeynode, netopeer and conf-D. https://wiki.opendaylight.org/images/b/b2/Feedback_on_ODL_netconf.pdf
29
4:30 PMODL Software Quality ImpovementsBradyDiscuss how to start implementing ODL Software Quality Improvements in the Neon release. We have been discussing this since the Fluorine DDF, and have made a lot of progress. We will also present a gap assessment, detailing the effort involved for all of the managed projects to enable the Style Check and Find Bugs tools.Presentation slides: https://docs.google.com/presentation/d/1Zvyg46O1iwgdQ6A4hRWrK5rRSS8Cg3PHk7rOmpfiou4/edit?usp=sharing
30
5:15 PMODL status based on Bitergia Analytics DashboardAlbertoBitergia Analytics Dashboard (https://opendaylight.biterg.io) provides data and metrics for several ODL community areas. We will introduce the dashboard and discuss some use cases. About the latter one, the idea is to get feedback and assist the community. Attendants are more than welcome to propose use cases during the event or beforehand (please add them below, next to your name).
31
6:00 PMIt's a wrap!
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100