As part of the generic building block SO shall orchestrate the configure actions for VNFfor config deploy (new in Dublin release) . SO based on a tosca flag at VNF level (query to be provide) shall determine if the config deploy action needs to be triggered. The the flag is set to true SO shall trigger the controller with config deploy action with the payload provide below. 

Payload to be define.

{

  "commonHeader": {

    "originatorId": "SO",

    "requestId": "${uuid}",

    "subRequestId": "${sub-uuid}"

  },

  "actionIdentifiers": {

    "blueprintName": "${blueprint-name}",

    "blueprintVersion": "${blueprint-version"},

    "actionName": "config-deploy",

    "mode": "async"

  },

  "payload": {

    "config-deploy-request": {

      "config-deploy-properties": {

          ${object}

      }

    }

  }

}

Describe how SO will pass the Blueprint Name, Blueprint Version, and Action  from tosca data.

 

The config deploy shall be a asynchronous request that SO triggers self service api. SO shall immediately receive a sync status from Self Service API and shall wait for intermediate and final status from the controller for the config deploy transaction progress/completion. 

 

On successfully completion of Config Deploy SO shall update A&AI with orchestration Status Updates TBD in generic vnf object.

 

On failures of Config Deploy SO shall update A&AI with orchestration Status Updates TBD in generic vnf object.

NOTE: In Dublin release rollback/ConfigUndo/ConfigDelete of config config deploy will not be supported. This feature will be added for El Alto .