ONAP Track | Key Points | Challenges | Next Steps/Action Items |
---|
Track: Release Cadence Transition Proposal Presenters/Moderators: Krzysztof Opasiak | |
| - Follow-up is required to define the next steps
|
Track: CNF Orchestration through ONAP Presenters/Moderators: Seshu Kumar Mudiganti, Lukasz Rajewski | - Candidate for the Guilin Release
| - Modelling og the CNF data
- So far VNF model will be used with slight modification required to track status of instantiated k8s resources
- 7 components impacted, required cooridnation effort
| - The implementation for Guilin will introduce first production level solution for CNF
- It will open further changed for deeper integration of ONAP with CNFs fir Day2 configuration purpose or close loop support
|
Track: Closed Loop Target Reference Architecture and Rel G steps | - IBN was presented by Dong Wang - there were many questions that will be asked via Control Loop subcommittee mailing list. Would like to schedule a more in-depth review of this use case on 7/1 or 7/8?
- TOSCA presented by Michela Bevilacqua and Liam Fallon
- Vijay noted that DCAE-MOD for Guilin scope has been changed to include the pushing of a new catalogue. May effect this POC
- Discussion on future work for Control Loop subcommittee
| - Michela Bevilacqua : How to update a control loop instance?
- Scott Blandford : We've put together a model for simplistic control loops. How do we deal with CL's that are stringing multiple DCAE together? Or have multiple interactions? How to monitor?
- Pamela Dragosh : Monitoring tools may not be enough? Gervais-Martial Ngueko CLAMP monitoring is only capturing Dmaap events. Need much more development to support DevOps
- Vijay Venkatesh Kumar : Discussion to support multi-tenant, how would control loops work in that architecture? How does a distributed deployment play out?
|
|
Track: Guilin Release - TSC Prioritization Presenters/Moderators: Catherine Lefèvre and ONAP TSC | Big thanks to all the Requirement Owners for their submission ! Dear ONAP Community - Continue to support our project teams through your engagement; They have a lot to accomplish prior our next milestone (July 9th, 2020) !!! Heartily Thank You
|
| - Prepare our Release Commitments before July 9th, 2020
|
Track: Presenter: Marek Szwałkiewicz | During this talk we can see the best practices for writing tests using Robot framework: - do not keep all tests in one file, - keyword using, - variables using, - set up and teardown. All of them with examples. We can see also a Python ONAP SDK wrapper for Robot framework named robotframework-oapsdk. |
| - robotframework-onapsdk publish
- extend ONAP wiki pages about Robot (add more examples)
- publish template to create own Robot libraries
|
Track: Set up Kubernetes ENV guide in Ubuntu Presenters/Moderators: | |
|
|
Track:Service Mesh for RBAC and security PoC presenters: Sylvain Desbureaux Krzysztof Opasiak | Service Mesh PoC will require few changes on the component: - add an option to disable AAF integration on user management part if any
- add an option to disable HTTPs
- retrieve header and pass them if they are doing subrequest
| - Retrieve all component clients (sdc distribution clients, dmaap clients, ...) and make them service mesh aware (pass headers in particular)
| |
OpenDaylight Track | | Challenges | Next Steps/Action Items |
---|
Sync OpenDaylight releases and LFN infra migrations | Open discussion on how we can improve the LFN infra migration and ODL release cycles. Those migrations affect the overall efficiency of the community but not only.
- migrations not at all synchronized with the release schedules
- migrations misexecution affects every project
- python version froced and 3.5 obsoleted after only 2 months during the Sodium SR2 release. When possible, lfn-tools must support several versions of python and not impose it.
- migrations are not automated. This also results in unexpected referencing problems for potential new contributors
| - more transparency on LFN infra migrations - can be achieved with more non-LFN contributors
- TSC should be able to block LFN migrations
- control-loop between users / TSC and TAC/LFN
|
|
ODL BGPCEP Magnesium Retrospective and Roadmap for Aluminium | This retrospective presented a quick overview of Graph & Algo features introduce in BGPCEP project for compliance to RFC 5440. A short demo will highlight the new functionalities. The presentation also covered the roadmap for Aluminium release and reviewed new features that will be introduced to provide a Path Manager service. | RFC 5440 support Growth the community Next challenge for the project | Design a PTL and add more reviewers / committers |
ODL Service Automation Framework (SAF) |
|
|
|
ODL Platform Aluminum updates and Silicon lookahead | This talk provided details on what platform updates will be part of the Aluminum release. Also covered were potential platform updates in the next release, effectively doing some planning for Silicon. |
|
|
|
|
|
|
CNTT Track | Key Points | Challenges | Next Steps/Action Items |
RI-2 DeepDive | - Georg Kunz Rihab Banday presented the scope of RI-2, the plan for Baraque.
- Presented OPNFV - Kuberef project proposal. The proposal will be edited (one sentence to address the point in the Challenge column) and OPNFV TSC Wiki-vote for Project Creation started today!
| - How to make sure requirements in the newly created project are taken from CNTT.
| - More discussion in RI-2 Calls to advance progress.
|
RC-2 DeepDive | Bill Mulligan led the session on RC-2 Deep Dive | - Align all efforts to a single outcome and agree on one way of doing it.
| - Currently the framework mixes a general what and why of the tools showing how they are useful testing tools. I do not see the high-level RC principles are listed.
- Scott Steinbrueck to arrange a meeting with RI/RC leads, Taylor Carpenter Gergely Csatari to agree on a single scheme.
|
CNTT/OPNFV Release Sync | |
|
|
|
|
|
|
OPNFV Track | Key Points | Challenges | Next Steps/Action Items |
---|
OPNFV INFRA Work Group Update Trevor Bramwell Sawyer Bergeron | - Need quotes for new machines at UNH - IOL and Oregon
- INFRA is working with various projects to transition to Lab As A Service, rather than Static assignments.
- CI/CD Evolution Options - OPNFV is different from other LFN projects (but needs update?)
- Migration plan includes a Proof of Concept phase
- Lab As A Service review - booking for various LFN projects. Look around at site: labs.lfnetworking.org
- LaaS New Features - PTLs can define complete HW configuration, network configuration, merge configuration
- LaaS Quick booking Improvements
- Plus CNTT-ready! additional requirements for networking: greater uplinks, and additional storage
- Anyone with LFID can use
- New features planned: booking transfers between users, analytics dashboard, Jenkins integration
| Lab folks are seeking HW quotes, but this has stalled (for many reasons that seem to be related to COVID-19). Need to Figure out a way to get quotes before the funding goes away! |
|
Second Session of Joint Topic: OPNFV and CNTT: OPNFV Release Process 2.0 JOINT with CNTT David McBride | - Project Release Plans Template - Each project will describe and document their Artifacts/Deliverables
- OPNFV's project plans have varied in degree of detail
- OPNFV TSC has the responsibility to establish the Release Process
- Requirements Vetting is still a sticking point
- Release requirments are part of OPNFV Release process. Full Stop
- Requirments will come from CNTT, AND Openstack, ETSI NFV, and OPNFV participants.
- There are already LOTS of requirments to Vet that intend to be part of OPNFV's next release.
|
|
|
ODL Track | Key Points | Challenges | Next Steps/Action Items |
Sync ODL Releases with LFN Infra Migrations |
|
|
|
ODL BGPCEP Magensium Retrospective |
|
|
|
ODL Service Automation Framework (SAF) |
|
|
|
ODL Platform Aluminum Updates & Silicon Release Lookahead |
|
|
|
Tungsten Fabric Track | Key Points | Challenges | Next Steps/Action Items |
TF Integration with ONAP |
|
|
|
Making TF Cloud Native |
|
|
|
Move Upstream DPDK for TF |
|
|
|