...
| 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 | Technical Community Coordination – Generic Network Management
| ||||||||||||||
| 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 | |||||||||||||||
| xGVela | |||||||||||||||
| Tungsten Fabric |
...