Service Delete - Flowchart diagram - obsolete for now

• Upon reception of delete service request, existing workflow "DeleteCustomeE2EServiceInstance" to be invoked.
• Validate the request with parameters such as - requestid, serviceInstanceId, serviceType, operationId, operationType

• Update RequestDb table - operation-status with an entry for this service delete operation.

If request validation is success, then

• send the success sync response to ExternalAPII with valid message.
• Invoke DoDeleteServiceInstance workflow.

If request validation is failure, then

• send the failure sync response to ExternalAPI with valid message.
• Go to initial state.

• Get the request parameters required to get the service instance details from AAI.
• The request parameters are requestid, serviceInstanceId.
• Get the service instance details from AAI using serviceInstanceId

If service-instance is found in AAI, then

• Verify the request-status in requestDB

If service-instance is not found in AAI,then

• send response to ExternalAPI with valid message.
• Go to initial state.

If request-status = completed, then

• Get the decomposed service request deatils from requestDB.

If request-status is not completed, then

• verify if the request-status is Failed.
  1. If request-status is Failed, then
     1. send response to ExternalAPI.
     2. Go to initial state.
  2. If request-status is not failed, then
     1. wait for service creation process to be completed by checking the request-status in requestDB every 10 mins.

• Prepare the completion delete request to be sent to SDN-C

• If servicetype=OTN:
• Then update orchestration-status = deleting in AAI.
• Send the delete requests for domain services to SDNC via DMaaP.

Upon reception of SDNC response,

• verify if it received response from SDNC for all domain services delet requests.
• Based on received response, update operation status of sub request in request DB with progress and result.

If SO not recieved the response for all domain service delete requests,

• wait for SDNC response for rest of the delete requests.

If SO received the response for all domain service delete requests,

• verify the flag ack-final-indicator=N in response to identify if the response if sync or async.
• ack-final-indicator=N implies sync response.
• ack-final-indicator=Y implies async response.

Upon reception of SUCCESS sync response from SDNC,

• Update orchestration-status of L1 Access service instance in AAI(orchestration-status=deleting)
• Update operation-status of main request in requestDB with progress=75%
• Send sync response to UUI.
• Wait for async response with timer.

Upon reception of FAILURE sync response from SDNC,

• If partial failure(e.g., 1 controller sends failure)
  1. Update orchestration-status of L1 Access service instance in AAI(orchestration-status=inactive).
  2. send partial failure response to ExternalAPI.
• If complete failure
  1. Update orchestartion-status of L1 Access service instance in AAI(orchestration-status change to created)
  2. Send Failure response toExternalAPI.

Upon reception of SDNC async response within timeout,

• Follow the steps from (1e).

Upon reception of SDNC async response after timeout,

• Consider it as failure scenario.
• Update orchestration-status in AAI by reverting its value to created.
• Update request-status in requestDB with progress and result.
• Send response to UUI with valid message.
• Go to initial state.

Upon reception of SUCCESS async response from SDNC,

• Update orchestration-status of L1 Access service instance in AAI(orchestration-status=deleting)
• Update operation-status of main request in requestDB with progress=100%
• Send async response to ExternalAPII.

Upon reception of FAILURE async response from SDNC,

• If partial failure(e.g., 1 controller sends failure)
  1. Update orchestration-status of L1 Access service instance in AAI(orchestration-status=inactive).
  2. send partial failure response to ExternalAPI.
• If complete failure
  1. Update orchestartion-status of L1 Access service instance in AAI(orchestration-status change to created)
  2. Send Failure response to ExternalAPI