Versions Compared

Key

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

...

#InterfaceRequirementAdditional InformationSign Off
1CPS-NCMP-I-01Update module

Upgrade module set for CM-Handle(s) using a

ModuleSetTag

moduleSetTag

Module Set Tag is owned (defined) by DMI Plugin
Known module set tags should prevent 'trips' to DMI for Module information
All data stores are accepted

2CPS-NCMP-I-01Initial Inventory can use ModuleSetTag  shall support (Optional) moduleSetTag tooTBC new performance requirements? 

Exiting performance shall not degrade.


3CPS-NCMP-I-01Update module set for CM-Handle(s) using a Blank ModuleSetTagmoduleSetTaguse 'old' algorithm from initial inventory
4CPS-E-05Read  moduleSetTag for given CM Handle(id)Probably no code changes required (just a model change)
5CPS-E-05Query Cm Handle(s) using CPS Path with moduleSetTagProbably no code changes required (just a model change)

Error Handling

#Error ScenarioExpected behavior
1Missing CM Handles (in list, some are OK)
2Upgrade request for 'cached' data (cache enabled)

...

Refuse request, not support

Characteristics

Excerpt


#ParameterExpectationNotes
1Request Frequency
Upgrade to NEW ModuleSetTags
2.5 3 upgrades  / second → 150 180 upgrades / minute

The assumption is there are 100 modules in each moduleSet and a moduleSet is available from a dmi plugin within 0.5 seconds.  Also assume there is a 90% overlap in modules across all CM Handles.

2Request Frequency
Upgrade to already existing ModuleSetTags
5 6 upgrades  / second → 300 360 upgrades / minute
3Test Environment


Expand
  1. CPS and NCMP

requests:
    cpu: 2000m
    memory: 2Gi
limits:
    memory: 3Gi
    cpu: 3000m

2. Postgres

requests:
    cpu: 4000m
    memory: 1Gi
 limits:
    memory: 3Gi
    cpu: 6000m



4Concurrent request12 clients requests toward 1 NCMP simultaneously
5Number of CM Handles in one request






...