STATUS: In Progress
1 High Level Component Definition and Architectural Relationships
..
2. Template Component API definitions
DCAE Component provides the following interfaces:
Interface Name | Interface Definition | Interface Capabilities | Version | Status | Consumed Models |
---|---|---|---|---|---|
DCAEE-1 | VES Collector | An interface to share FM/PM data for VNF FCAPS from the VNFs via the EMS Driver to VES Collector | REST | production | |
DCAEE-2 | Inventory API |
| REST | production | |
DCAEE-3 | Deployment Handler | High-level API for deploying/undeploying composed DCAE services | REST | production | |
POE-2 | Policy Handler | Fetched and updates policies from the Policy Framework | REST | production |
DCAE Component consumes the following Interfaces:
Interface Name | Purpose Reason For Use | Version(s) |
---|---|---|
POE-1 | Sends PDP requests asynchronously via DMaaP | |
3. Component Description:
A more detailed figure and description of the component.
<< link to project-specific description elsewhere >>
4. known system limitations
Architectural Technical Debt
Runtime: None
Clamp data redundancy is dependant on kubernetes and the persisten volume.
Clamp appliation redundancy HA reliease on kubernetes
5. System Deployment Architecture
FFS
6. New Release Capabilities
<< list the new capabilities that were introduced in this release, or a hot-link to the key features. New sub-chapter per release, as per a release notes document >>
7. References
- CLAMP Overview & User Guide: https://onap.readthedocs.io/en/latest/submodules/clamp.git/docs/index.html
- CLAMP internal interfaces: https://onap.readthedocs.io/en/latest/_downloads/d3c9f924c6586fe411d40a05ad9b1bb7/swagger.pdf