Brief Project Overview (brief as it should be known)
New component capabilities for Dublin, i.e. the functional enhancements.
New or modified interfaces
There's no interface change in R4. Besides, Holmes is basically a consumer rather than a provider of APIs. In other words, all defined APIs for Holmes are intended for internal use. The interactions between Holmes and other ONAP components are implemented through DMaaP.
For reference, all Holmes APIs are defined here.
Interface naming
The pattern of API names of Holmes is like <protocol>://<host>:<port>/api/<module-name>/<version>/<func> .
For example, for health check, the APIs are like:
- api/holmes-rule-mgmt/v1/healthcheck
- api/holmes-engine-mgmt/v1/healthcheck
For rule related operations, the APIs are like:
- api/holmes-rule-mgmt/v1/rule
- api/holmes-engine-mgmt/v1/rule
In addition, we use method PUT/POST/DELETE/GET to distinguish different behaviors for the APIs that share the same name.
Reference to the interfaces.
Holmes APIs for R4 are defined here.
What are the system limits?
Involved use cases, architectural capabilities or functional requirements.
- VOLTE
- CCVPN
Listing of new or impacted models used by the project (for information only).
None.