...
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 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-1812 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-1865 - Impl. Proposal for Merging of Subscriptions CM Subscriptions : Creating/Merging( Positive Scenarios )
Requirements
Functional
Interface | Requirement | Additional Information | Signoff | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | CPS-E-08e | 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-08e | 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. A delete should only be forwarded if there is no other subscription for cmhandle datastore path. |
| |||||||||
| 3 | CPS-E-08e | NCMP responds using Kafka message(s) with the result of the LCM operation These messages will use agreed status fields:
| Action: Define error details later
| |||||||||
| 4 | CPS-E-08e | All events should use Cloud Events format | https://cloudevents.io/ | |||||||||
| 5 | CPS-E-08e | 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. | |||||||||
| 6 | CPS-E-08.e | NCMP is to merge CM Notification Subscriptions create request and forward those to DMI plugin. (Interface to be added). |
| |||||||||
| 7 | CPS-E-08.e | Last lights out: upon subscription Delete request only when there is no more subscription for a cm-handle & xpath & datastore combination a subscription-delete request will be sent to the relevant DMI(s). | ||||||||||
| 8 | CPS-E-08.e | A single client subscription request should result into a maximum of one request per DMI. Of course there can be several messages if more than 1 DMI is involved. | ||||||||||
| 9 | CPS-E-08.e | Amalgamate response should include rejected/accepted/pending DMI responses received within 30 seconds. A client shall be notified of available DMI subscription information after 30 seconds. Subsequent DMI subscription updates shall be notified to clients as they become available. |
| |||||||||
| 10 | CPS-NCMP-I-01 | CM Handle deletion should NOT update subscription details. | Do NOT delete dmi-subscription entry until owning subscription is deleted, see issue #4 below | |||||||||
| 11 | CPS-E-08.e |
...
| # | Topic Name | Environment Variable | Source | Destination | Notes |
|---|---|---|---|---|---|
| 1 | subscription | CM_SUBSCRIPTION_NCMP_CMIN_AVC_SUBSCRIPTIONTOPIC | DME | DME/Client-Apps | |
| 2 | ncmp-dmi-cm-avc-subscription-<dmi-name> | NCMPCM_FORWARDSUBSCRIPTION_CMDMI_AVCIN_SUBSCRIPTIONTOPIC | NCMP | DMI Plugin | |
| 3 | dmi-ncmp-cm-avc-subscription | NCMPCM_RESPONSESUBSCRIPTION_CMDMI_AVCOUT_SUBSCRIPTIONTOPIC | DMI Plugin | NCMP | |
| 4 | subscription-response | NCMPCM_OUTCOMESUBSCRIPTION_CMNCMP_AVCOUT_SUBSCRIPTIONTOPIC | NCMP | DME/Client-Apps | |
| 5 | dmi-cm-events | DMI_CM_EVENTS_TOPIC | DMI Plugin | NCMP | actual data notifications as per the subscriptions |
| 6 | cm-events | NCMP_CM_EVENTS_TOPIC | NCMP | DME/Client-Apps | NCMP to forward the notifications to the client-apps. |
Operation Specific Impl. Proposals
Create and Merge
- Impl. Proposal for Merging of Subscriptions CM Subscriptions : Creating/Merging( Positive Scenarios )
Delete
- Impl. Proposal CM Event Subscription LCMSubscriptions : Delete // to be deprecated( Positive Scenarios )