Page Comparison

Investigate ways of persisting policy state information with different structures at run time. One approach could be to use Avro & Apache Hive. [There is also a NoSQL/JSON option available in MariaDB and Postgres]

Another option is the Apache Cassandra database. Datastax provide a Java Driver for Apache Cassandra.

Writing plugins towards state information stored in CPS might be another approach that could work across all the PDPs.

Multi-cluster database support

Upgrade/rollback of database tables

Invalid target-database property in persistence.xml in apex pdp.

Persistence.xml should use eclipselink.target-database

e.g. <property name="eclipselink.target-database" value="MySQL" />

Ajith Sreekumar

• reassign to Kevin

3 (bug fix)

Done

Currently, the models Provider classes manage transactions. Transaction management should be moved to client for better performance and atomicity. This will also eliminate the need for caching on the client side.

Note: The transactional annotation can be used  to group transactions together.

Ideally transactions should be executed serially in order to avoid dirty reads, non-repeatable reads and phantom reads. 

Note: DatabasePolicyModelsProviderImpl in the models-provider package provides rest APIs such as createServiceTemplate, updateServiceTemplate and deleteServiceTemplate which in turn call the corresponding APIs from AuthorativeToscaProvider in the models-tosca package..

How best to deal with CRUD of data types in policy-api and policy-models. It is possible only to create data types indirectly in policy type create requests. Update and delete of data types is not possible.

SimpleToscaProvider contains the following methods not available in AuthorativeToscaProvider : getDataTypes, getCascadedDataTypes, createDataTypes, updateDataTypes and deleteDataType.

Database backup and restore

1

rename to backup/restore

What policy components needs to be centralized vs de-centralized and moved to tenant namespaces. (R8 ONAP to support multi-tenancy)

Multi-tenancy support in Policy Framework

Note: Eclipselink supports Using Table-Per-Tenant Multi-Tenancy 

Clean up/Roll up of old DB data. Purge/Archive job should be created and run at a scheduled interval.

MariaDB Event Scheduler     Postgres pg_cron

MariaDB allows for the partitioning of tables : Partitioning Overview

4 (for purge)

6 (roll-up)

create separate tickets for purge & roll-up, and separate tickets for operations history and statistics

Externalizing ONAP DBs to a separate namespace

We would like to improve the current situation by implementing a two staged deployment:

1) Deploy all required DB engines (can be done using community charts or any user chart)

2) Deploy ONAP components & configure them to make use of those engines

This would allow use to basically bring his own database for ONAP no matter if it is running in the same k8s cluster or it has been provided by some DBaaS solution. Additionally it makes our deployment more modular and configurable thus may result in significant footprint savings.