Versions Compared

Old Version 17

changes.mady.by.user Liam Fallon

Saved on

compared with

New Version Current

changes.mady.by.user Liam Fallon

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Lifecycle ManagementRESTTOSCA Handling
No.TechnologyPolicy FrameworkCLAMPRecommendationComment101

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-3209

Policy CommonSpring Framework

Spring for new (All participants including DCAE/K8S)

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-3168

Migrate if doing something else in existing PF code in master

(Spring in policy-common?)


Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-3210

102

Policy Common, using JAX-RS annotationsCamelCamel the Commissining/Instantiation
Spring for Supervision/Monitoring
Use Camel where we need flexibility.

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-3211

103Parameter Handling

Built in parameter validation in policy commonSpring propertiesLet's investigate if the policy-common parameter handling can be got to work in Spring (javax validation)

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-3212

104

Policy Models, integrated serialization and persistence for most TOSCA entitiesCLAMP 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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-3213

105Persistence

Policy Models using JPA/JDBC/Eclipselink/MariaDBSpring 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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-3214

106UI

None (Angular in TOSCA PoC, APEX policy editor)ReactReact

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.

Code Structure, Build, and Test

Module StructureDocker BuildIntegration Test

AreaPolicy FrameworkCLAMPRecommendationComment

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-3215

201

Maven multi module projectSingle module project, builds everythingMulti ModulePrice to pay is that we could have some issues with getting integration coverage

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-3216

202

Common approach for current components and repos using a "packages" maven modulePart of Single module
Add TOSCA components to the Docker build, also see if or how we use the Policy Framework approach

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-3217

203

CSITs done per component, separate to buildComprehensive Integration test, part of buildThe ONAP recommendation is that Integration tests should be a part of the build.
204No JiradocsAll docs are in policy parentdocs in subdirectory in clamp repoMove to policy parent

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-3218

205UI

Separate "policy gui" repoui-react subdirectories in clamp repo

Let's think about it.

We should do this

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-3219

206Simulators

DMaaP Simulator A&AI, SDNC, CDS, APPC, and othersEmulator 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)

...