...
# | Interface | Requirement | Additional Information | Signoff | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | CPS-E-08 | NCMP will forward 'CM Notifications Subscription' LCM Create events to the appropriate DMI Plugins responsible for the CM Handles (ids) defined in the LCM Events. The message sent to DMI should include the private properties for each CM-Handle | ||||||||||
2 | CPS-E-08 | NCMP will forward 'CM Notifications Subscription' LCM Delete events to the appropriate DMI Plugins responsible for the CM Handles is defined in the LCM Events. The message sent to DMI should include the private properties for each CM-Handle | 'Basic' delete we be implemented followed by a more advanced delete operation depending on Merge functionality:
| |||||||||
3 | CPS-E-08 | NCMP responds using Kafka message(s) with the result of the LCM operation These messages wil use agreed status fields:
| Action: Define error details later | |||||||||
4 | CPS-E-08 | All events should use Cloud Events format | https://cloudevents.io/ | |||||||||
5 | Order of the create/delete subscription needs to be discussed . TBD.CPS-E-08 | Messages should be processed in the order they are created (received) | It will depend on DMIs responding within 30s. Subscription-id should be used as Kafka 'key' to ensure this. |
|
Error Handling
# | Error Scenario | Expected behavior |
---|---|---|
1 | Non responding DMIs (configurable timeout) | An error message listing the 'pending' CM Handle IDs and statusMessage as "partially applied subscription" with relevant statuscode. |
2 | Non Existing or non-valid CM Handle Ids | An error message listing the 'rejected' CM Handle IDs |
3 | DMI Plugin without CM Event subscription support | An error message listing the 'rejected' CM Handle IDs |
4 | Late (after timeout defined in #1) responding DMIs | A message contain the status message as "fully applied subscription" with relevant status code. |
...