...
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:
...
...
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, 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 ONAP Application Controller User Guide and the APPC API page.