-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
Policy 23/6 - 7/7, Policy 12/7-26/7
As an ONAP Policy Developer, I need to be able to support upgrade/rollback of ONAP releases so the community is not required to start from scratch when a new release occurs.
Must support both the api/pap and xacml-pdp. One of the actual components must be able to support this.
Should remove "create" flags from persistence.xml and move table creation into the upgrade/downgrade/install scripts.
Prefer it to work with other DBMSs besides just mariadb?
Should this be an ONAP-wide requirement?
- relates to
-
POLICY-3404 Rolling DB errors in log output for API, PAP, and DB components
-
- Closed
-
-
POLICY-2715
Allow underlying database to be configured: MariaDB or Postgres
-
- Closed
-
(1 mentioned in)
1.
|
Investigate technology for upgrade/rollback |
|
Closed | ktimoney |
2.
|
Create liquibase script for the existing database |
|
Closed | Unassigned |
3.
|
Move drools-pdp db-migrator to separate container |
|
Closed | ktimoney |
4.
|
Update OOM to include initContainer for db-migrator |
|
Closed | ktimoney |
5.
|
Update Policy Components not to create tables |
|
Closed | Adheli Tavares |
6.
|
Update db-migrator to include ability to deal with partial installs |
|
Closed | ktimoney |
7.
|
Add db-migrator to CSIT |
|
Closed | ktimoney |
8.
|
Integration testing for db-migrator |
|
Closed | ktimoney |
9.
|
SQL script for PdpStatistics |
|
Closed | Adheli Tavares |
10.
|
Update existing pdpstatistics records with IDs |
|
Closed | Adheli Tavares |
11.
|
Update pdp_enginestats records during upgrade/downgrade |
|
Closed | ktimoney |