...
| 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-1065 |
|---|
|
Open Issues & Decisions
| # | Issue | Notes | Decision |
|---|
| 1 | List scenarios | Need to clarify scenarios | Refer to Internal study |
|---|
| 2 | Topics | what topics are used in what scenario (topic for each Datastore ?) |
|---|
Refer to Internal studySee Topics section below.
All NCMP notifications to be published on the public cm-events topic by default regardless of data type, notification type or datastore the change came from. This topics acts as the TBAC_ALL topic.
cm-events topic name should be configurable in deployment settings.
Future : In future NCMP shall publish the notification based on TBAC where the notification is published on the appropriate target group topic cm-events[-<target-group-name>] matching the target group(s) the data type(s) is associated with. Not in scope of this story.
|
| 3 | Handle unknown event schemas | Wrap event? | Yes - see below. |
|---|
|
|
|
|
|---|
|
|
|
|
|---|
|
|
|
|
|---|
Event Flow Sketch
CM Event Specification Outline
...
