...
Architecturally, the Policy Framework and CLAMP are complimentary as separate systems. The Policy Framework is part of control loops, and CLAMP is a control loop management system.
Technologies
| Technology | Policy Framework | CLAMP | Recommendation | Comment |
|---|---|---|---|---|
| Lifecycle Management | Policy Common | Spring Framework | ||
| REST | Policy Common, using JAX-RS annotations | Camel | ||
| Parameter Handling | Built in parameter validation in policy common | Spring properties | ||
| TOSCA Handling | Policy Models, integrated serialization and persistence for most TOSCA entities | CLAMP TOSCA handling (more info) | ||
| Persistence | Policy Models using JPA/JDBC/Eclipselink/MariaDB | Spring using JPA/JDBC/Hibernate/MariaDB | ||
| UI | None (Angular in TOSCA PoC, APEX policy editor) | React |
Code Structure, Build, and Test
| Area | Policy Framework | CLAMP | Recommendation | Comment |
|---|---|---|---|---|
| Module Structure | Maven multi module project | Single module project, builds everything | ||
| Docker Build | Common approach for all components and repos using a "packages" maven module | Part of Single module | ||
| Integration Test | CSITs done per component | Integration test part of build |
Use of Policy/Common or Spring Framework for component LCM
TOSCA Handling
Use of Angular or React for GUIs
Use of Camel or direct REST coding for operations
Introduction of executable components for Participants
Structuring of policy/clamp for multiple components
...
| docs | All docs are in policy parent | docs in subdirectory in clamp repo | ||
| UI | Separate policy gui repo | ui-react subdirectories in clamp repo | ||
| Simulators | DMaaP Simulator and others | Emulator for CLAMP external interfaces |