...
| Technology | Policy Framework | CLAMP | Recommendation | Comment | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Lifecycle Management | Policy Common | Spring Framework | Spring for new (All participants including DCAE/K8S)
Migrate if doing something else in existing PF code in master (Spring in policy-common?) | |||||||||
| REST | Policy Common, using JAX-RS annotations | Camel | Camel the Commissining/Instantiation Spring for Supervision/Monitoring Use Camel where we need flexibility. | |||||||||
| Parameter Handling | Built in parameter validation in policy common | Spring properties | Let's investigate if the policy-common parameter handling can be got to work in Spring (javax validation) | |||||||||
| TOSCA Handling | Policy Models, integrated serialization and persistence for most TOSCA entities | CLAMP TOSCA handling (more info) | Separate study ongoing in the Policy Framework on this We should try and get this framework on Spring, which would enable further merging | |||||||||
| Persistence | Policy Models using JPA/JDBC/Eclipselink/MariaDB | Spring using JPA/JDBC/Hibernate/MariaDB | To be investigated. Should also consider using the policy DB to store TOSCA rather than caching it in a separate CLAMP-specific DB | |||||||||
| UI | None (Angular in TOSCA PoC, APEX policy editor) | React | React | Angular (Security issues raised), new version did not solve the issues. React is flexible and easier to understand, we moved in an earlier release from Angular to React. Used Jsoneditor (library), easier with React. Develop the Monitoring GUI as a new tab in the CLAMP UI. |
...