NCMP should be able to handle a large (10,000s!) batch of registrations at once. To make this possible we need to
| 1 | Create updated DMI Registry Yang Schema (using @yyyy-mm-dd) in changelog/db/changes/data/yang-models/dmi-registry @ 2021-12-13.yang to store Handle State | ||
| 2 | Change schema to have one entry (anchor) for each cm-handle instead of the current list! Registry becomes a dataspace with many anchors | ||
| 3 | Add State, LockReason and LockReasonDetails as (Yang)Strings to the schema. Any validation or enum-limitations can be handled in the Java code. | ||
| 4 | Consider timestamp for retry and timeout related scenarios as part of same schema update to reduce overhead of Liquibase changesets | ||
| 5 | Test/demo using CPS-Core |
- Create updated DMI Registry Yang Schema (using @yyyy-mm-dd) in changelog/db/changes/data/yang-models/dmi-registry @ 2021-12-13.yang to store Handle State
see also [https://wiki.onap.org/display/DW/CPS-677+Support+%27public%27+Cm+Handle+Properties#CPS677Support'public'CmHandleProperties-December2021YangModelforPublicPropertiesSupport - Change schema to have one entry (anchor) for each cm-handle instead of the current list!
- Test/demo using CPS-Core
- Can create anchor with new schema
- Can add and create data
A/C
- Propose and agree new model with team and stakeholders
- Demo
- Can create anchor using new model
- Can add data for new model
- Can query data using file based on state
Out of Scope:
- No Code changes!
- No CSIT Test