Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

#4 5G OOF SON use case

Image Added



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

View file
nameTCC Generic Network Management.pdf
height250

View file
nameLFNTECH_ETSI_NFV_ONAP_Oct2020_final1.pdf
height250



 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


  •  Consider portability between ETSI & ONAP for CNF
CNTT/OPNFV


xGVela


Tungsten Fabric


...