[TRNSPRTPCE-519] Refactor nbi-notifications Created: 09/Sep/21 Updated: 12/Sep/22 |
|
| Status: | Open |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Phosphorus |
| Type: | Story | Priority: | Low |
| Reporter: | Olivier Renais | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 2 weeks | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | 2 weeks | ||
| Issue Links: |
|
||||||||
| Epic Link: | Higher Rates | ||||||||
| Description |
|
Refactor nbi-notification to rationalize the code, according to TRNSPRTPCE-638. This means defining a baseline for notification provided through the kafka broker (Topics, message+ specific content that will depends on the notification type/topic). This shall include the management of notification on path-computation-result according to the need expressed by UTD through their contribution (code used during the OFC demo to provide information on the path to be established). |