ODL to provide a minimum set of components from ODL to narrow the attack surface and CVE exposure
Will have monthly sync meetings between ODL/ONAP into the future starting week of
What made it an effective discussion
Being f2f is powerful to help discussions/collaboration
ODL prefers to have DDF before the start of the next releases - so ONS aligns well with the ODL schedules
Chaker Al-Hakim set aside time for cross-community discussions at joint events
Events and TAC/MAC role
LFN sponsored events ONES - MAC lead the events
DDF/Plugfest joint project events - community inputs on timing/location
GB moving to LFN paid developer events instead of member volunteered sites
TAC as a broker to help consolidate community desires for joint events
fd.io's audience differs from large orchestration projects and thus it is not served by joint DDFs with such projects. fd.io needs its own DDF, or a DDF in collaboration with other dataplane projects such as DPDK, OVS, etc.
Propose projects get event budget to allocate as they wish
AI: TAC would like a description of the event strategies for each project so that TAC might help broker dates/approach
user-20f1f Recommends that we augment ONS with the developer events.
GB review of the SPC contributions
Board has asked SPC to balance internal focus and external adoption focus
TAC action items from GB
technical architecture white paper (gaps, overlaps, touchpoints)
Help articulate how the LFN pieces fit together
Identify synergies to encourage collaboration
Something like a landscape slide that shows relationships
Showing dependencies would be useful (eg. ONAP has dependencies on ODL jars)
Intended audience: utility to both internal/external - need clarification
All LFN projects focus on the delivery of NFVs and ultimately VNFs
Overlaps exist - we know that mapping is the first step in understanding
Volunteers for technical architecture review of LFN projects