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

Compare with Current View Page History

« Previous Version 6 Current »


Reference

CPS-1172 - Getting issue details... STATUS


Assumptions

#AssumptionNotes
1


Issues & Decisions

#IssueNotesDecision
1Agree registration performance KPI
  1. Size of request (e.g. 100 cm handles, total size <10Kb)
  2. Concurrent requests for registration (e.g. 4)
  3. Request frequency (e.g. 4 concurrent request each 5 seconds)
  4. Response time of each request (e.g. <4sec)
  5. Single CPS instance
  6. No other workload (module sync 'delayed')
  7. Default resources as defined in our helm charts

2

Agree test environment (talk with Andrew Fenner)

CI Job(s) required?
3Agree technology used to test
  1. Groovy/Spock
  2. CSIT
  3. Python
  4. K6 (not recommended)
  5. Other script using curl?

4Additional requirements to be able to run test

'dummy' DMI PLugin for testing ? (possibly not needed yet for this testcase)




Key Performance Indicators (KPIs)


Contact Toine Siebelink, Tony Finnerty, & kieran mccarthy 


#

Action

KPINotesDecision
1




Test Environment

TBD 

Contact Andrew Fenner 


Technology Assessments

Here the various technologies will be assessed to determine which can offer the most flexibility, maintainability, and reliability.


Groovy/Spock

There is an existing Groovy/Spock performance test located in org.onap.cps.ri.performance.CpsToDataNodePerfSpec that could be used as the basis for this...


CPS-1351 - Getting issue details... STATUS


#ProsConsNotes
1
  1. A lot of knowledge in the team
  2. Easier to control
  1. Might not be at the correct loacation - too low down?
  2. Adds additional time to tests during clean install
  1. Is it too low down in the stack


CSIT


#ProsConsNotes
1
  1. A lot of knowledge in the team
  2. Easier to control
  1. Adds additional time to tests during clean install


Python


#ProsConsNotes
1
  1. There is a lack of knowlesge in the team and ramp up would e necessary 


Curl/Script


#ProsConsNotes
1



Outcomes

#Outcome/ACNotesDone
1

Document proposal on Wiki and share with team and stakeholder



2

Agree with team and stakeholders on options proposed in Spike



References


  • No labels