Details
-
Story
-
Status: Closed
-
Medium
-
Resolution: Done
-
None
-
None
-
Policy 23/6 - 7/7, Policy 12/7-26/7
Description
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?
Attachments
Issue Links
- 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)