A Controller manages the state of a single Resource (Application, Infrastructure, or Network). It participates in executes the Resource's instantiation and configuration and instantiation, and is the primary player in ongoing management, e.g. control loop actions, Resource migration/scaling, and managementscaling. All of these actions involve executing workflows (recipes) obtained from ASDC. In addition, the Controller reports the status of each workflow execution to both A&AI and MSO.
In effect, each Controller instance supports a form of orchestration to manage operations within its scope. This low-level orchestration is done outside the MSO.
The MSO is responsible for ensuring that the Controller successfully completes its Resource configuration as defined by the recipe.
OpenECOMP uses three distinct Controller types to manage Resources in the execution environment, corresponding to their assigned controlled domain:
- cloud computing resources (Infrastructure Controller, typically within the cloud layer)
- network configuration (Network Controller)
- application (Application Controller).
Infrastructure Controllers
Network Controllers
...