...
- The long term aim is to integrate CLAMP into the Policy Framework and to align the structure and technologies of CLAMP and the Policy Framework in general
- Is the Policy Framework structure correct?
- Should the Policy Framework shift to a framework?
- Module structure of Policy, in SDC an integration test is not possible? Integration test in SDC is not feasible
- In CLAMP, everything is in one module so integration test is done as part of the build
- Problem with Jacoco, coverage is taken using XML rather than a binary, so currently we can't report the coverage from the integration tests, by having a single module, we can get the coverage out of the integration test.
- We should have a picture of what the long term vision for CLAMP in the Policy Framework
- How the TOSCA based Control Loop features are implemented should be in line with this long term vision
...
| Technology | Policy Framework | CLAMP | Recommendation | Comment |
|---|---|---|---|---|
| Lifecycle Management | Policy Common | Spring Framework | Spring for new (participant) Migrate if doing something else (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 | |
| Persistence | Policy Models using JPA/JDBC/Eclipselink/MariaDB | Spring using JPA/JDBC/Hibernate/MariaDB | To be investigated | |
| 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. |
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 current components and repos using a "packages" maven module | Part of Single module | ||
| Integration Test | CSITs done per component | Comprehensive Integration test, part of build | ||
| docs | All docs are in policy parent | docs in subdirectory in clamp repo | ||
| UI | Separate "policy gui" repo | ui-react subdirectories in clamp repo | Take the easiest approach for now | |
| Simulators | DMaaP Simulator and others | Emulator for CLAMP external interfaces |
...
- Metadata and generic handling of definitions and instances of TOSCA control loop models (in policy models)
- Monitoring and supervision of instances of control loops
- Be able to handle arbitrary control loops on the fly (Arbitrary participants, maybe not DCAE or Policy Framework or ONAP controllers)
- Be able to parameterize the TOSCA directly (irrespective of the participant type)
- Participants (Intermediary, simulator, DCAE, Policy, and K8S) as separate executing components
Meeting notes
- As complexity increases we ill need to move to some sort of multi maven project whilst preserving the power of the current approach.