STATUS: Under Construction
SDN-C / App-C:
1 High Level Component Definition and Architecteral Relationships
<< Short description
2. SDN-C API definitions
Controller provides the following interfaces:
| Interface Name | Interface Definition | Interface Capabilities |
|---|---|---|
| CONE-1 | OSS Interface | An interface to request for Lifecycle management operations on network resources |
| CONE-2 | Operations Interface | An interface to request for Lifecycle management operations on network resources |
| CONE-3 | Service Order Interface | An interface to request for Configuration and Lifecycle management operations on network resources |
| CONE-4 | Policy Interface | An interface to support LCM requests such as Restart, Rebuild, Migrate, Evacuate operations on network resources |
| CONE-5 | Resource Rest API | An interface for configuration and Lifecycle management of network resources using REST protocol |
| CONE-6 | Resource Chef API | An interface for configuration and Lifecycle management of network resources using Chef protocol |
| CONE-7 | Resource NetConf API | An interface for configuration and Lifecycle management of network resources using NetConf protocol |
| CONE-8 | Resource Ansible API | An interface for configuration and Lifecycle management of network resources using Ansible protocol |
Controller consumes the following interfaces:
| Interface Name | Interface Definition | Interface Capabilities |
|---|---|---|
| SDCE-6 | SDC Interface | An interface to receive resource Templates from SDC design catalog |
| CDSE-1 | CDS Interface | An interface to receive resource blueprint from CDS |
| AAIE-1 | Inventory Service Interface | An interface to create, update, query, and delete resource information and relationships |
| POE-2a | PDP Query API | Policy Decision Point query for IP address |
Note: xxxI interface is a internal interface. xxxxE interface is a external interface
The current API documents can be found at:
link to documentation
Controller consumes the following Interfaces:
3. Component Description:
A more detailed figure and description of the component.
<< For later inclusion >>
4. known system limitations
Runtime: None
Clamp data redundancy is dependant on kubernetes and the persisten volume.
Clamp appliation redundancy HA reliease on kubernetes
5. Used Models
Clamp uses the following models:
- please fill in (and references if possible)
- << include model that you recieve from SDC >>
- << Include the model that you configure in the policy >>
6. System Deployment Architecture
Clamp consists of 4 containers:
- CLAMP container
- MariaDB container
- Kibana ontainer
- E_Search ontainer
- LogStash container
7. New Release Capabilities
<<>>
8. 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