Page Comparison

...

The following diagram depicts Oslo ONAP Component Architecture:

ONAP Core Components

The remaining ONAP components/projects are now ONAP Core components:

Portal-NG : is a GUI platform provides the ability to integrate different ONAP GUIs
Use-Case UI (UUI) : provides the capability to instantiate the blueprint Use Cases and visualize the state. It also provides intent-based network management, leveraging genAI/ML
SDC : provides a design time tool for common model/catalog onboarding design and distribution
Policy Framework : provides the ability for the creation and management of policies. Its CLAMP (Closed Loop Automation Management Platform) provides the run-time control loop management
SO : Service Orchestrator and its modular sub-components provide the service orchestration, network service, network slicing and VFN/CNF/PNF in the ONAP architecture
AAI : provides real-time views of Resources and Services and their relationships. It also provides services to register externally used services
CPS : provides storage for real-time configuration and operational parameters
DCAE : provides the capability to collect events, and host analytics applications (supporting VES events)
Multi-VIM/Cloud : provides mediation capabilities to connect to different infrastructure providers (including K8s plugin for CNF)
CDS : is a framework to automate resource resolution for instantiation and configuration (Day 0, Day 1, Day 2)
CCSDK : provides a common set of reusable code that can be used across multiple controllers (for building/plug-in controller personas)
SDNC

SDC

...

: provides a network controller capability for establishing network connections and configuring VNFs/CNFs. It is based on CCSDK

Security Framework : provides security capabilities for external and inter-component secure communications, authentication and authorization
Logging Framework (PoC) : provides general-purpose logging collection/aggregation/persistence/visualization, by leveraging open-source log collector, aggregator, database and visualizer (e.g., FluentBit, FluentD, ElasticSearch, Kibana)

Infrastructure Service supports the foundation of ONAP applications to run and includes computing, networking, storage, security and other essential resources. In ONAP, Service Mesh is placed in the Infrastructure Service layer for secured ONAP application communications
Service Mesh is an infrastructure layer to handle communication between microservices in a distributed system. In ONAP, Istio Service Mesh with Envoy proxies as the sidecars manages all incoming and outgoing network/application traffic for ONAP applications with mTLS, authentication and authorization

x