Age | Commit message (Collapse) | Author | Files | Lines |
|
This update contains for the fixes for the following JIRAs:
SO-3512: update logical-link name and logical-link id in
TN NSSI
SO-3544: Transport Slicing problems found in RAN NSSMF and
TN NSSMF integration
Issue-ID: SO-3512
Issue-ID: SO-3544
Signed-off-by: hyu2010 <hyu2010b@gmail.com>
Change-Id: I075bf76da635365260bfc52b0fe13ac3cb69c3c7
Signed-off-by: hyu2010 <hyu2010b@gmail.com>
|
|
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
|
|
This update contains for the fixes for the following JIRAs:
SO-3429: Transport Slicing integration: fix resource operation
status table mapping
SO-3434: Transport Slicing integration: modelUuid and modelInvariantUuid
are missing from service-instance
Issue-ID: SO-3429
Issue-ID: SO-3434
Signed-off-by: hyu2010 <hyu2010b@gmail.com>
Change-Id: I7a9b7b7a3e40d967c138067a01f2c045fb3e4b56
Signed-off-by: hyu2010 <hyu2010b@gmail.com>
|
|
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
|
|
- 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>
|
|
(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>
|