Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Note that VES needs to be added for correctness. Small updates projects/functions/components

...

This section aims to present an end-to-end use case where the 8 LFN projects work in harmony to deliver a "service" that includes VNFs, connectivity and analytics-powered assurance as shown in the following picture:

Picture needs an update: VES - VNF Event Stream - from VNF directly to ONAP for VNF feedback loop

 


In this example, 2 VNFs (for the sake of simplicity, provided by the same vendor) must be deployed on top of an NFVI (e.g., OpenStack), be interconnected and provided with external connectivity to the Internet. Moreover, the VNFs require network acceleration and the whole service must be assured using Analytics driven closed loop operations.

...

At runtime, ONAP orchestrates the deployment of the whole service either through ONAP internal projects functions/components or leveraging the capability to interwork with 3rd party projectscomponents.

In particular, ONAP Service Orchestrator (ONAP SO) instructs the underlying ONAP projects functions in order to deploy all of the elements that compose the end-to-end service.

...