JIRA Relationships and Sequencing

Owned by Kevin Timoney
Last updated: May 10, 2021
1 min read

In Progress

Level 1

Level 2

Priority

Level 1

Level 2

Priority

POLICY-3000: Create an ability to recover if policy database gets corruptedClosed

POLICY-3231: Implement backup and restore functionality for PolicyDBClosed



1



POLICY-3249: Investigate backup and restore functionality for policy frameworkClosed





POLICY-3270: Create shell script to kick off the backupClosed





POLICY-3271: Create a docker image to call the backup scriptClosed





POLICY-3272: Create a kubernetes cron job to run the docker containerClosed



POLICY-2898: Policy should function in a multi-cluster environmentClosed



1



POLICY-3252: Investigate how other components in OOM are using mariadb clusterClosed



POLICY-1787: Support mariadb upgrade/rollback functionalityClosed



1



POLICY-3250: Investigate technology for upgrade/rollbackClosed





POLICY-3251: Create liquibase script for the existing databaseClosed



POLICY-3236: Adjust flexibility of Tosca Service Template HandlingClosed



5



POLICY-3255: Create Policy API calls for SimpleToscaServiceTemplateProviderClosed





POLICY-3256: Create new methods in tosca provider for get and delete of non-default policiesClosed



POLICY-2715: Allow underlying database to be configured: MariaDB or PostgresClosed

https://lf-onap.atlassian.net/browse/POLICY-2086



3



JIRA allocation to sprints

Level 1 Jira

2021-05-06

2021-05-20

2021-06-03

2021-06-17

2021-07-01

2021-07-15

2021-07-29

2021-08-12

Level 1 Jira

2021-05-06

2021-05-20

2021-06-03

2021-06-17

2021-07-01

2021-07-15

2021-07-29

2021-08-12

POLICY-3000: Create an ability to recover if policy database gets corruptedClosed



POLICY-3249: Investigate backup and restore functionality for policy frameworkClosed

















POLICY-3270: Create shell script to kick off the backupClosed

















POLICY-3271: Create a docker image to call the backup scriptClosed

















POLICY-3272: Create a kubernetes cron job to run the docker containerClosed































POLICY-2898: Policy should function in a multi-cluster environmentClosed













POLICY-3252: Investigate how other components in OOM are using mariadb clusterClosed











































POLICY-1787: Support mariadb upgrade/rollback functionalityClosed









POLICY-3250: Investigate technology for upgrade/rollbackClosed













POLICY-3251: Create liquibase script for the existing databaseClosed























POLICY-3236: Adjust flexibility of Tosca Service Template HandlingClosed













POLICY-3255: Create Policy API calls for SimpleToscaServiceTemplateProviderClosed















POLICY-3256: Create new methods in tosca provider for get and delete of non-default policiesClosed



























POLICY-2715: Allow underlying database to be configured: MariaDB or PostgresClosedhttps://lf-onap.atlassian.net/browse/POLICY-2086





Open

Level 1

Level 2

Priority

Level 1

Level 2

Priority

https://lf-onap.atlassian.net/browse/POLICY-1821



5

https://lf-onap.atlassian.net/browse/POLICY-2540



5

https://lf-onap.atlassian.net/browse/POLICY-2717



8

https://lf-onap.atlassian.net/browse/POLICY-2997



4



https://lf-onap.atlassian.net/browse/POLICY-2998





https://lf-onap.atlassian.net/browse/POLICY-311



https://lf-onap.atlassian.net/browse/POLICY-1837



5

https://lf-onap.atlassian.net/browse/POLICY-3153





https://lf-onap.atlassian.net/browse/POLICY-3167



4

https://lf-onap.atlassian.net/browse/POLICY-3156





Externalizing ONAP DBs to a separate namespace







Most of these issue are covered under https://lf-onap.atlassian.net/browse/POLICY-3297

Not included POLICY-1821, POLICY-2717, POLICY-3153 as they are either epics themselves or are included in other epics