...
| No. | 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.103 | |||||||||||||||||||
| 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)104 | |||||||||||||||||||
| 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. |
...
| Area | Policy Framework | CLAMP | Recommendation | Comment | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Module Structure | Maven multi module project | Single module project, builds everything | Multi Module | Price to pay is that we could have some issues with getting integration coverage202 | ||||||||||
| Docker Build | Common approach for current components and repos using a "packages" maven module | Part of Single module | Add TOSCA components to the Docker build, also see if or how we use the Policy Framework approach203 | |||||||||||
| Integration Test | CSITs done per component, separate to build | Comprehensive Integration test, part of build | The ONAP recommendation is that Integration tests should be a part of the build. | |||||||||||
| 204No Jira | docs | All docs are in policy parent | docs in subdirectory in clamp repo | Move to policy parent205 | |||||||||||
| UI | Separate "policy gui" repo | ui-react subdirectories in clamp repo | Let's think about it. | We should do this206 | ||||||||||
| Simulators | DMaaP Simulator A&AI, SDNC, CDS, APPC, and others | Emulator for CLAMP external interfaces, TOSCA POC we have a participant simulator | CLAMP should use the real Policy components in the integration tests within the build (stretch goal) |
...