...
References
| Jira Legacy |
|---|
| server | System 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 | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | CPS-1616 |
|---|
|
| Jira Legacy |
|---|
| server | System 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 | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | CPS-1615 |
|---|
|
| Jira Legacy |
|---|
| server | System 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 | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | CPS-1812 |
|---|
|
| Jira Legacy |
|---|
| server | System 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 | 4733707d425b2b0a-2057557c-3a0f3c0c-ae5eb515-4fd8aff50176579789cceedb |
|---|
| key | CPS-1865 |
|---|
|
- Impl. Proposal for Merging of Subscriptions ( Positive Scenarios )
...
* Note 1: given the possible combinations the message to DMI needs to be able to specify different xpaths per cm-handle. So a more complex structure is needed for this even ie. an array of CM Handles objects each having their own list of (target) xpaths!
Note 2: as per decision #11'datastore' should be included in all messages as well
Note 3: the correlation-id for message to and from to DMI will be composed from the subscription-id and the dmi-name
Delete Combinations
| # | Existing Subscription A-10 | Existing Subscription B-52 | Client Delete A-10 Request | DMI Sub update/delete request | Data Model* Before Before | Data Model* After Delete |
|---|
| 1 | CH-1, [ /p/c1, p/c2 ] | CH-1, [ /p/c1 ] |
| CH-1, [ p/c2 ] |
| Expand |
|---|
|
| Client Subscription |
| DMI Subscription | | name | client-id | cm-handle | xpath | subscribers | | A | 10 | CH-1 | /p/c1 | [ A-10, B-52 ] | | B | 52 | CH-1 | /p/c2 | [ A-10 ] |
|
|
| Expand |
|---|
|
| Client Subscription |
| DMI Subscription | | name | client-id | cm-handle | xpath | subscribers | | A | 10 | CH-1 | /p/c1 | [ A-10 ] |
| CH-1 | /p/c2 | [ A-10 ] |
|
|
| 2 | CH-1, [ /p/c1]
CH-2, [ /p/c1] | CH-2, [ /p/c1]
CH-3, [ /p/c1] |
| CH-1, [ /p/c1]
|
| Expand |
|---|
|
| Client Subscription |
| DMI Subscription | | name | client-id | cm-handle | xpath | subscribers | | A | 10 | CH-1 | /p/c1 | [ A-10 ] | | B | 52 | CH-2 | /p/c1 | [ A-10, B-52] |
| CH-3 | /p/c1 | [ B-52 ] |
|
|
| Expand |
|---|
|
| Client Subscription |
| DMI Subscription | | name | client-id | cm-handle | xpath | subscribers | | B | 52 | CH-2 | /p/c1 | [ B-52 ] |
| CH-3 | /p/c1 | [ B-52 ] |
|
|
| 3 | CH-1, [ /p/c1]
| CH-1, [ /p/c1]
CH-2, [ /p/c1] |
| None |
| Expand |
|---|
|
| Client Subscription |
| DMI Subscription | | name | client-id | cm-handle | xpath | subscribers | | A | 10 | CH-1 | /p/c1 | [ A-10 ] | | B | 52 | CH-1 | /p/c2 | [ A-10, B-52 ] |
|
|
| Expand |
|---|
|
| Client Subscription |
| DMI Subscription | | name | client-id | cm-handle | xpath | subscribers | | B | 52 | CH-2 | /p/c1 | [ B-52 ] |
|
|
...
Error-Upon-Error Combinations
( To be captured as part of
...
| 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 |
|---|
|
...
...
...
...
...
)
| Previous Interaction | Current Interaction | Expectation | Notes | Sign-Off |
|---|
| 1 | any operation on non-existing cm-handle | operation for same non-existing cm-handle | listed in 'rejected' immediately | behavior as normal | |
| 2 | create operation rejected by DMI | create for same cm-handle/xpath | Submit create request again. |
| |
| 3 | create pending | create for same cm-handle/xpath | Set it to pending without submitting a new request. When we get response for previous interaction it is applied for the current interaction as well. |
| |
| 4 | create pending | delete for same cm-handle/xpath | Set an error 'Conflict/Busy' | up to client to retry the operation. | |
| 5 | delete pending | delete for same cm-handle/xpath | Set it to pending without submitting a new request. When we get response for previous interaction it is applied for the current interaction as well. |
| |
| 6 | delete pending | create for same cm-handle/xpath | Set an error 'Conflict/Busy' | up to client to retry the operation. | |
...