...
Jira server ONAP Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CPS-1616 Jira server ONAP Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CPS-1615 - Impl. Proposal CM Event Subscription LCM: Create
- Impl. Proposal CM Event Subscription LCM: Delete
Requirements
Functional
# | 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. | '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:
| ||||||||||
| 4 | CPS-E-08 | All events should use Cloud Events format | https://cloudevents.io/ |
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. |
Characteristics
# | Parameter | Expectation | Notes |
|---|---|---|---|
| 1 | Frequency of LCM Events | No high volume of such events is expected For testing purposed 1 LCM event per minute would suffice | |
| 2 | How many subscriptions | ||
| 3 | How many cmhandles will be there per subscription | ||
| 4 | How many datastore-xpaths-filter for the subscription |
Out-of-scope
- Working with the wildcards, only list of specific CM Handle IDs are supported
- Subscription Update scenarios for an ongoing subscription.
...