Backlog
| Number | Notes | Relates To | Type | Assignee |
|---|---|---|---|---|
POLICY-1821 - Getting issue details... STATUS | 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] | POLICY-2898 | Epic | |
POLICY-2898 - Getting issue details... STATUS | Need to determine a strategy and/or design for multi-cluster support. MariaDB Galera Cluster PostgreSQL Clustering Note: PostgreSQL does not natively support any multi-master clustering solution, like MySQL or Oracle do. | POLICY-1821 | Story | |
POLICY-2715 - Getting issue details... STATUS | Allow DB to be changed based on user needs e.g Postgres for MariaDB | POLICY-1787 | Epic | |
POLICY-1787 - Getting issue details... STATUS | Move table creation into the upgrade/downgrade/install scripts in order to support upgrade/rollback of ONAP releases. Liquibase may be the required solution. | POLICY-2715 | Story | Jorge Hernandez |
POLICY-2086 - Getting issue details... STATUS | References to DB should be moved from persistence.xml to properties file to facilitate the use of alternate databases. We may be able to use Kubernetes secrets to store this information. | Story | ||
POLICY-3059 - Getting issue details... STATUS | 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" /> | Task | Ajith Sreekumar | |
POLICY-1837 - Getting issue details... STATUS | 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: 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.. | Story | ||
POLICY-2540 - Getting issue details... STATUS | 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. | Story | ||
POLICY-3000 - Getting issue details... STATUS | Recover from corruption of policy database. [Possibly a bug in mariadb] | MDEV-23119 | Story | |
POLICY-2587 - Getting issue details... STATUS | The CLC (Control Loop Coordinator) lockingStrategy should allow policy designers to specify the target locking behaviour according to the needs of the use case [Policy template issue] | POLICY-2588 | Story | Pramod Jamkhedkar |
POLICY-2588 - Getting issue details... STATUS | Ability to implement target locking mechanisms over such sub-parts of a target or collection of targets. [Policy template issue] Note: AuthorativeToscaProvider provides synchronized object thread locking in it's methods. | POLICY-2587 | Story | Pramod Jamkhedkar |
POLICY-2717 - Getting issue details... STATUS | What policy components needs to be centralized vs de-centralized and moved to tenant namespaces. (R8 ONAP to support multi-tenancy) Note: Eclipselink supports Using Table-Per-Tenant Multi-Tenancy | Story | ||
POLICY-2997 - Getting issue details... STATUS | Clean up/Roll up of old DB data. Purge/Archive job should be created and run at a scheduled interval. | Story | Jorge Hernandez | |
POLICY-3153 - Getting issue details... STATUS | Concurrent DB access issues in control loop POC. | Bug | Ramesh Murugan Iyer |