Age | Commit message (Collapse) | Author | Files | Lines |
|
This update fixes the exceptions found in the integration tests
of transport slicing in Istanbul release
Issue-ID: SO-3631
Signed-off-by: hyu2010 <hyu2010b@gmail.com>
Change-Id: Ib085742f09f6c31bc6d238d1b9f4c12b3e16d04e
Signed-off-by: hyu2010 <hyu2010b@gmail.com>
|
|
Modify/re-use of an existing TN NSSI contains problems since
Guilin release. We have planned to resolve these issues in
Honolulu release. This submission contains these fixes.
Issue-ID: SO-3563
Signed-off-by: hyu2010 <hyu2010b@gmail.com>
Change-Id: If2b22260797135eab3cc74c66e0b9a9ec8d91d65
|
|
This update contains for the fixes for the following JIRAs:
SO-3483: Transport Slicing integration: status field in
resource_operation_status table should be in capital
letters
SO-3488: Transport Slicing integration: orchestration status
of TN NSSI is missing a 'd' in 'activate' and 'deactivate'
Issue-ID: SO-3483
Issue-ID: SO-3488
Signed-off-by: hyu2010 <hyu2010b@gmail.com>
Change-Id: I0e3ce5b8819aab61138d3eb7e119b9c9aa7e5a55
|
|
(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>
|