Project | Link to Topic Page | 1-2 Key Highlights | Take-aways |
---|
ONAP 9 sessions | 2022-06-DD - ONAP: SECCOM retrospectives for log4j (Istanbul Maintenance) and Jakarta releases - LF Networking - LF Networking Confluence | - Lesson Learnt from Log4 Security Alert handled early this year by the ONAP Community
- Review of ONAP Jakarta Security requirements/improvements deliverables:
- 299 recommended package upgrades - 60% already completed
- CII Badging - 5 projects on their way to "Gold"
| - SBOM (“Software Bill of Materials”) can help to identify dependencies early; ONAP Community is taking an action to move forward integrating it as part of our CI/CD pipeline
- ODL (Robert Varga ) is offering some experience about SPDX and SBOM to be reviewed by the ONAP SECCOM
|
| 2022-06-DD - ONAP: SECCOM Kohn release security goals - LF Networking - LF Networking Confluence | - Review of current Global Requirements/Best Practices/Waivers
- Service Mesh POC
- SBOM (also discussed in previous session)
- CII Badging - 5Y Project Review
- Path to remove 'Unmaintained Code'
| - Lots of different wiki pages about ONAP Service Mesh - can we consolidate?
- Call for ONAP project participation to "Container Signing" POC?
- Check Scancode.onap.eu for License dependency
|
ONAP + 5G SBP
| 2022-06-14 - 5G SBP: ORAN SMO Package - Combining multiple open sources into an E2E package - LF Networking - LF Networking Confluence | - Explain how the SMO package was built and how it grows and could become a 5G superblueprint deployment
- Live E2E Flows POC demonstrating a self-contained '5G Super Blueprint' setup that can start and test a 'reference' ORAN SMO package based on ONAP Jakarta release, O-RAN Simulators and more, in alignment with ORAN SC Technical Community
| - Enhance more the package with additional integrations
- Anuket for Infra management, Emco
|
| 2022-06-DD - ONAP: Day1-ConfigManagement for O-RAN components - LF Networking - LF Networking Confluence | - How to handle different conf (DAY1) for multiple cell sites with multiple elements inside ONAP ? ONAP CDS +CU/DU
- Next step: replace CDS-DB by CPS
| |
| 2022-06-DD - ONAP: CNF Orchestration Scenarios - LF Networking - LF Networking Confluence | - Share latest CNF O capabilities available today (Onboarding, Modeling, CBF/PNF Coordination, Scaling on Demand, Upgrades and Migration, etc.), (Public) Cloud Deployment based on K8s
- Use Cases
- Future Steps: Integration with other external k8S orchestrators (Nephio?), Service Assurance (Control Loop), k8s Cluster Homing, ASD model integration and more
| - Map to Promotheus Metrics
- Start d
- iscussions with Nephio
|
| 2022-06-DD - Virtual: General: ONAP EMCO integration and Demo - LF Networking - LF Networking Confluence | - ONAP/EMCO POC Introduction and Demo by leveraging Plug&Play with ONAP SO, EMCO as blackbox, min. ONAP footprint (SO, A&AI)
- Real Demo
|
|
Anuket | Anuket: RA1 OpenStack Architecture- Moselle release and beyond | - Review of RA1 Moselle release
- Status on GSMA NG.133 document (based on RA1)
- Discussion on the choice of OpenStack release for next step
- Agreement on the scope of next release (topics to be developped: acceleration, storage, 5G use cases and deployments with inputs from OpenInfra)
| - Preparation of the scope of next release (Nile)
- The last OpenInfra summit in Berlin can bring good inputs for RA1
|
| Virtual: Anuket: Scope of Anuket | - Scope of Anuket specifications was extended since the beginning of CNTT, and that is okay
- Anuket defines both requirements and recommendations from which the recommendations are not mandatory
- Scope of the specifications is related to all the specs, therefore should be discussed in TSC
- We do not have an agreement on how implementable requirements in RM should be
- We do not have a documented scope of Anuket
- The meeting had too low participation to get any conclusions
- We will continue in the TSC
| - Discussion about the change of the scope of the project and the control of this change
- Discussion will continue in the Anuket TSC
|
| Anuket: Leftovers of the merger are still with us | - We still have lots of artifacts with OPNFV and CNTT what confuses Anuket's end users
- We collected the things what we would need to update and proposed a next step to change them
| - Anuket is working on the usage of its name in the artifacts and even would pay in beers for github.com/anuket
|
EMCO |
|
|
|
ODL |
|
|
|
FD.io |
|
|
|
|
|
|
|