You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Initial Comments

  1. 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
  2. We should have a picture of what the long term vision for CLAMP in the Policy Framework is
  3. How the TOSCA based Control Loop features are implemented should be in line with this long term vision

Policy Framework and CLAMP

Architecture

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

TechnologyPolicy FrameworkCLAMPRecommendationComment
Lifecycle ManagementPolicy CommonSpring Framework

RESTPolicy Common, using JAX-RS annotationsCamel

Parameter HandlingBuilt in parameter validation in policy commonSpring properties

TOSCA HandlingPolicy Models, integrated serialization and persistence for most TOSCA entitiesCLAMP TOSCA handling (more info)

PersistencePolicy Models using JPA/JDBC/Eclipselink/MariaDBSpring using JPA/JDBC/Hibernate/MariaDB

UINone (Angular in TOSCA PoC, APEX policy editor)React

Code Structure, Build, and Test

AreaPolicy FrameworkCLAMPRecommendationComment
Module StructureMaven multi module projectSingle module project, builds everything

Docker BuildCommon approach for all components and repos using a "packages" maven modulePart of Single module

Integration TestCSITs done per componentIntegration test part of build

docsAll docs are in policy parentdocs in subdirectory in clamp repo

UISeparate policy gui repoui-react subdirectories in clamp repo

SimulatorsDMaaP Simulator and othersEmulator for CLAMP external interfaces

Needs for TOSCA Control Loop Requirements





  • No labels