Versions Compared

Old Version 16

changes.mady.by.user Kolawole Adebisi-Adeolokun

Saved on

compared with

New Version 17

changes.mady.by.user Kolawole Adebisi-Adeolokun

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
styledefault
typelist
printabletrue

...

Issue

Notes 

Decision

1

Review the use case returning all 50k cmHandle

Validity of the use case where ALL 50k 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:

  1. High memory usage during CM-handle registration

  2. Consistency problem

  3. 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

  • CPS optimised locking mechnism on the bug

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyCPS-2403

  • Still open pending CPS completion of Hazalcast study

Requirements

Functional

Operations

Parallel/Sequential

DMI Delay

Response Size

Performance

Additional Information

Signoff

1

Registration & De-registration (Discovery) In Batch size of 100 per request.

  • With moduleSetTag &

  • With alternateID

Parallel

  1. How long should it take cmhandle to reach in ready state - 11 Cm Handles/second per NCMP instance.

Base:

  • Average:

  • Peak:

    1. Overall budget; Peter Turcsanyi
      a. Advise → locked → Ready: ?
      b. Advise → Ready:

    30 Oct

    1. ?

    2. Initial delay ; Currently 2 min. TBC Peter Turcsanyi

    3. System driven load from topology Request ? Peter Turcsanyi

    2

    CM-handle ID Search

     

    5 Parallel

    1. Frequency will increase by 2.5 of current capacity

    2. Search shall return all 50k searches ?

    3. Searches shall return all 50k searches within 1 minute max TBD

    4. Base:

    5. Average:

    6. Peak:

     

    1. 5 parallel request of ID search and search, = combined total of 10 parallel search requests.

    3

    CM-handle search

     

    5 Parallel

    1. Frequency will increase by 2.5 of current capacity - CPS-391Spike: Define and Agree NCMP REST Interface - Developer Wiki - Confluence (onap.org)

    2. Search shall return all 50k searches ?  

    3. Searches shall return all 50k searches within 1 minute max TBD

    4. Base:

    5. Average:

    6. Peak:

     

    1. 5 parallel request of ID search and search, Total of 10 parallel search requests.

    4

    Synchronous single CM-handle pass-through write (CUD)

    Review; the current FS numbers

    1. What will be frequencies for write req. ? TBD

    2. Frequencies will increase (2.5) of current performance of 25 request/sec= 62.5req/sec…. Currently 10 req/sec= 25 req/sec

    3. Response time should stay the same as current - NCMP Characteristics

    4. Base:

    5. Average:

    6. Peak:

    5

    Synchronous single CM-handle pass-through Read

     

    1. Frequencies will increase (2.5) atm TBC

    2. Response time should stay the same as current NCMP Characteristics (delay, size)

    3. Base:

    4. Average:

    5. Peak:

     

    6

    Batch Read Operation/Legacy 

     

    1. Frequencies will increase (2.5)

    2. Same load 200 per request

    3. Same duration of test

    4. Responses are expected back in 80 sec.

    5. Base:

    6. Average:

    7. Peak:

     

    7

    CM change Notification Event

    1. NCMP shall support a CM notification load of 150 million CM change notifications per day with an average of 870 notification

    2. NCMP shall support a peak CM change notification load of 7k/s for a duration 5 minutes

     

    1. 2,175  / sec (base/Average load)

    2. 8.75 k/sec (peak load) TBC kieran mccarthy

    3. Base:

    4. Average:

    5. Peak: 

     

    Error Handling

    Scenario

    Expected Behavior

    Notes

    Signoff

    1

    ...