.. This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE
.. Full license text at https://creativecommons.org/licenses/by/4.0/legalcode
+:orphan:
+
.. contents::
:depth: 3
..
(b) ‘Vpn-binding’is used to store ACTN OTN Tunnel model’s parameters.
- **OOF**: Updates include:
-
+
(a) NST selection is enhanced by fetching the templates from SDC directly.
(b) coverageArea to coverageAreaTAList mapping is done by OOF (as part of Slice Profile generation)
by accessing CPS.
(a) Service instantiation for non-shared and shared scenario and fixes to support option 1 are done
(b) NSI selection process support for shared NSI is tested
-
+
Impacted Modules for Istanbul Release
-------------------------------------
- **SO**
- **CN NSSMF**: Bug fixes in shared allocate flow, modify flow and terminate flow
- Slice Profile alignment with NSSMF
(d) NSMF based TN Slices (TN-FH, TN-MH are created by NSMF) - Work flow changes to support this approach
-
+
- **OOF**
(a) Integration with CPS for coverage area to coverage area TA list
(b) Bug fixes in NxI termination
- **CPS-TBDMT**
(a) This component is enhanced to support different type of queries based on templates
-
+
- **CPS**
- (a) Bug fixes and support for GET, POST, PATCH and DELETE type of queries.
+ (a) Bug fixes and support for GET, POST, PATCH and DELETE type of queries.
Istanbul Release - Functional Test cases
----------------------------------------
1. **E2E Network Slicing Solution**
- Slice selection based on resource occupancy level. With this enhancement, NSMF/NSSMF is able to monitor and update resource levels at NSI/NSSI level. OOF returns the solution for NSI/NSSI selection based on the criteria. In case of shared scenario, NSI/NSSI can be shareable only if sufficient resources are available in the network. RAN NSSMF’s resource occupancy is considered for this release. Resource occupancy of Core and TN NSSMFs will be considered in future releases.
- - Activate, Deactivate scenarios support in external RAN NSSMF - Option2. Note that instantiation and termination are supported in Istanbul release.
-
2. **RAN Slicing**
- Optimization of cm-handle registration with CPS-DMI Plugin for RAN NF instances to upload yang model.
- CPS integration with SDN-R for RAN slice allocation and reconfiguration scenarios
- CPS integration stabilization for RAN slice activate/deactivate and terminate scenarios. Validation and bug fix for CPS integration of RAN slice lifecycle.
- - CSIT for RAN slicing
3. **Transport Slicing**
- OOF involvement in TN slice reuse and terminate scenarios
- Implementation of the call to OOF for allocateNSSI to enable TN NSSI reuse in TN NSSMF
- CPS integration stabilization, which validates and enhances CPS integration for closed loop.
5. **Carryover tests from Istanbul release**
- Option-1 (internal NSMF, NSMF and NSSMF)
- - E2E testing for activate/deactivate scenario
- Pending test cases for E2E Slice termination
- - NSMF driven TN slicing
- - Pending testing for activate/deactivate and terminate scenarios
- Bug fixes and testing for Core slicing
- NF instantiation issue with same NSST
- Multiple non-share Core slice creation issue
------------------------------------
- **SO**: Requirements below are identified for Jakarta release and have impacts in SO component:
(1) Use of Optimization solution (OOF) in allocateNSSI, deallocateNSSI in TN NSSMF
- (2) Activate, Deactivate flows support in external RAN NSSMF for option 2
- (3) Bug fixes/enhancements of carryover test cases from Istanbul release
+ (2) Bug fixes/enhancements of carryover test cases from Istanbul release
- **OOF**: OOF component has an impact for the requirement below:
(1) NSI/NSSI Selection enhancements based on resource occupancy levels
(1) Optimizing cm-handle registration with CPS-DMI Plugin to upload yang model
(2) CPS Integration with SDN-R for RAN Slice allocate and reconfigure scenarios
(3) CPS Integration Stabilization - RAN Slice activate/deactivate and terminate scenarios
- (4) CSIT for RAN slicing
Jakarta Release - Functional Test cases
---------------------------------------
------------------------------------
The setup and operation details for E2E network slicing use case are available at `User Operation Guidance - Jakarta Release <https://wiki.onap.org/display/DW/User+Operation+Guidance+-+Jakarta+Release>`_.
+Jakarta Release - Automate Network Slicing Option2 preparation step
+-------------------------------------------------------------------
+
+Automation of the Network Slicing Option2 use case is under development. At this moment automation of the preparation step is completed, with the source code under `SMO package repo <https://github.com/sebdet/oran-deployment>`_. The detailed introduction of the framework can be found at `SMO package introduction <https://wiki.o-ran-sc.org/display/IAT/Automated+deployment+and+testing+-+using+SMO+package+and+ONAP+Python+SDK>`_.
+
+The preparation scripts are python scripts, based on the ONAP pythonsdk framework. More libraries are added under SMO package in order to run the preparation scripts.
+
+The preparation scripts locate in folder **test/pythonsdk/src/orantests/network_slicing**. Before running the script, please open **settings.py** under folder **test/pythonsdk/src/orantests/configuration**. Make sure the URL settings for all the components are the good values.
+
+If the settings are good, go to folder **test/pythonsdk/src/orantests/network-slicing** and run the following command to trigger the preparation script:
+
+
+.. code-block:: bash
+
+ cd ./test/pythonsdk/src/orantests/network-slicing
+ tox -e ns-tests
+
+The command will trigger the main script **test_network_slicing.py**, which in turn triggers the preparation script of each component.
+
+The whole preparation process will configure the components and also verifies a bit whether the configuration was done successfully at the end of each step.
+
+The whole process may take about 1 hour to complete. You can monitor the progress using the log file **pythonsdk.debug.log** located in the folder **network_slicing/preparation**.
+
+If everything goes fine, you will see similar logs as shown below in the end.
+
+.. image:: files/ns_automation/ns_automation_suc.png
+
+If things goes wrong, please read the logs to identify which part has go wrong and try to fix that step manually.
+
+Then you can update the **test_network_slicing.py**, disable steps that are already complete, and replay the tox command to complete the rest of the configuration.
+
+
+Please note, when checking **test_network_slicing.py** in details, you will find some of the preparation steps might require extra input parameters, such as **cst_id**, **cst_invariant_id** and **sp_id**. These values could be found in both logs and SDC UI.
+
+.. image:: files/ns_automation/ns_automation_test_class.png
+
+In case it failed in the middle of the SDC template creation, please update the **sdc_template_suffix** variable inside the **test_network_slicing.py** and then rerun the script with tox command.
+
+Since SDC doesn't support creating template with the same name, neither deleting of any templates, you have to add a suffix to the original name to create template with a new name.
+
+.. image:: files/ns_automation/ns_automation_sdc_suffix.png
+
+
Jakarta Release - Known issues and Solutions
--------------------------------------------
Details of up to date manual configurations, known issues, solutions and work-arounds can be found in the following wiki page: `Jakarta Release - Issues and Solutions <https://wiki.onap.org/display/DW/Jakarta+Release+-+Issues+and+Solutions>`_.
+
+Kohn Release Updates
+-----------------------
+In Kohn release, the following enhancements are implemented:
+
+- IBN driven E2E Network Slicing support including enhancement to Slice Analysis MS to listen to real-time user intents posted by AAI using DCAE SDK dmaap-client lib and and report slice KPI to UUI.
+- KPI computation enhancements including new KPI added and new UUI display design, KPI spanning multiple resources, error handling for missing counters.
+- DCAE R11 global requirements contribution `(See the wikipage here) <https://wiki.onap.org/display/DW/R11+Global+requirements+Contribution>`_.
+
+Kohn release also fixed a few critical bugs in Jakarta release.
+
+Impacted Modules for Kohn Release
+------------------------------------
+- **DCAE**: Requirements below for Kohn release have impacts on DCAE component:
+ (1) Enhancement to Slice Analysis MS
+ (2) KPI computation enhancements
+ (3) DCAE R11 global requirements and bug fixes
+
+- **UUI**: Requirements below for Kohn release have impacts on UUI component
+ (1) Slicing KPI monitoring and display for IBN driven network slicing
+
+Kohn Release Functional Test Cases
+---------------------------------------
+Details of the test cases can be found at: `E2E Network Slicing Tests for Kohn Release <https://wiki.onap.org/display/DW/E2E+Network+Slicing+Integration+Tests+for+Kohn+Release>`_ and its child wiki pages.
+
+London Release Updates
+-----------------------
+The following enhancements are added to the London release:
+
+- Support of 3GPP 28.532 based APIs for network slicing
+
+Impacted Modules for London Release
+------------------------------------
+- **SO**: Requirements below for London release have impacts on SO component:
+ (1) Enhancement to SO macro flow to support 3GPP 28.532 based APIs for network slicing
+ (2) NSST selection APIs for integration with OOF
+
+- **OOF**: Requirements below for Londond release have impacts on OOF component:
+ (1) NSST selection APIs for integration with SO
+
+London Release Test Cases
+--------------------------
+Details of the test cases can be found at: `E2E Network Slicing Tests for London Release <https://wiki.onap.org/display/DW/E2E+Network+Slicing+Integration+Testing+for+London+Release>`_.
Code Review / integration.git / blobdiff