...
| Drawio | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Consider Features A, B and C in the diagram above.
...
All three features are realised as Automation Compositions, as shown in the diagram below.
| Drawio | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The ability to deploy features in a scalable, flexible and loosely coupled microservice architecture is of course a major step forward from layered architectures of the past. However, managing at "Feature" level in such architectures does present challenges. For example, to manage the three running instances of Features A to C above, 9 separate elements must be kept track of. There is nothing in the deployed system to sat what element is related to what other element, and what element are working together to realise a feature.
Automation Composition Management (ACM) is a framework that supports Life Cycle Management of Automation Compositions. It supports deployment, monitoring, update and removal of Automation Compositions en-bloc, allowing users to manage their features, services, and capabilities as single logical units.
Introduction
The idea of using compositions to automate network management has been the subject of much research in the Network Management research community, see this paper for some background. However, it is only with the advent of ONAP that we have a platform that supports management of those compositions. Before ONAP, Automation Compositions have been implemented by hard-coding elements together and hard coding logic into elements.
...
| Drawio | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The diagram above shows the architecture of ACM in ONAP.
...
| Drawio | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Note that the system dialogues for run time capabilities are described in detail on the System Level Dialogues page.
Automation Composition Instance States
...
| Drawio | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Drawio | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Following the ONAP Reference Architecture, the architecture has a Design Time part and a Runtime part.
...
| Drawio | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Drawio | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
At runtime, interaction between ONAP platform services and application microservices are relatively unconstrained, so interactions between Automation Composition Element instances for a given Automation Composition Instance remain unconstrained. A proposal to support access-controlled access to and between ONAP services will improve this. This can be complemented by intercepting and controlling services accesses between Automation Composition Elements for Automation Composition Instances for some/all Automation Composition types.
...
| Drawio | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The APIs and Protocols used by ACM for Automation Compositions are described on the pages below:
- System Level Dialogues
- Defining Automation Compositions in TOSCA for ACM
- REST APIs for ACM Automation Compositions
- The ACM Automation Composition Participant Protocol
6 Design and Implementation
The design and implementation of ACM is described for each executable entity on the pages below: