Versions Compared

Old Version 48

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Hector Anapan-Lavalle

Saved on

Key

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

...

In effect, each Controller instance supports a form of orchestration to manage the operations that are within its scope. This orchestration is a lower-level of orchestration than the orchestration done by the MSO. 

OpenECOMP ONAP uses different Controller types to manage Resources in the execution environment, corresponding to their assigned controlled domain:

...

The SDNC network controller in FIgure Figure 1 illustrates the core OpenDaylight framework that supports a model driven service abstraction layer (MD-SAL),  api handlers,  operational and configuration trees, and an adapter framework for integrating with controlled devices, virtual functions,  and cloud infrastructure.  Within this framework the OpenECOMP ONAP Service Logic Interpreter (SLI) addition provides an extensible scripting language for expressing service logic through a Direct Directed Graph (DG)  builder based on Node-Red.   The SLI is extended by adding Java classes that can be called as a node in a DG to support frequent complex operations.

...

Note that not all changes in network or service behavior are the result of orchestration.  Policies and rules (in the Policy subsystem) inform the controller such that the Controller can enable service behavior changes.

OpenECOMP ONAP includes a generic Application Controller (APPC, sometimes formerly called APP-C) that receives commands from OpenECOMP ONAP components, such as MSO, DCAE, or the Portal, and uses these commands to manage the life cycle of Services, Resources (virtual applications and Virtual Network Functions), and their components. The Application Controller is based on the same OpenDaylight Framework with SLI additions.   The Application Controller project provides SLI node types, adapters, and API handling logic required for the life cycle management of complex, distributed services composed of many VNF types and instances. See the OpenECOMP

Documentation:

...

NOTE: For instructions on how to build and run an ONAP Component (APP-C is taken as an example) locally, please refer to this documentation.