CPS-2169: NCMP to support 200k Cells (50KCM-handles)
References
https://lf-onap.atlassian.net/browse/CPS-2169
Issues & Decisions
Issue | Notes | Decision | |
|---|---|---|---|
| 1 | Review the use case returning all 50k CM Handles | Validity of the use case where ALL 50k CMhandles are expected to be returned every time ? AP @Csaba Kocsis & @kieran mccarthy
Jan 30, 2025
| May 13, 2025 @Toine Siebelink All KPIS are now signed off. |
| 2 | Proposal to remove Hazelcast for NCMP Module sync | The use of Hazelcast during NCMP's CM-handle Module Sync is leading to:
Proposal to remove hazelcast from NCMP Module Sync requires an LCM State Machine Change. Need stakeholder input. | Mar 26, 2025 @Daniel Hanrahan @Toine Siebelink
|
| 3 | Impacts CM Event Storm | Wil requires special test setup (maybe once off testing in CPS Team) to asses impact of CM Event Storm on KPIs | May 12, 2025 @Csaba Kocsis @kieran mccarthy All KPIs should still be met during a CM Event Storm. |
Requirements
Characteristics (only)
Operations | Parallel | Performance | Notes | Status Apr 24, 2025 | Signoff | |
|---|---|---|---|---|---|---|
| 1 | Registration & De-registration (Discovery) In Batch size of 100 per request.
| Parallel |
|
|
Adjust both Blue line | Apr 28, 2025 Agreed with @kieran mccarthy @Csaba Kocsis |
| 2 | CM-handle ID Search | 5 Parallel |
| Aug 28, 2024
Jan 30, 2025 @kieran mccarthy |
| Apr 29, 2025 Agree to have 10% above for every 10k cm handles 50K: 2 Sec + 3 * 0.2 Sec = 2.6 Sec @kieran mccarthy @Csaba Kocsis |
| 3 | CM-handle search | 5 Parallel |
| Aug 28, 2024
Jan 30, 2025 No change TBD AP; @Peter Turcsanyi @kieran mccarthy |
| Apr 29, 2025 Agreed to have 20% above every 10k cm handles 50K: 15 Sec + 3 * 3 Sec = 24 Sec |
| 4 | Synchronous single CM-handle pass-through Read (CUD) | 4 parallel Operations | Review; the current FS numbers
| Nov 19, 2024
Jan 30, 2025 Policy executor have different test suit and won’t be impacted by this @kieran mccarthy |
| Apr 28, 2025 Agreed with @Csaba Kocsis @kieran mccarthy |
| 5 | Synchronous single CM-handle pass-through Write | 4 (Parallel operations) |
| Jan 30, 2025 @kieran mccarthy
|
| Apr 28, 2025 Agreed with @kieran mccarthy @Csaba Kocsis |
| 6 | Batch Read Operation/Legacy |
|
| Investigation needed because target is not met at this point Jan 30, 2025 |
| Apr 28, 2025 Agreed with @kieran mccarthy @Csaba Kocsis |
| 7 | CM change Notification Event
|
|
| Jan 30, 2025 Use number on FS and * 2.5 as the source of truth |
| May 12, 2025 @kieran mccarthy @Csaba Kocsis
|
CM Event Background Load Specification
80k cells | Base Rate | Peak Rate* | Storm Rate** |
|---|---|---|---|
AVC | 368 | 752 | 4,744 |
Create/Delete | 288 | 312 | 312 |
Total | 656 | 1,064 | 5,056 |
200k cells (50k cmhandles) | |||
AVC | 920 | 1,880 | 11,860 |
Create/Delete | 720 | 780 | 780 |
Total | 1,640 | 2,660 | 12,640 |
* Peak Rate happens 96 times a day for 5 minutes each time.
** Storm Rate happens 6 times a day for 6 minutes each time.
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