Orchestration can be viewed as the definition and execution of workflows or processes to manage the completion of a task. In OpenECOMP, orchestration automates the activities, tasks, rules and policies needed for on-demand creation, modification, or removal of network, application or infrastructure services and resources. The Master Service Orchestrator (MSO) manages orchestration at the top level and facilitates additional orchestration that takes place within underlying controllers. It also marshals data between the various controllers so that they have all of the process steps and components needed to complete the execution of a task or service.
The MSO subsystem runs autonomously within OpenECOMP. In general, Orchestration can be viewed as the definition and execution of workflows or processes to manage the completion of a task. The ability to graphically design and modify a workflow process is the key differentiator between an orchestrated process and a standard compiled set of procedural code. Orchestration provides adaptability and improved time-to-market due to the ease of definition and change without the need for a development engagement. As such, it is a primary driver of flexibility in the architecture. Interoperating with Policy, the combination provides a basis for the definition of a flexible process that can be . OpenECOMP's combination of orchestration and policies can be used to create flexible processes that are guided by business and technical policies and driven by process designers.
****
Orchestration Orchestration exists throughout the D2 architecture and should not be limited to the constraints implied by the term “workflow” as it typically implies some degree of human intervention. Orchestration in D2 will not involve human intervention/decision/ guidance in the vast majority of cases. The human involvement in orchestration is typically performed up front in the design process although there may be processes that will require intervention or alternate action such as exception or fallout processing.To support the large number of Orchestration requests, the orchestration engine will be exposed as a reusable service. With this approach, any component of the architecture can execute process recipes. Orchestration Services will be capable of consuming a process recipe and executing against it to completion. The Service model maintains consistency and reusability across all orchestration activities and ensures consistent methods, structure and version of the workflow execution environment.
...