| Table of Contents |
|---|
| minLevel | 1 |
|---|
| maxLevel | 6 |
|---|
| outline | false |
|---|
| style | default |
|---|
| type | list |
|---|
| printable | true |
|---|
|
References
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | CPS-2169 |
|---|
|
Issues & Decisions
| Issue | Notes | Decision |
|---|
| 1 | Review the use case returning all 50k cmHandle | Validity of the use case where ALL 50k |
CMhandle CMhandles are expected to be returned everytime ? AP Csaba Kocsis & kieran mccarthy AP CPS to report where they think scalability issues will occur. TBC kieran mccarthy | |
| 2 | Proposal to remove hazelcast for NCMP Module sync | The use of Hazelcast during NCMP's CM-handle Module Sync is leading to: High memory usage during CM-handle registration Consistency problem Poor load balancing between NCMP instances for module sync
Proposal to remove hazelcast from NCMP Module Sync requires an LCM State Machine Change. Need stakeholder input. Proposal: CPS-2161: Remove Hazelcast from NCMP Module Sync |
AP Csaba Kocsis & kieran mccarthy
Requirements
Functional
Requirements
Functional
| Operations | Parallel/Sequential | DMI Delay | Response Size | Performance | Additional Information | Signoff |
|---|
| 1 |
N/A | Registration & De-registration (Discovery) |
In Batch size of 100 per request. With moduleSetTag & With alternateID
|
/Sequential ? tbc Csaba Kocsis Batch size of 100The whole cmhandle should be | | | How long should it take cmhandle to reach in ready state
|
@the moment - TBC (should change to rate) Csaba Kocsis 2 | N/A | CM-handle search |
- 11 Cm Handles/second per NCMP instance. Overall budget; Peter Turcsanyi
a. Advise → locked → Ready: ?
b. Advise → Ready: ? Initial delay ; Currently 2 min. TBC Peter Turcsanyi System driven load from topology Request ? Peter Turcsanyi
| | |
| 2 | CM-handle ID Search | 5 Parallel | | | Frequency will increase by 2.5 of current capacity Search shall return all 50k searches ? Searches shall return all 50k searches within 1 minute max TBD Base: Average: Peak:
| 5 parallel request of ID search and search, = combined total of 10 parallel search requests.
TBD; AP Peter Turcsanyi | |
| 3 | CM-handle search | 5 Parallel | | | 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 CM-handle ID Search Searches shall return all 50k searches within 1 minute max TBD
|
3 | N/A | 4 | N/ABase: Average: Peak:
| |
- 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
5 parallel request of ID search and search, Total of 10 parallel search requests.
No change TBD AP; Peter Turcsanyi | |
| 4 | Synchronous single CM-handle pass-through write (CUD) |
| 4 parallel Operations | | | Review; the current FS numbers What will be frequencies for write req. ? AP: TBD Frequencies will increase (2.5)
|
atm TBC Csaba Kocsis N/A5 | Stick with 10 req/sec= 25 req/sec (Should CPS PoC it?) to measure the current no of req. CPS measure current capacity CPS will engage in Setting the frequency (Based on previous result) Share with stakeholder No changes to Delay is expected
| |
| 5 | Synchronous single CM-handle pass-through Read |
4 (Parallel operations) | | | Frequencies will increase (2.5) atm TBC Response time should stay the same as current NCMP Characteristics (delay, size)
| CPS measure current capacity CPS will engage in Setting the frequency (Based on previous result) Share with stakeholder No changes to Delay is expected
| |
| 6 |
N/A | Batch Read Operation/Legacy |
| | | | Frequencies will increase (2.5) Same load 200 per request (Same response size) Same duration of test Responses are expected back in 80 sec.
| TBD AP; Peter Turcsanyi | |
| 7 |
N/A | CM change Notification 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
|
| | | 2,175 / sec (base/Average load) 8.75 k/sec (peak load) TBC kieran mccarthy Base: Average: Peak:
| Current numbers on FS as of today should be by 2.5 (non-negotiable). | |
Error Handling
| Scenario | Expected Behavior | Notes | Signoff |
|---|
| 1 | | | | |
Characteristics
| Parameter | Expectation | Notes | Signoff |
|---|
| 1 | | | | |
Robustness
| Scenario | Input Load | Performance | Notes | Number of NCMP Instances | Signoff |
|---|
| 1 | Base Performance & Performance | | | | | |
| 2 | Average Performance & Duration | | | | | |
| 3 | Peak Performance & Duration | | | | | |
| 4 | Number of Instances | | | | TBC - Each NCMP instance takes 11 CM-Handles/second. | |
Out of Scope
Datajob which is still in development are out of scope
For now Paging is out of scope, open to rescope depending on NCMP spike result
Solution Proposal