Versions Compared

Old Version 3

changes.mady.by.user Byung-Woo Jun

Saved on

compared with

New Version Current

changes.mady.by.user Byung-Woo Jun

Saved on

Key

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

Mission Statements

Target Goals

  • More component/sub-component modularity and independence
  • Component interface and behavior normalization / standardization
  • Extensible, customizable and substitutional component functions and mechanisms
  • Well-balanced common/platform services vs. autonomous services
  • Pick & choose and Aggregation of functions
  • Unified and Platform-level security and logging across ONAP and SP OAM & Network Resource domains
  • Separation of non-functional requirements from the components

New architecture aims to facilitate ONAP adaptation and extensibility for Service Providers / DevOps

Architecture Diagram

<diagram here>

ONAP Security 

OOM team is working on ONAP Security and Logging. ONAP ARCCOM will define additional architecture guidelines (Byung plans to lead this)

  • Unified and open-source-based security at the platform level, allowing configuration, extensibility and multi-tenancy (user-, operation- and resource-level)
  • Open-source-based logging framework, which separates Log generation from Log collection/Aggregation/Persistence/Visualization; Network Function and Infrastructure logging will be defined

ONAP Logging Framework

more to define..This describes ONAP Streamlining - The Process. For more details, see ONAP Streamlining - The Process (Link) .