Versions Compared

Key

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

...

Gliffy
nameARH Flow
pagePin2

The following URL is exposed by SO for receiving Async notifications:

http://so-bpmn-infra.onap:8081/mso/async/services/updateStatus

The JSON format to be used in POST request is

      {
      "request-id":"abfcf8f5-1123-4870-b0bc-d4d21b03a9fa",
      "response-code":"200",
      "response-message":"SUCCESS",
      "ack-final-indicator":"Y"
      }

Once this response is received, SO performs the following:

  1. If response-code is 200, the CREATE service request in request DB table is updated as SUCCESS and progress as 100.
  2. If response-code is not 200, the CREATE service request in request DB table is updated as FAILED.
  3. If DB update is success, then response code 200 is sent to calling SDNC process.
  4. If DB update is failure or any exception occurs during update, then response code 500 is sent to calling SDNC process.
  5. Once the result is updated in request DB, the UUI which monitors the table gets updated as success/failure.

SDNC

The DG and notification call back handing in SDNC has already been supported in Frankfurt release. Modification in optical-package as well as in DGs are needed in G Release.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDNC-1233

The Async notification is received in SDNC when the service is activated in domain controller and then SDNC passes it to SO. 

For thsthis, we can use URL for POST: https://<SNDC Public IP>:30267/asyncNotification

The JSON format required for posting in this URL is as below:

      {
      "input":{
      "configuration-response-common":{
           "svc-request-id":"d33e2d45-3ee0-486f-af6e-1caf42db0aa7",
           "response-code":"200",
           "ack-final-indicator":"Y"
            },
      "service-identifiers":{
            "service-name":"async1_MDONS-OTN_Virtuora-MSA",
            "common-id":"abfcf8f5-1123-4870-b0bc-d4d21b03a9fa"
             }
        }
     }

SDNC

The DG and notification call back handing in SDNC has already been supported in Frankfurt release. Modification in optical-package as well as in DGs are needed in G Release.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDNC-1233

SO

An asynchronous call back SO Rest API needs to be added to support such functionality if the existing SO Rest API does not support MDONS.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2950

The following URL is exposed by SO for receiving Async notifications:

http://so-bpmn-infra.onap:8081/mso/async/services/updateStatus

The JSON format to be used in POST request is

      {
      "request-id":"abfcf8f5-1123-4870-b0bc-d4d21b03a9fa",
      "response-code":"200",
      "response-message":"SUCCESS",
      "ack-final-indicator":"Y"
      }

Once this response is received, SO performs the following:

  1. If response-code is 200, the CREATE service request in request DB table is updated as SUCCESS and progress as 100.
  2. If response-code is not 200, the CREATE service request in request DB table is updated as FAILED.
  3. If DB update is success, then response code 200 is sent to calling SDNC process.
  4. If DB update is failure or any exception occurs during update, then response code 500 is sent to calling SDNC process.
  5. Once the result is updated in request DB, the UUI which monitors the table gets updated as success/failure.

UpdateStatus Call Back

DESCRIPTION

...