-- Control Loop in TOSCA LCM Improvement: abstract Automation Composition
- Management (ACM) logic with a generic Automation Composition definition,
- isolating Composition logic from ONAP component logic. It elaborates APIs
- that allow integrate with other design systems as well as 3PP component
- integration.
-- The current PMSH and TCS control loops are migrated to use an Automation
- Composition approach. Support for Automation Compositions in SDC is also
- introduced.
-- A Metadata set allows a global set of metadata containing rules or global
- parameters that all instances of a certain policy type can use. Metadata
- sets are introduced in the Policy Framework in the Jakarta release. This
- means that different rule set implementations can be associated with a
- policy type, which can be used in appropriate situations.
-- Introduction of Prometheus for monitoring Policy components so that
- necessary alerts can be easily triggered and possible outages can be
- avoided in production systems.
-
- - Expose application level metrics in policy components. An end user can
- plug in a Prometheus instance and start listening to the metrics exposed
- by Policy components and either raise alerts or show them on a Grafana
- dashboard for operations team to keep monitoring the health of the system.
- - Improve the policy/api and policy/pap readiness probes to handle database
- failures so that the policy/api and policy/pap kubernetes pods are marked
- ready only if the Policy database pod is ready.
- - Provide sample Grafana dashboards for policy metrics
-
-- Migration of Policy Framework components to Springboot to support easier
- handling, configuration and maintenance.
-- Policy Framework Database Configurability. The Policy Framework can be
- configured to use any JDBC-compliant RDBMS and configuration files are
- supplied for the Postgres RDBMS. MariaDB remains the default RDBMS for the
- Policy Framework in ONAP
-- System Attribute Improvements
-
- - Transaction boundaries on REST calls are implemented per REST call
- - JDBC backend uses Spring and Hibernate rather than Eclipselink
- - All GUIs are now included in the policy/gui microservice
- - Documentation is rationalized and cleaned up, testing documentation is
- now complete
- - Scripts are added to make release of the Policy Framework easier
-
-Fault management
-^^^^^^^^^^^^^^^^
-
-- DCAE Helm Transformation finalized
-- Topic alignment for DCAE microservices: use standard topics for PM-Mapper,
- Slice-Analysis and KPI-MS