[TRNSPRTPCE-638] Specs on how notifications shall be handled Created: 02/Mar/22  Updated: 12/Sep/22

Status: Open
Project: transportpce
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: High
Reporter: Olivier Renais Assignee: Olivier Renais
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to TRNSPRTPCE-378 Implement OR service-notification Open
relates to TRNSPRTPCE-519 Refactor nbi-notifications Open
Epic Link: Service assurance

 Description   

Build a specification defining the notification we must handle and the way we will handle them. Propose to handle notifications associated with services (including all information associated with the service grouping) according to OpenROADM APIs. Notifications associated with alarms, state change, path computation result used in the scope of MDONs, and OFC demonstrations will be handled through Kafka broker and DMaaP. The scope of this task is to define a specification so that coders understands how to handle nbi-notification refactoring (TRNSPRTPCE-519) as well as OpenROADM service-notification ((TRNSPRTPCE-378)


Generated at Wed Feb 07 20:43:38 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.