-
Bug
-
Resolution: Done
-
High
-
Guilin Release, Honolulu Release
-
None
Currently, macro flow creates service with many vnfs in the wrong order. It does not group building blocks by the type of the resource and instead, the order of building blocks to be executed is determined only by the order of blocks from orchestration_flow_reference table.
Currently, we have
AssignServiceInstanceBB AssignVnfBB AssignVnfBB AssignVfModuleBB AssignVfModuleBB AssignVfModuleBB AssignVfModuleBB ControllerExecutionBB [vnf, config-assign] ControllerExecutionBB [vnf, config-assign] ControllerExecutionBB [vf-module, config-assign] ControllerExecutionBB [vf-module, config-assign] ControllerExecutionBB [vf-module, config-assign] ControllerExecutionBB [vf-module, config-assign] CreateVfModuleBB CreateVfModuleBB CreateVfModuleBB CreateVfModuleBB ControllerExecutionBB [vf-module, config-deploy] ControllerExecutionBB [vf-module, config-deploy] ControllerExecutionBB [vf-module, config-deploy] ControllerExecutionBB [vf-module, config-deploy] ActivateVfModuleBB ActivateVfModuleBB ActivateVfModuleBB ActivateVfModuleBB ControllerExecutionBB [vnf, config-deploy] ControllerExecutionBB [vnf, config-deploy] ActivateVnfBB ActivateVnfBB ActivateServiceInstanceBB
when we should have
AssignServiceInstanceBB AssignVnfBB AssignVfModuleBB AssignVfModuleBB ControllerExecutionBB [vnf, config-assign] ControllerExecutionBB [vf-module, config-assign] ControllerExecutionBB [vf-module, config-assign] CreateVfModuleBB ControllerExecutionBB [vf-module, config-deploy] ActivateVfModuleBB CreateVfModuleBB ControllerExecutionBB [vf-module, config-deploy] ActivateVfModuleBB ControllerExecutionBB [vnf, config-deploy] ActivateVnfBB AssignVnfBB AssignVfModuleBB AssignVfModuleBB ControllerExecutionBB [vnf, config-assign] ControllerExecutionBB [vf-module, config-assign] ControllerExecutionBB [vf-module, config-assign] CreateVfModuleBB ControllerExecutionBB [vf-module, config-deploy] ActivateVfModuleBB CreateVfModuleBB ControllerExecutionBB [vf-module, config-deploy] ActivateVfModuleBB ControllerExecutionBB [vnf, config-deploy] ActivateVnfBB ActivateServiceInstanceBB
There is no way also to specify the order of the processing of resources of the same type. When for instance vf-module-assign operation is conducted we can't enforce to process them in the specified order. For that, we should introduce some priority fields in the SO request.
