You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 27 Next »

 

TrackKey PointsChallengesAction Items
Cross-Community


ONAP

Session on E2E Network Slicing - Honolulu release Scope and Future Roadmap (Presenters: LIN MENGSwaminathan SeetharamanMilind 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:

  • Enhancements in CSMF and NSMF for E2E Network Slice allocation, standards alignment, operator intervention, etc.
  • RAN, Core and Transport Slicing related aspects, including alignment with O-RAN (RAN) and ETSI ZSM & IETF (Transport)
  • KPI Monitoring, Closed Loop Control & Intelligent Slicing

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 Orchestration of Free 5G Core CNFs using ONAP4K8s (EMCO)



CNTT/OPNFV

CNTT K8S SURVEY

OPNFV TSC Meeting

  • Jerma M2 scheduled for Oct 20
    •  Functional freeze - Readiness Review
      • Document significant accomplishments
      • Release Management Tasks sent to for M2
  • Goal for Documentation outline in Jerma Release -Agreed
  • Revisions to RELREQ-13 on Storage testing requirements and clarifications - Agreed
  • OPNFV Input to LFN Governing Board meeting on Project's Priority Activities - Agreed





XGVela Project Update & Discussion




EUAG and SDN

EUAG and Software Defined Networking by Ahmed El Sawaf



 

TrackKey PointsChallengesAction Items
Cross-Community


ONAP

ONAP Requirements Subcommittee - new requirements for Honolulu

#1 ONAP ETSI-Alignment (SOL004, SOL005 v3.3.1)

#2 Slice Management

#3 Smart Operator Intent -based Network & 5G Slicing Support



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

  • ETSI
    • ETSI NFV update – Thinh Nguyenphu
    • ONAP Conformance to ETSI – Byung-Woo Jun
  • 3GPP
    • RAN Slicing: 5G NR Resource Configuration Management – Kamel Idir
  • TM Forum
    • Digital Transformation World – Magnus Buhrgard
    • Catalysts, rapid-fire proof-of-concept projects – Magnus Buhrgard



 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 OliveiraByung-Woo Jun

REQ-341: Lukasz RajewskiSeshu Kumar Mudiganti

CNTT/OPNFV


xGVela


Tungsten Fabric


 

TrackKey PointsChallengesAction Items
Cross-Community


ONAP


CNTT/OPNFV


xGVela


OpenDaylight



  • No labels