Considerations for spike

1. load scenario: (model)sync 10,000 cm handles with same schema-set: imagine this is done by firing 1000 request of (batches of) 10 cm handles registration to a pool of cps-ncmp instances 
2. Are (service) code changes required to support this (assuming not)
3. What configuration changes are required (in ONAP deployment)
4. What load balancing is available, how can this be configured
5. What will be the likely bottlenecks when system is under load
   1. DB Contention?
   2. HTTP Protocol?
   3. External services (e.g. mediation)

Out of scope

• Other CPS components, for now this spike should only consider multiple instances of CPS-NCMP 

A/C

• Document Spike findings on Wiki
• Shared with and reviewed by team
• Present to stakeholders