...
# | Issue | Notes | Decision |
|---|---|---|---|
| 1 | Short term solution will be delivered on 'latest branch | NOT in any specific commit/version mention in original bug | Agreed in meeting with stakeholders on |
| 2 | Where to Store Version Number | Database/ Liquibase (Liquibase not possible for NCMP) CPS-Core Liquibase as 'id' field which act as vessio. Current id/version is 15 see changelog/db/changes/15-rename-column-yang-resource-table.yaml | Use Liquibase ID as CPS & NCMP 'version'
|
| 3 | Does NCMP need (separate) version number from CPS-Core | Long term issue? | |
| 4 | Where to trigger implement upgrade action | Options:
| Developer agreed on Liquibase step 16 (depending issue #7) |
| 5 | What Dmi-registry yangmodel version we need to upgrade FROM | Relate commit message: https://gerrit.onap.org/r/gitweb?p=cps.git;a=commit;h=7914c8924723092345e8b4d829f15d2a3a5c72c8 Was the data compatibility issue introduced by changelog/db/changes/14-loadData-dmi-registry-2022-05-10-schema-set.yaml | |
| 6 | Does short term solution need version | Check with Tony Finnerty see #2 | |
| 7 | Technical debt: dmi-registry is installed as part of liquibase step in CPS-Core. Can solution build upon this technical debt | Add liquibase steps | Preferred solution is to use Liquibase step ie build upon the technical debt Check with Tony Finnerty |
| 8 | Do we need to worry about rollback | requires specific statements to execute rollbackYes
| Team and stakeholder agreed rollback support is required in case upgrade fails at customer |
| 9 | Size of customer data, can transformation cause delay/startup problems | ||
| 10 | Describe/document upgrade and rollback procedures? | Is this needed or handle as part of orchestration install/upgrade procedures |
...