...
| # | Error Scenario | Expected behavior |
|---|---|---|
| 1 | DMI Not respond to initial synchronous request with normal HTTP timeout | Special Error message (Kafka event) including affected, and reason for all the handles in the message cm handles send to client topic detailing cm-handles (per dmi plugin) |
| 2 | Topic not supplied on CPS-E-05 | Return HTTP 501 (not implemented) |
| 3 | Client specided Topic is not configured | See open issue #9Log error message only |
| 4 | Non-existing cm-handle id | imilar Similar message but different reason as specified #1 above |
...
| # | Parameter | Expectation | Notes |
|---|---|---|---|
| 1 | Response Time 1 Batch request | <2 seconds (average) |
|
| 2 | Batch-size | 200 -300 cm handles | No hardcoded limit |
| 3 | Response payload size | ?? TBD KB | Performance test for cabilitie should be tested with this average response size |
| 4 | Maximum registered #cm handles | 20,000 | This will effect the internal query time |
| 5 | Supported # DMI PLugins | <30 (TBC)10 | This might effect processing timetimes |
| 6 | Test Environment | TBD | |
| 7 | Concurrent request | 12 | 12 clients requests toward 1 NCMP simultaneously |
| 8 | Request Frequency | 100 request/min | Should not affect performance, does not need to be tested |
Out-of-scope
- Support for multiple resource identifies identifiers in one batch operation
- Support cache cached data batch requests: only passthrough datastores will be supported (see decision #2)
- NCMP does NOT keep track of request status to see if it is completed, amalgamate responses or anything like that. It wil simply forward responses from the internal topic to the client topic.
- Access control
...