...
| # | Description | Notes | Decision | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | AAI failed to send DMaaP notification after xNF was created |
| The bug causing this error was fixed and changes have been merged. | ||||||||||
| 2 | DMaap Client failed because of dependency Issues |
| The bug causing this error was fixed and changes have been submitted. | ||||||||||
| 3 | setFilter() is not documented | Fiachra Corcoran (DMaaP) advised any existing documentation is out of date and this should not be used | Based on input from (DMaaP) team and possible lack of future support we will do filtering on client side | ||||||||||
| 4 | Decide on which property to filter on | Which property from the DMaaP event should we filter on? | |||||||||||
| 5 | Update Events for address information | is it possible for address information to change ie. does CPS need to listen to these? | Address information might change but we don't need to worry about it for our use case as we use SDN-C and only the pnd-id to identify the resource |
Background
When a xNF object is added to A&AI, a DMaaP event, AAI-EVENT is created. A&AI handles the publishing of this event. To be notified of the AAI-EVENT, CPS will need to register on DMaaP Message Router.
...