...
Track | Key Points | Challenges | Action Items | ||||||
---|---|---|---|---|---|---|---|---|---|
Cross-Community | Good discussions on how to build a trusting community. Targeted at the CNTT/OPNFV Meld activities, but applies across the LFN and Open Source communities. | ||||||||
ONAP | Session on E2E Network Slicing - Honolulu release Scope and Future Roadmap (Presenters: LIN MENG, Swaminathan Seetharaman, Milind Jalwadi,Henry Yu) This session covered what functionality has been realized in Guilin, and the proposal for Honolulu and beyond for each of the following tracks of the E2E Network Slicing use case:
Feedback from the ONAP community was sought on topics such as Network Slicing in roaming scenarios (i.e., true e2e slicing), interaction of slice management & orchestration functions (NxMF) with the Core NFs such as NSSF and NWDAF, collaboration with C&PS project, etc. Presentation Slides are available here. | ||||||||
ONAP Demo of O-RAN-SC O1 interface simulator configuration via CDS
| |||||||||
ONAP Orchestration of Free 5G Core CNFs using ONAP4K8s (EMCO)
| |||||||||
CNTT/OPNFV | CNTT K8S SURVEY
OPNFV TSC Meeting
| ||||||||
XGVela Project Update & Discussion | |||||||||
EUAG and SDN | EUAG and Software Defined Networking by Ahmed El Sawaf
|
...
Track | Key Points | Challenges | Action Items | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cross-Community | Multiple engaging discussions on EUAG
| ||||||||||||||
ONAP | ONAP Requirements Subcommittee - new requirements for Honolulu #1 ONAP ETSI-Alignment (SOL004, SOL005 v3.3.1) #2 Slice ManagementE2E Network Slicing use case #3 Smart Operator Intent -based Network & 5G Slicing Support #4 5G OOF SON use case | #2 E2E Network Slicing use case Comment: O-RAN alignment and collaboration seems more pragmatic for the upcoming releases, than the other topics such as slicing in roaming scenarios, etc. Comment: Clarify what exactly is meant by O-RAN alignment to avoid misinterpretation. | |||||||||||||
ONAP | ONAP Impact of the current ONAP release- and branching strategy on documentation Discussed the possible solutions for branching documentation and project / Cross release issues. | Several projects have deprecated repos Documentation update tracking should be part of release process should documentation be in a single repo ? | |||||||||||||
ONAP | ONAP Security Subcommittee Kanban Review Helm, OS, Python/java updates Update Vulnerable direct depencies (tracking through wiki) M1 (TBD) commit resources M4 (TBD) complete upgrades Guilin seccom retrospective : lots of improvements in this release Reviewed H release priorities |
| |||||||||||||
ONAP |
| ||||||||||||||
ONAP | ONAP Honolulu - CNF Task Force Requirements Presentation of REQ-334 (ETSI Alignment-CNF Support) - SOL004, SOL005 v3.3.1 REQ-341 (CNF Orchestrator) | Call for Developers for the Honolulu Release If any interest then please contact REQ-334: Fernando Oliveira , Byung-Woo Jun REQ-341: Lukasz Rajewski , Seshu Kumar Mudiganti
| |||||||||||||
ONAP | ONAP: Hands-on session on ONAP Optimization Framework (OOF) This session provided an overview of OOF, its modular architecture, capabilities and ease of reuse w.r.to onboarding a new use case or requirement that needs some sort of optimization functionality. It also described the typical realization steps to follow for any use case or requirement needing optimization (provided by OOF). It was followed by a guided walk-through with an example of how the E2E Network Slicing use case realized the optimization needs easily through a lot of reuse of existing functionality with some enhancements. Comment: Policy team highly appreciated the work done by OOF team for effective usage of the new Policy framework. Query: A query on how subnet instance's resource occupancy levels and capability of an existing instance to cater to a new request are considered by OOF. Response: This isn't yet considered by OOF, however, it is proposed to be realized in Honolulu release, with OOF getting the required info on available resources and capacity through an "inventory provider" which for example could be AAI or DCAE, which leverages existing OOF capabilities to a large extent. Presentation slides are available here. | ||||||||||||||
CNTT/OPNFV | Field trial by Orange reviewed Next OVP revision documentation update planning Very engaged conversation on Telemetry and Observability HA requirements got into the obligation of defining the test approach vs. implementation. ODIM Project gave an overview of the project, with the CNTT RM team describing how the Hardware Interface Manager (HIM) concept can be addressed by ODIM. Several key areas were identified for collaboration. The ODIM team will continue the dialog in RM meetings and RA meetings afterwards, at the appropriate time. | ||||||||||||||
CNTT | this session presented an architecture for the Telemetry/Observability of VNFs and Cloud Infrastructure (NFVI) to achieve full automation leading to zero touch operation. This architecture is based on a central telemetry data BUS on which are connected Providers Consumers and Subscribers of telemetry data. | 2020-10-14 - CNTT - Telemetry/Observability architecture - a path to full automation | |||||||||||||
xGVela | |||||||||||||||
Tungsten Fabric |
| ||||||||||||||
Tungsten Fabric |
| ||||||||||||||
Tungsten Fabric | Prabhjot Singh Sethi we can consider looking forward to phase out kernel module vrouter, will carry further discussions around this in community
| ||||||||||||||
Tungsten Fabric | consider further sessions and discussion around debuggability in community calls
| ||||||||||||||
Tungsten Fabric |
Track | Key Points | Challenges | Action Items | ||||||
---|---|---|---|---|---|---|---|---|---|
Cross-Community | PLEASE FILL OUT THE EVENT SURVEY: https://www.surveymonkey.com/r/LFNTech PLEASE REGISTER IF YOU HAVE NOT: https://www.cvent.com/d/k7q1mh/4W?ct=50221cf5-5496-4c34-9ec0-3b52b1bf1204&_ga=2.21073848.2005020082.1597615801-222812119.1571605958&_gac=1.250209970.1597348253.EAIaIQobChMIuJ2l9vmY6wIVEh-tBh3_KApSEAAYASAAEgLU1fD_BwE | ||||||||
ONAP |
All the details (slides, postman collection etc) are available here - https://wiki.onap.org/display/DW/2020-10-15+October+LFN+Virtual+Technical+Meetings | ||||||||
ONAP | ETSI ZSM - ONAP architecture collaboration
|
Otherwise the TN NSSMF is part of the Guilin Release
| |||||||
ONAP | ONAP: O-RAN ↔ ONAP Collaboration and Alignment Presentation slides are available here. ONAP 5G & PNF use cases aligned with O-RAN & 3GPP |
| |||||||
ONAP | |||||||||
ONAP | |||||||||
ONAP |
| ||||||||
ONAP | CONFIGURATION PERSISTENCE SERVICE
| ||||||||
ONAP | ONAP: 5G OOF SON use case - Honolulu release requirements, dependencies and roadmap Presentation slides are available here. | ||||||||
ONAP | What's New in ONAP Frankfurt
| ||||||||
CNTT/OPNFV | Edge Workstream
OVP 2.0 OPNFV Investigates CNTT Telemetry Req.
OPNFV Kuberef project review -
| ||||||||
xGVela | |||||||||
OpenDaylight | ODL-Micro Aluminium updates |