Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

References

CPS-2169 - Getting issue details... STATUS  

Issues & Decisions


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 


Requirements

Functional


InterfaceRequirementAdditional InformationSignoff
1N/A

Registration & De-registration (Discovery) 

  • With moduleSetTag &
  • With alternateID

 

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


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
  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 Operation/Legacy

TBC next call
7N/A

CM change notification

  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

TBC next call



Error Handling


ScenarioExpected BehaviorNotesSignoff
1



Characteristics 


ParameterExpectationNotesSignoff





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

  • No labels