| Date | User Story | Demo Recording | Comments | |
|---|---|---|---|---|
| 1 |
| CPS-1515 - Getting issue details... STATUS | Bulk (batch) Data Operations Demo | Demo (recording) was first part of regular CPS ONAP Meeting |
| 2 |
| Complete e2e DEMO: Notifications Creation of Subscriptions including schemas 1..5 with Cloud Events & common headers, latest enhancement on the schemas, and subscription status codes with details. | ||
| 3 |
| Partial DEMO of Forward Subscription Information to DMI Plugin(s) This DEMO includes Schema 1, Schema 3 and Schema 4 as mentioned in the Jira tickets. This DEMO does not include, Subscription Create Outcome part. | ||
| 4 | CPS-977 - Getting issue details... STATUS | Full Demo for CM Handle Query Endpoints Walkthrough of documentation followed by demo querying CM Handles using postman | ||
| 5 |
| CPS-1015 - Getting issue details... STATUS | Demo Distributed data store solution for Watchdogs Run three cps instance and all watchdog will wake up and start work on different cm-handles. | |
| 6 |
| CPS-1119 - Getting issue details... STATUS | Demo here shows the initial data sync state, along with the initial data sync enabled flag. The first demo shows the initial sync state being set to 'NONE_REQUESTED' when the data sync enabled flag is set to 'false' The second demo shows the initial sync state being set to 'UNSYNCHRONIZED' when the data sync enabled flag is set to 'true'. Note - Demo was initially supposed to be set as part of CPS Kubernetes cluster, bug has been raised in regard to this as kubernetes cluster is down. | |
| 7 |
| Shows the state registration in a state of ADVISED. The watchdog process will then kick off and set the state from READY to ADVISED. This will in turn create the schema set and anchor. This also shows the lock process too from STATE advised to LOCK. | ||
| 8 |
| CPS-875 - Getting issue details... STATUS | State Change From ADVISED to READY as part of watchdog process. State is added manually using PUT request api, it will be eventually be added as part of registration process. | |
| 9 |
| CPS-896 - Getting issue details... STATUS | Weekly CPS Meeting | Demo starts after about 40 minutes |
| 10 |
| CPS-731 - Getting issue details... STATUS | Query based on Public CM Properties | |
| 11 |
| CPS-322 - Getting issue details... STATUS | Implement additional validations for names used as identifiers | |
| 12 |
| CPS-817 - Getting issue details... STATUS | Create Endpoint For Get Cm Handles (incl. public properties) By Name | |
| 13 |
| CPS-872 - Getting issue details... STATUS | Update dmi-registry yang to support cmHandle State | |
| 14 |
| CPS-791 - Getting issue details... STATUS | CPS-Core sends DELETE notification event Note - Also shows UPDATE events. | |
| 15 |
| CPS-638 - Getting issue details... STATUS | Support Delete operation for Passthrough running within CPS-NCMP/DMI | |
| 16 |
| CPS-637 - Getting issue details... STATUS | Support Update/Replace operation for Passthrough running within CPS-NCMP/DMI | |
| 17 |
| CPS-644 - Getting issue details... STATUS | Get anchor identifiers for the given list of module names | |
| 18 |
| CPS-615 - Getting issue details... STATUS | Demo content:
Supporting materials:
| |
| 19 |
| CPS-374 - Getting issue details... STATUS | CPS-374.mp4 | sending data updated event to Event bus (Kafka) |
| 20 |
| CPS-373 - Getting issue details... STATUS | ||
| 21 |
| CPS-305 - Getting issue details... STATUS | ||
| 22 |
| CPS-265 - Getting issue details... STATUS |
| |
| 23 |
| CPS-231 - Getting issue details... STATUS | E2E - Data node query by cps path
| |
| 24 |
| CPS-199 - Getting issue details... STATUS | Demo CPS | E2E CPS Demo using Network Slicing Use case |
| 25 |
| CPS-8 - Getting issue details... STATUS | ||
| 26 |
| CPS-42 - Getting issue details... STATUS | Demo showing create module and then create anchor with few error scenarios as well. | |
| 27 |
| CPS-23 - Getting issue details... STATUS |
Overview
Content Tools