...
| 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 coverage |
| 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 approach | |
| 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. | |
| docs | All docs are in policy parent | docs in subdirectory in clamp repo | Move to policy parent | |
| UI | Separate "policy gui" repo | ui-react subdirectories in clamp repo | Let's think about it. | We should do this |
| 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 its CSITsthe integration tests within the build (stretch goal) |
Other Considerations
- CLAMP planned improvements (Can we add?)
- Caching policies in CLAMP vs accessing PF database (Mentioned in the demo video)
- DCAE is evolving, how to work towards the K8S based DCAE
...