aboutsummaryrefslogtreecommitdiffstats
path: root/bpmn/so-bpmn-infrastructure-flows/src/main/resources/subprocess/DoAllocateTransportNSSI.bpmn
AgeCommit message (Collapse)AuthorFilesLines
2020-11-30Fixes for bugs found in Transport Slicing integrationhyu20101-1/+1
This update contains for the fixes for the following JIRA: SO-3406: Transport Slicing integration: environment_context and orchestration_status are wrong values Issue-ID: SO-3406 Signed-off-by: hyu2010 <hyu2010b@gmail.com> Change-Id: I9bccc3c916d4b775d3cfaf10d6c817faffa73c18
2020-10-07Fixes for bugs in Allocate TN NSSI WF found in integration testhyu20101-2/+2
- Fix for SO-3284: Exceptions in Allocate TN NSSI WF - Fix for SO-3293: Allocate TN NSSI fails to create relationship between allotted-resource and logical-links Issue-ID: SO-3284 Issue-ID: SO-3293 Signed-off-by: hyu2010 <henry.yu1@huawei.com> Change-Id: Ib625ec4b70db08af46031d392aa75ef22abd439e Signed-off-by: hyu2010 <henry.yu1@huawei.com>
2020-09-15Implementation of TN NSSMF WF on SOhyu20101-0/+493
(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>