Page Status:
...
Reviewed
Component Status: INCUBATION
Last Reviewed on:
Certified by:
1. High Level Component Definition and Architectural Relationships
| Drawio | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
2. Component API definitions
...
| Consumed Interface Name | Consumed Interface Description | Version(s) | API Spec (Swagger) |
| POE-4 | To send the closed control loop events to policy to trigger downstream actions. | - | Closed Loop Event Data Structure |
| DMaaP-2 | To retrieve VES events from DMaaP. | 4.0.0 | swagger.json |
| DMaaP-3 | To send closed control loop events to DMaaP. | ||
| AAIE-1 | To query resource information from A&AI. | v19 |
3. Component Description:
...
https://docs.onap.org/projects/onap-holmes-rule-management/en/latest/platform/architecture.html
4
...
. Dependencies on other ONAP Components
- AAF - the HTTPS certificates are provided by AAF.
- AAI - Holmes needs the resource information to perform alarm analysis. Without AAI, the capability of Holmes will be partially unavailable (rules depending on resource information will lose the ability to analyze alarms).
- DMaaP - The main input of Holmes. For now, if DMaaP stops work, Holmes could get VES data from nowhere.
- OOM - OOM is responsible for the deployment of Holmes. Without OOM, Holmes could also run in a standalone mode, but all OOM/Helm-related functionalities will be lost.
5. Component Deployment Architecture
...
https://docs.onap.org/projects/onap-holmes-rule-management/en/latest/release-notes.html
...
- More documents about API : Holmes API Documentation - Honolulu (As the APIs are the same as in Honolulu, so we pasted the link of the Honolulu doc here to avoid having another identical page.)