Versions Compared

Old Version 23

changes.mady.by.user Zu Qiang

Saved on

compared with

New Version 24

changes.mady.by.user Fernando Oliveira

Saved on

Key

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

...

RequirementPresenter(s)/Contact(s)
Onboard ETSI SOL004  compliant VNF packages (ETSI Package Management)Fernando Oliveira
Onboard ETSI SOL004  compliant VNF packages (ETSI Package Management)Fernando Oliveira
Design ETSI SOL007  compliant Network Service Descriptor packages  (ETSI Package Management)Fernando Oliveira
Support for Nested/Hierarchical ETSI SOL001 v2.7.1 Network Service DescriptorFernando Oliveira
Support for ETSI SOL003 v2.7.1 Or-Vnfm Interface from ONAP to external VNF Manager(s)Fernando Oliveira
E2E Network Slicing 

Lin Meng (menglinyjy@chinamobile.com), Swaminathan S (swaminathan.seetharaman@wipro.com)

Support xNF Software Upgrade in association to schema updatesZu Qiang
ONAP components support for native CNAs artifacts and cloud native service models distribution and managementAlessandro
Support for a declarative approach in the SO engineAlessandro
Support for hitless A&AI schema modification for new services/CNFs (e.g. no A&AI pods restart)Alessandro
Support for A&AI and k8s alignment about instance details that need to be kept in A&AIAlessandro
Support for Test Topology Auto Design （NFV Testing Automatic Platform）
Support for Test Environment Auto Deploy（NFV Testing Automatic Platform）
Support for Test Task Auto Execution （NFV Testing Automatic Platform）
Support for Test Result Auto Analysis & Certification （NFV Testing Automatic Platform）
OOF-SON: 5G Self-Organizing Network (SON) using ONAP Optimization Framework (OOF)Shankaranayaranan N K (shankar@research.att.com), Swaminathan S (swaminathan.seetharaman@wipro.com)

Run Time Configuration Database / Data Persistency Service Project

Ben Cheung (ben.cheung@nokia.com)

...

ONAP components support for native CNAs artifacts and cloud native service models distribution and management

Executive Summary – Today new emerging infrastructures based on kubernetes are becoming very popular. ONAP components shall support CNAs artifacts and cloud native service models and relevant distribution/management. Given the fact that K8s has its own orchestration capabilities that partially overlap with ONAP capabilities, it is expected that ONAP developments will focuse only on aspects not covered by K8s. The envisioned scenario is based on both CNFs (deployed on kubernetes infrastructure) and PNFs.

Business Impact – Today, many ONAP components (e.g. SDC, SO and AAI) are not able to manage CNA artifact/service models in a native way that bring to unnecessary complexity in service orchestration. It is expected that ONAP modeling and LCM support services composed of PNFs and CNFs to be future proof. ONAP developments will focuse only on LCM aspects not covered by K8s (e.g. service orchestration rather than resource orchestration.

Business Markets - All operators and service providers that are using ONAP for service and network function Life Cycle Management

...