...
In MDONS use case, the domain OTN service activation sometime could happen hours, even days, after the service is created. Flow steps are the followfollowing:
- Notification callback URL is usually provided as input of service creation request.
- Upon activation successful, an a notification will be sent back to SDNC from SB domain controller by calling an appropriate DG
- The DG will call an SO API to update the status of the corresponding L1 Access Service.
Diagram
SDNC
The DG and notification call back handing in SDNC has already been supported in Frankfurt release. Minor modification Modification in optical-package is as well as in DGs are needed in G Release.
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SDNC-1233 |
---|
|
SO
There is a possibility that an An asynchronous call back SO REST Rest API needs to be added to support such functionality if the existing SO Rest API does not support MDONS.
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-2950 |
---|
|
References