Versions Compared

Old Version 9

changes.mady.by.user Kolawole Adebisi-Adeolokun

Saved on

compared with

New Version 10

changes.mady.by.user Gerard Nugent

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


IssueNotes Decision
1

Review the use case returning all 50k cmHandle

Validity of the use case where ALL 50k CMhanlde are expected to be returned everytime ?

AP Csaba Kocsis & 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

AP Csaba Kocsis  & kieran mccarthy 


Requirements

Functional


InterfaceRequirementAdditional InformationSignoff
1N/A

Registration & De-registration (Discovery) 

  • With moduleSetTag &
  • With alternateID

 

  1. Parallel/Sequential  ? tbc Csaba Kocsis 
  2. Batch size of 100
  3. The whole cmhandle should be in ready state @the moment - TBC (should change to rate) Csaba Kocsis 


2N/A

CM-handle search

 

  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 ? @NCMP to confirm 
  3. Searches shall return all 50k searches within 1 minute max

3N/A

CM-handle ID Search

 

  1. Frequency will increase by 2.5 of current capacity
  2. Search shall return all 50k searches ? @NCMP to confirm
  3. Searches shall return all 50k searches within 1 minute max

4N/A

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

 

  1. Frequencies will increase (2.5) atm TBC Csaba Kocsis 
  2. Response time should stay the same as current - NCMP Characteristics

5N/A

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)

6N/A

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.

7N/A

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  

...