aboutsummaryrefslogtreecommitdiffstats
path: root/bpmn/so-bpmn-infrastructure-flows/src/main/resources/subprocess/DoDeallocateTransportNSSI.bpmn
AgeCommit message (Collapse)AuthorFilesLines
2020-10-15Fixes for bugs found in Transport Slicing integrationhyu20101-2/+2
This update contains for the fixes for the following JIRAs: SO-3308: Transport Slicing integration: MSOWorkflowException: mso-request-id not provided SO-3309: Transport Slicing integration: unable to get prefix environment variable from execution in TnNssmfUntils SO-3310: Transport Slicing Integration: null pointer exception in saving SDNC rollback data Issue-ID: SO-3308 Issue-ID: SO-3309 Issue-ID: SO-3310 Signed-off-by: hyu2010 <henry.yu1@huawei.com> Change-Id: I0c9ed038454b309914ddee6ea2366db58f248f9f Signed-off-by: hyu2010 <hyu2010b@gmail.com>
2020-09-15Implementation of TN NSSMF WF on SOhyu20101-0/+221
(1) Workflow of Allocate TN NSSI (2) Workflow of Deallocate TN NSSI (3) Workflow of Activate and Deactivate TN NSSI (4) Workflow of Modify TN NSSI NOTE: 1. The full implementation of TN NSSMF consists of two layers: (1) The TN Sice definition layer, which is an orchestration layer that provides the NBI of TN NSSMF to its consumers (i.e., it concerns the "what" question), and (2) the TN slice realization layer, which is responsible for the actual network configurations of TN slicing (i.e., the "how" question). The first layer is done on the SO (i.e., this changeset), while the 2nd layer is implemented on the SDNC. That's why this changeset is relatively simple, since the "real work" is done by the SDNC. 2. This changeset depends on the common NSSMF WF (https://gerrit.onap.org/r/c/so/+/111477) Issue-ID: SO-2959 Signed-off-by: hyu2010 <henry.yu1@huawei.com> Change-Id: I9d4e77b7706d28fb4133ddca0ff1d6e307be613d Signed-off-by: hyu2010 <henry.yu1@huawei.com>