Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyCPS-1492
<optional other relevant references, Jiras, Confluence pages, external links>


Subscription Creation Events Handling

Assumptions<optional>

<optional, assumptions are like decision made up front ie. everyone agrees on the answer but they are important to mention>

Assumptions

#AssumptionNotes
1Forwarded Subscription Event Responses communicate asynchronously.  (from DMI Plugins to NCMP) 


2The NCMP component should create a Subscription Event Outcome message and publish it into the topic (cm-avc-subscription-response) for Client Apps consumed from

Issues & Decisions

#IssueNotes Decision
1Do we need a analysis template?is convention for (new) developers to guide them

Luke Gleeson and Toine Siebelink  agreed we do to have consistent pages 

2This is an open issue3This is a very important (blocking issue)

<Note. use green for closed issues, yellow for important ones if needed>

Any Other Header

< we do not want to dictate the remainder of an analysis it will depend on the type of user story at hand>

Any Other Header

...

Possible 'timeframe' period for timeoutNCMP to Client Apps response timeout

30 sec.

2Response in a single step (as of now)from DMI to NCMP responses

Is the ACK would be required? No

DMI-Plugin would publish actual response to NCMP

3Response schema should be decided

from DMI to NCMP response schemas should be decided for single step response

Should DMI Plugins detail cm-hande IDs in response? Yes

Accept or Decline


4Subscription event outcome schema should be decided

from DMI to Client Apps

  • Possible options for initial response and further updates
     
    1. Status only: COMPLETED / PARTIALLY_COMPLETED
    2. List of accepted CM Handle IDs
    3. List of declined CM Handle IDs

We include : 

  1. Status only: COMPLETED / PARTIALLY_COMPLETED
  2. List of accepted CM Handle IDs
  3. List of declined CM Handle IDs

Note : Avoid for wild card * (for all cm handles)

Possible Topic Names

#SourceDestinationContentTopic Name
1Client AppsNCMPSubscription Create Eventcm-avc-subscription
2NCMPDMI Plugins

Forwarded Subscription Create Event

ncmp-dmi-cm-avc-subscription-{DMI-DATA-SERVICE-NAME}


3DMI PluginsNCMPForwarded Subscription Create Event Responsedmi-ncmp-cm-avc-subscription
4NCMPClient AppsSubscription Create Event Outcomecm-avc-subscription-response

Implementation Details


Testing Details