...
Current Overall Architecture
In ONAP, Holmes is deployed as an analytics application of DCAE. So basically, Holmes is spun up and configured through DCAE. During the runtime, Holmes has to interact with the following components:
- CLAMP - CLAMP is the place in which the correlation rules are designed. Ideally, all the Holmes rules are designed in CLAMP cockpit and then deployed into DCAE.
- MSB - MSB is a mandatory dependency of Holmes. All HTTP requests are transferred by MSB from Holmes to other components, such as communications with DMaaP and AAI. Even inside Holmes, the sub-modules call each other's API via MSB.
- AAI - Holmes uses the resource information provided by AAI as a clue for alarm correlation. Only alarms with topologically correlated resources are considered to have some kind of relationship with each other.
- DMaaP
- DCAE-PG
- DCAE-CBS
Planned Internal Architecture of Holmes
