Building Block Understanding


There are basically 2 flows - macro , a la carte.

In a la carte:

We manually will initiate each step for a process.

In macro:

The whole flow happens at a single click like if we want to create a service. The flow will itself look whether there are vnfs, pnfs or networks in the service and it will be created and activated in the flow also.Thus these independent tasks like if vnf is present, then assign create and activate vnf are all taken up as individual building blocks and are only called on need basis. Each and every request will reach to the api handler first.


# 1. Rest call reaching SO Api handler with the input json

According to the below path it is mapped to the createServiceInstance function in ServiceInstances file.

curl -v -H "Content-Type: application/json" -X POST --data @serviceinstance.json -u mso_admin:password1$ http://localhost:8080/onap/so/infra/serviceInstantiation/v7/serviceInstances.

# 2. Herein a unique requestid is generated corresponding to every request, and is checked whether that particular requestid exists in request db (Happens in createServiceInstance in ServiceInstances).

  1. http://request-db-adapter:8083/infraActiveRequests/requestid (GET), which will return a 404 if not exists.

  2. CreateInstance is set to the action variable. Here the request scope is set to service from the inputjson - modelType.

# 3. Running local validations on input json.

# 4. create InfraActiveRequests, to store request details in request db adapter and as a payload to bpmn.

  1. A new InfraActiveRequests object is created. And all the necessary information from the input is set to it.

  2. Retrieving productFamilyName from the input json to put into requests db. http://aai/servicedesigncreation/services/service/{productfamilyid} (GET), which will return a 404 if not exists in aai. If service exists, then that service’s serviceDescritiption is set as productfamilyName.

  3. http://aai/cloudinfrastructure/cloudregions/cloudregion/cloudowner/{lcpCloudRegionId}/tenants/tenant/{tenantId} (GET), checks for whether the particular cloud configuration exists in aai, if not exists returns 404. If we are able to get, then the tenant’s name derived from aai is set as tenantName.

  4. serviceInstanceName is derived from requestInfo.instanceName and is set.

  5. Request json is also set as RequestBody of InfraActiveRequests.

# 5. Checks fro whether duplicate name exists.

  1. version v[integer] is converted to the particular integer and stored.

  2. Checks whether instance name already exists in with a POST request in http://request-db-adapter:8083/infraActiveRequests/checkInstanceNameDuplicate, with the data { instanceIdmap = null, instanceName = {instanceName} , instanceservice = service } . It checks for the current progress and if in progress it throws the particular status.

# 6. Gets the orchestration url from the recipe table.

  1. Checks whether the service already exists in catalogdb http://catalog-db-adapter:8082/service/{modelNameVersionId} (GET).

  2. Checks the service recipe table with the modelNameVersionId and the action to be performed http://catalog-db-adapter:8082/serviceRecipe/search/findFirstByServiceModelUUIDAndAction?serviceModelUUID={modelNameVersionId}&action=createInstance . Returns a 404 if no recipe exists with the corresponding id.

  3. As recipe corresponding to this doesn’t exist, we try to get with a default value. This flow comes under generic resource flow so the default value is GR-API-DEFAULT. First we get service with this value http://catalog-db-adapter:8082/service/search/findFirstByModelNameOrderByModelVersionDesc?modelName=GR-API-DEFAULT (GET). It returns a service with modelUUID as d88da85c-d9e8-4f73-b837-3a72a431622b, and further can be used to get the recipe.

  4. http://catalog-db-adapter:8082/serviceRecipe/search/findFirstByServiceModelUUIDAndAction?serviceModelUUID=d88da85c-d9e8-4f73-b837-3a72a431622b&action=createInstance (GET), gives a recipe which has a parameter “orchestrationUri” as “/mso/async/services/WorkflowActionBB”.

# 7. Updates the infraActiveRequests with the current request.

  1. http://request-db-adapter:8083/infraActiveRequests/ (POST) with the data formed. And a 201 created response is received.

# 8. Call the bpmn with a post call on orchestrationUri. The data to bpmn is prepared having parameters like

  1. bpmnRequest - formed from input request.

  2. vfModuleId, pnfCorrelationId, networkId, configurationId, vfModuleType, serviceInstanceId , serviceType are updated if present in the input json or else set to empty string.

  3. apiVersion , requestId, aLaCarte = false (def), recipeTimeout = 180(def) ,requestAction= createInstance are all updated accordingly.

  4. requestUri - v7/serviceInstances ,which is formed from the request url.

# 9. A sync response is obtained on reaching bpmn like


# 10. Calls the WorkflowActionBB.bpmn


Hits WorkflowActionBB.bpmn


# 10.1. RetrieveBBExecutionList - implemented in selectExecutionList in

  1. resourcetype, resourceid are formed from matching the requestUri to a regex pattern matcher

[pattern=[vV]\d+.*?(?:(?:/(?<type>vnfs|vfModules|networks|networkCollections|volumeGroups|serviceInstances|instanceGroups)(?:/(?<id>[^/]+))?)(?:/(?<action>[^/]+))?(?:/resume)?)] .
  1. Checks whether there is a service subscription with service instance name as {instanceName} correspoding to the customer in aai


    Returns 404 not found, if it doesnt exists then the id of that particular instance is taken and given as both the resourceid and serviceinstance id. If not present then a random value is generated, and is assigned same to both.

  2. Checks whether there is a service of the particular serviceInstanceId exists in aai. https://aai.onap:8443/aai/v19/nodes/service-instances/service-instance/{serviceInstanceId} , returns not found if it doesnt exist. If service with corresponding instance name already exists , then flowsToExecute is got by quering the requestdbadapter with the earlier request id. If not present, then only orchestrationflows are got, and later from that the flowsToExecute are found out.

  3. Get the particular service from catalogdb . http://so-catalog-db-adapter.onap:8082/service/{modelNameVersionId} (GET). Be sure that the service with this particular modelNameVersionId exists in catalogdb, because based on the services (like whether pnf, or vnf, or networkcollection) present in that particular service, which all bbs to execute are decided.

  4. This being a service, “service” is added to the resource list. And is checked upon for other resources like vnf and network, eg:

    http://so-catalog-db-adapter.onap:8082/service/{modelNameVersionId}/vnfCustomizations (GET)

    http://so-catalog-db-adapter.onap:8082/service/{modelNameVersionId}/collectionResourceCustomizations (GET)

    http://so-catalog-db-adapter.onap:8082/service/{modelNameVersionId}/networkCustomizations (GET)

    And depending on the resources in the service, the resources found is updated like

    Found :Service - 1 Vnf - 0 Pnf - 0 VfModule - 0 VolumeGroup - 0 Network - 0 VirtualLink - 0 NetworkCollection - 0 Configuration - 0 InstanceGroup - 0

  5. Then the orchestration flows are get from the orchestration_flow_table depending on the cloudowner and request scope:

    http://so-catalog-db-adapter.onap:8082/northbound_request_ref_lookup/search/findOneByActionAndRequestScopeAndIsAlacarteAndCloudOwnerAndServiceType?action=createInstance&requestScope=Service&isALaCarte=false&cloudOwner={CloudOwner}&serviceType=%2A (GET)

    Here if present, then the orchestration flows are returned or else with default cloud owner, we try again

    http://so-catalog-db-adapter.onap:8082/northbound_request_ref_lookup/search/findOneByActionAndRequestScopeAndIsAlacarteAndCloudOwnerAndServiceType?action=createInstance&requestScope=Service&isALaCarte=false&cloudOwner=DEFAULT&serviceType=%2A (GET)

    Here in northBoundRequest is returned which has the parameter orchestrationFlowList, that contains the link that will return the orchestration flows.

    “orchestrationFlowList” : { “href” : “http://so-catalog-db-adapter.onap:8082/northbound_request_ref_lookup/101/orchestrationFlowList”}

    Now we do a get on the orchestration flow link to get the set of orchestration flows required


    Here a set of 20 orchestration flows are returned under the action of Service-Macro-Create, each with a sequence no assigned sequentially in the given order

    • AssignServiceInstanceBB,

    • CreateNetworkCollectionBB,

    • AssignNetworkBB,

    • AssignVnfBB,

    • AssignVolumeGroupBB,

    • AssignVfModuleBB,

    • ConfigAssignVnfBB,

    • AssignPnfBB,

    • WaitForPnfReadyBB,

    • ActivatePnfBB,

    • CreateNetworkBB,

    • ActivateNetworkBB,

    • CreateVolumeGroupBB,

    • ActivateVolumeGroupBB,

    • CreateVfModuleBB,

    • ActivateVfModuleBB,

    • ConfigDeployVnfBB,

    • ActivateVnfBB,

    • ActivateNetworkCollectionBB,

    • ActivateServiceInstanceBB.

  6. Flows to execute is determined by iterating through all the orchestartion flows and matching it with the found resources. It is merely a contains matching. In this particular as service was the only resource : List of BuildingBlocks to execute:AssignServiceInstanceBB, ActivateServiceInstanceBB.

  7. processing data is added to the requestdbadapter. Here the data is post to the requestdb as two different building blocks http://so-request-db-adapter.onap:8083/requestProcessingData.

  8. The already stored request details in request db is ammended like “lastModifiedBy” : “CamundaBPMN” , and status to in_progress with a put request.

# 10.2. sendSyncAck - This was used to give an acknowledgement , with status code as 200, and requestId and resourceId is sent as content.

# 10.3. Prevalidate the workflow

# 10.4. SelectBB - implemented in selectBBin WorkflowActionBBTasks

This is used to select the building block from the flows to execute depending on the sequence order.

  1. Depending on the current sequence , the building block is selected from the flows to execute.

  2. Execution variable, that is passed between the different building blocks as the payload is amended as: execution.setVariable(“buildingBlock”, buildingblockselected).

  3. current sequence is incremented by 1, and updated in execution variable.

  4. Depending on whether currentSequence is greater than flowsToExecute.size(), COMPLETED variable is either set to true or false.

# 10.5. updateFlowStatistics - implemented in updateFlowStatistics in WorkflowActionBBTasks

  1. Depending on the current sequence no, the completed bb and next bb is got from the flows to execute. And these are mentioned in a statusMessage.

  2. Percentage progress is got from the total no of bbs

  3. These are ammended to the already present request in the request db

# 10.6. Execute BB - calls the ExecuteBuildingBlock.bpmn

Hits ExecuteBuildingBlock.bpmn


# 10.6.1. BBInputSetup - implemented in execute in BBInputSetup

Here a generalbuildingblock is formed from executingbuildingblock after certain updations and validations.

  1. lookupKeyMap is formed from the input , and a map is formed with serviceInstanceId, networkID, vnfID, pnfID, vfmoduleID, volumegroupID, configurationID, instancegroupID as the keys.

  2. Depending on whether a la carte or macro , different flows are called. getGBBMacro is called in here.

  3. In getGBBMacro , a valid customer is got with service subscription. (getCustomerAndServiceSubscription)

    First a customer is got by get request on https://aai.onap:8443/aai/v19/business/customers/customer/{globalSubscriberId}

    After that ServiceSubscription is got by doing a get request


    If, the above request doesnt give any , then ServiceSubscription is fetched by first creating uri keys


    Then ServiceSubscription is got from the globalSubscriberId and the uri keys


    a valid customer and a corresponding ServiceSubscription must be present in the aai, for setting up the customer to gbuildingblock

  4. project and owningEntity is updated from the input

  5. service is got from the catalog db either by ModelVersionId or by ModelVersion and ModelInvariantId.

  6. ServiceInstance is created from the above parameters, and this ServiceInstance is used in the preparation of general building block.

  7. Depending on whether the current executing block name contains either of the network, or configuration, or network collection. A new instance of the corresponding type is created and is updated to the general building block (Happens in getGBBMacroNoUserParamsCreate)

  8. This general building block is set to the gBuildingBlockExecution and gBBInput parameter of execution.

# 10.6.2. StatusPolicy - implemented in validateOrchestrationStatus in OrchestrationStatusValidator. Input being gBuildingBlockExecution

  1. orchestrationStatus is obtained after checking the resource type. We had updated the orchestrationStatus in the above step when a new service instance was created.

  2. OrchestrationStatusStateTransitionDirective is got by doing a get call to the catlog db with the url as findOneByResourceTypeAndOrchestrationStatusAndTargetAction


  1. orchestrationStatusValidationResult parameter is set to executionvariable from the OrchestrationStatusStateTransitionDirective.getFlowDirective() “flowDirective” : “CONTINUE”

# 10.6.3. Prevalidate the gBuildingBlockExecution

# 10.6.4. BB To Execute: Depending on which building block is to be executed, that particular bpmn is called .In this case, AssignServiceInstanceBB is called

Hits AssignServiceInstanceBB.bpmn


# AAI create service subscription - implemented in createServiceSubscription of createAAITasks

This method is used for creating and subscribing the service in A&AI

  1. Customer is got from the general building block that was updated above

  2. Here a serviceSubscriptionURI is formed by taking in the globalSubscriberId and the serviceType

  3. If a service subscription for the particular customer doesnt exist in AAI, then a new subscription is created by taking in the serviceSubscriptionURI

GET performed on uri:https://aai.onap:8443/aai/v19/business/customers/customer/slice1/service-subscriptions/service-subscription/service? {“results”:[{“service-subscription”:1}]}

# AAI create service instance - implemented in createServiceInstance of createAAITasks

This method is used for creating the service instance in A&AI

  1. Customer is got from the general building block that was updated above

  2. A serviceInstanceURI is formed by taking in the globalSubscriberId, the serviceType and the service instance id

  3. If the service instance in the particular path doesnt exist in AAI , then a new service instance is created by using the serviceInstanceURI

GET to:https://aai.onap:8443/aai/v19/business/customers/customer/slice1/service-subscriptions/service-subscription/service/service-instances/service-instance/2b955def-e536-40ee-84cb-3f06e3cc6d84?

response: {"requestError":{"serviceException":{"messageId":"SVC3001","text":"Resource not found for %1 using id %2 (msg=%3) (ec=%4)","variables":["GET","business/customers/customer/slice1/service-subscriptions/service-subscription/service/service-instances/service-instance/2b955def-e536-40ee-84cb-3f06e3cc6d84","Node Not Found:No Node of type service-instance found at: business/customers/customer/slice1/service-subscriptions/service-subscription/service/service-instances/service-instance/2b955def-e536-40ee-84cb-3f06e3cc6d84","ERR.5.4.6114"]}}}

Sending HTTP PUT to:https://aai.onap:8443/aai/v19/business/customers/customer/slice1/service-subscriptions/service-subscription/service/service-instances/service-instance/2b955def-e536-40ee-84cb-3f06e3cc6d84

with req body : {"service-instance-id":"2b955def-e536-40ee-84cb-3f06e3cc6d84","service-instance-name":"DEMO_123456","model-invariant-id":"944862ae-bb65-4429-8330-a6c9170d6672","model-version-id":"d88da85c-d9e8-4f73-b837-3a72a431622b","orchestration-status":"Inventoried"}

# AAI create project - implemented in createProject of createAAITasks

This method is used for creation of the project A&AI. Here too it checks whether a project with a {projectName} exist in AAI . If not it creates one, and connects it to the service instance identified by the serviceInstanceId

Sending HTTP PUT to:https://aai.onap:8443/aai/v19/business/projects/project/name%20of%20proj/relationship-list/relationship

with req body: {"related-link":"/business/customers/customer/slice1/service-subscriptions/service-subscription/service/service-instances/service-instance/2b955def-e536-40ee-84cb-3f06e3cc6d84"}

# AAI create owning entity - implemented in createOwningEntity of createAAITasks

  1. OwningEntityId and OwningEntityName is extracted from the OwningEntity given in the input json

  2. If both of them are null, then an exception is raised.

  3. If only OwningEntityId is null, then whether the OwningEntityName is present in AAI is checked. If present then OwningEntityId is set by quering the OwningEntity from AAI. And then connect it to the service instance. If not present in the aai then a random id is generated and assigned to OwningEntityId. Then Owning entity is first created and then connected to the service instance

  4. Depending on whether the owning entity is already present or not, either createOwningEntityandConnectServiceInstance is called, or connectOwningEntityandServiceInstanceis called.

    Sending HTTP PUT to:https://aai.onap:8443/aai/v19/business/owning-entities/owning-entity/owningEntityIdof%20owningEntity/relationship-list/relationship
    req body: {"related-link":"/business/customers/customer/slice1/service-subscriptions/service-subscription/service/service-instances/service-instance/2b955def-e536-40ee-84cb-3f06e3cc6d84"}

# SDNC Create Assign Request - implemented in assignServiceInstance of SDNCAssignTasks

  1. Here first the requestContext, serviceInstance, customer are obtained from the general building block

  2. Then a payload for the assignServiceInstance of the sdnc is formed by passing in the above parameters to the assignServiceInstance in sdncSIResources.

  3. A new sdnc request is formed with the above thing as payload

  4. This sdnc request is assigned to the SDNCRequest parameter of the execution variable

     "request-information" : {
       "request-action" : "CreateServiceInstance",
       "source" : "MSO",
       "request-id" : "139636cd-4b69-4c3a-9e67-fed2c283baee"
     "sdnc-request-header" : {
       "svc-request-id" : "9bfe8cb0-bb8b-4dca-949d-2f2b51011b54",
       "svc-action" : "assign"
     "service-information" : {
       "onap-model-information" : {
         "model-name" : "GR-API-DEFAULT",
         "model-version" : "1.0",
         "model-uuid" : "d88da85c-d9e8-4f73-b837-3a72a431622b",
         "model-invariant-uuid" : "944862ae-bb65-4429-8330-a6c9170d6672"
       "subscription-service-type" : "service",
       "service-id" : "2b955def-e536-40ee-84cb-3f06e3cc6d84",
       "global-customer-id" : {global_customerid},
       "service-instance-id" : "2b955def-e536-40ee-84cb-3f06e3cc6d84"
     "service-request-input" : {
       "service-input-parameters" : {
         "param" : [ {
           "name" : "some name",
           "value" : "some value"
         } ]
       "service-instance-name" : {instance_name}

# It calls another bpmn file - SDNCHandler.bpmn

  1. Setup callback variables - Here mainly the correlator variable and the sdnc timeout variable is set

  2. callSDNC - Here post call to sdnc client is done with the above prepared payload. And then isSDNCCompleted is set to the execution variable

    Both the above tasks are implemented in SDNCRequestTasks.


# AAI Update (svc instance)- implemented in the updateOrchestrationStatusAssignedService in AAIUpdateTasks

BPMN access method to update the status of Service to Assigned in AAI. Here serviceInstance is obtained , then its orchestration status is changed to assigned and is updated in the AAI

Reaches back to ExecuteBuildingBlock.bpmn

# 10.6.5. Post validate the generic building block

# 10.6.6. Set Handling Code To Success - implemented in setHandlingStatusSuccess in ExecuteBuildingBlockRainyDay handling code is set to success for the execution variable

Reaches back to WorkflowActionBB.bpmn

# 10.7. postProcessingExecuteBB

If the building block excuted is ActivateVfModuleBB, then a postProcessingExecuteBBActivateVfModule needs to be executed

Then again it is looped back to selectBB through a checkRetryStatus block.

This block comes into play only if the handlingCode is retry, and the retry count is lesser than the maximum allowed no of retries, then the current sequence is again reduced by 1 , so that the same block is executed again. Request in the requestdb is updated with a setRetryStatusMessage, keeping an eye on the no of retries executed.

And in this particular example ActivateServiceInstanceBB. bpmn is called next in the sequence.

Here updateOrchestrationStatusActiveService is called, which is BPMN access method to update status of Service to Active in AAI. Here orchestrationStatus is set to active for the particular service instance and is updated in the AAI .

# 10.8. updateRequestStatusToComplete is called if the “complete” flag is true

  1. Here first the request is got from the requestDbclient http://request-db-adapter:8083/infraActiveRequests/requestid

  2. Then a status message is formed as “Macro-” + resourceName + “-” + action + ” request was executed correctly.”

This status message is updated in the request as well as is set to finalStatusMessage of the execution variable

  1. Other request parameters are updated


    request.setFlowStatus(“Successfully completed all Building Blocks”);




  2. This new request parameters are updated by a put request to the requestDbclient

Flow ends

If there are other resources present along with the service : Eg :- Volumegroup.( These BBs wil be specifically called )

  1. AssignVolumeGroupBB :

    1. genericvnfid and volumegroupid is obtained from the execution block.

    2. volumegroup orchestrationstatus is set to assigned

    3. a volume group of the above details is created in aai

    4. connect volumegroup to this genericvnf

    5. cloud configuration is got, and then the volumegroup is linked to tenant

  2. createVolumeGroupBB :

    1. get the vf details according to Vf module id from sdnc.

    2. vfmodulequeriedfromsdnc is set to the executionvariable.

    3. createVolumeGroupRequest is formed with getCloudRegion, serviceinstance, genericVnf, volumegroup, sdncVfModuleQueryResponse.

    4. calls vnfadapter, which in turn calls openstackadaptertask.

    5. update heattask in the volumegroup and which is ammended in the aai.

    6. orchestrationstatus for the volume group is set to created.

  3. ActivateVolumeGroupBB :

    orchestrationstatus for the volume group is ammended to active.

Rollback, Retry and abort

When exception is thrown then Error handling event subprocess in BPMN ExecuteBuildingBlock is invoked.


QueryRainyDayTable task main responsibility is to determine with rainy_day_handler_macro table the right policy to apply in order to recover from error.

For each BB a policy is defined in rainy_day_handler_macro table (retry, rollback, abort …)

HandlingCode parameter is populated with BB policy value.

# 1. In case of retry handling code

Policy in rainy_day_handler_macro table for current BB failure is Retry


Once Error handling subprocess has set handlingCode to retry value, the main process retries to execute previous failing BB (green arrow).


If a new failure occurred a new retry is performed (green arrow in Error handling subprocess)


Until max retry count is reached, this time secondary policy will be queried.


HandlingCode is now set with secondary policy value from rainy_day_handler_macro table (rollback, abort…)


# 2. In case of rollback handling code

Policy in rainy_day_handler_macro table for current BB failure is set to Rollback (or RollbackToXXX)


In case of Rollback the main process follows green arrows

  1. HandlingCode set previously in Error handling subprocess to Rollback (or RollbackToXXX) drives to RollBack Execution Path in main process

  2. RollBack Execution Path task has responsibility to prepare rollback flow sequence.

    BB FlowName are changed in the following way:

    • AssignXXX => UnassignXXX

    • CreateXXX => DeleteXXX

    • ActivateXXX => DeactivateXXX

    • AddXXX => DeleteXXX

    • VNFSetXXX => VNFUnsetXXX

    • VNFLockXXX => VNFUnLockXXX

    • VNFStopXXX => VNFStartXXX

    • VNFQuiesceXXX => VNFResumeXXX

  3. and 4. Loop on step 3 and step 4, BB are executed one after one in order to rollback previous flow execution.

  1. RollBack completed.

# 3. In case of Abort handling code

Policy in rainy_day_handler_macro table for current BB failure is Abort


Suppress Rollback

Request can disable rollback with suppressRollback parameter

if suppressRollback is set to false value, QueryRainyDayTable task will directly return abort without querying policy in table rainy_day_handler_macro

curl --location --request POST 'http://master2:30277/onap/so/infra/serviceInstantiation/v7/serviceInstances' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic abcdef' \
--header 'X-ONAP-PartnerName: NBI' \
--data-raw '{
    "requestDetails": {
        "subscriberInfo": {
            "globalSubscriberId": "ones"
        "requestInfo": {
            "suppressRollback": false,
            "productFamilyId": "Useless_But_Mandatory",