| Interface | Requirement | Additional Information | Signoff |
|---|
| 1 | N/A | Registration & De-registration (Discovery) - With moduleSetTag &
- With alternateID
| - Parallel/Sequential ? tbc
- Batch size of 100
- The whole cmhandle should be in ready state @the moment - TBC (should change to rate)
| |
| 2 | N/A | CM-handle search | - Frequency will increase by 2.5 of current capacity - CPS-391Spike: Define and Agree NCMP REST Interface - Developer Wiki - Confluence (onap.org)
- Search shall return all 50k searches ? @NCMP to confirm
- Searches shall return all 50k searches within 1 minute max
|
|
| 3 | N/A | CM-handle ID Search | - Frequency will increase by 2.5 of current capacity
- Search shall return all 50k searches ? @NCMP to confirm
- Searches shall return all 50k searches within 1 minute max
|
|
| 4 | N/A | Synchronous single CM-handle pass-through write (CUD) | - Frequencies will increase (2.5) atm TBC
- Response time should stay the same as current - NCMP Characteristics
|
|
| 5 | N/A | Synchronous single CM-handle pass-through Read | - Frequencies will increase (2.5) atm TBC
- Response time should stay the same as current NCMP Characteristics (delay, size)
|
|
| 6 | N/A | Batch Read Operation/Legacy TBC next callLegacy | - Frequencies will increase (2.5)
- Same load 200 per request
- Same duration of test
- Responses are expected back in 80 sec.
|
|
| 7 | N/A | CM change notificationNotification Event - NCMP shall support a CM notification load of 150 million CM change notifications per day with an average of 870 notification
- NCMP shall support a peak CM change notification load of 7k/s for a duration 5 minutes
| TBC next call - 2,175 / sec (base/Average load)
- 8.75 k/sec (peak load) TBC kieran mccarthy
|
|