Honolulu release updates
------------------------
-In Honolulu release, the following aspects were realized:
+In Honolulu release, the following aspects were realized:
- **Modeling Enhancements** were made, details can be found at:
`Modeling enhancements in Honolulu <https://wiki.onap.org/display/DW/Modeling+enhancements+in+Honolulu>`_.
(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.
- Support Output Transformation
(a) Extract desired output from the data returned from CPS.
- (b) If 'transformParam' is not defined in the template no transformation takes place.
+ (b) If 'transformParam' is not defined in the template no transformation takes place.
- Support Multiple query
(a) Make multiple queries to CPS in single request.
(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**:
-
- (a) Support of NSI termination by enhancing the interaction with OOF, AAI and UUI
- (b) RAN NSSI Termination support with OOF & SDN-R interactions
- (c) Bug fixes in Option 1 (CSMF, NSMF and NSSMFs are within ONAP & TN-FH, TN-MH are created by RAN NSSMF)
-
- - **CSMF**: Fixed sNSSAI format and updated authentication for NSMF invocation
- - **NSMF**: Fixes in NSI termination issues to support OOF interaction for NSI termination query and added subnet Type support for respective TN Domain
- - **AN NSSMF**: Fixes for different termination scenarios in Option 1
- - **CN NSSMF**: Bug fixes in shared allocate flow, modify flow and terminate flow
- - Slice Profile alignement with NSSMF
- (d) NSMF based TN Slices (TN-FH, TN-MH are created by NSMF) - Work flow changes to support this approach
-
+- **SO**
+ (a) Support of NSI termination by enhancing the interaction with OOF, AAI and UUI
+ (b) RAN NSSI Termination support with OOF & SDN-R interactions
+ (c) Bug fixes in Option 1 (CSMF, NSMF and NSSMFs are within ONAP & TN-FH, TN-MH are created by RAN NSSMF)
+ - **CSMF**: Fixed sNSSAI format and updated authentication for NSMF invocation
+ - **NSMF**: Fixes in NSI termination issues to support OOF interaction for NSI termination query and added subnet Type support for respective TN Domain
+ - **AN NSSMF**: Fixes for different termination scenarios in Option 1
+ - **CN NSSMF**: Bug fixes in shared allocate flow, modify flow and terminate flow
+ - Slice Profile alignement 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
(a) Minor changes in Slice Analysis MS to support CPS integration
(b) KPI Computation MS in enhanced to support policy based KPIs and formula
-- **SDN-R**
+- **SDN-R**
(a) Bug fixes in instantiateRANSliceAllocate, instantiateRANSliceAllocateModify, activateRANSlice, terminateRANSlice Directed Graphs
(b) CPS integration for the instantiateRANSliceAllocateModify, activateRANSlice, terminateRANSlice Directed Graphs
(c) A new karaf feature is introduced to register the cm-handle with CPS
-- **CPS-TBDMT** - This component is enhanced to support different type of queries based on templates
-
-- **CPS** - Bug fixes and support for GET, POST, PATCH and DELETE type of queries.
+- **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.
-Functional Test cases
-----------------------
-**Honolulu release carry-over test cases**
+Istanbul Release - Functional Test cases
+----------------------------------------
+**Honolulu release carry-over test cases**
(a) Different possible scenarios of E2E Slice (eMBB) creation are tested in I-release
(b) RAN slice Termination testing completed
(c) Test cases to validate slice reuse and terminate using Option 2 (Core NSSMF and RAN NSSMF external) are completed
-
-**R9 Integration Testing**
+**R9 Integration Testing**
(a) RAN NSSMF integration with CPS is covered for RANSlice modification, activation, deactivation and termination
(b) NSMF driven TN-FH and TN-MH slices creation is tested
(c) CPS impacts in closed loop scenario is validated and few test cases are deferred to Jakarta release
-
- Integration test plan is available at `Integration Testing in Instanbul Release <https://wiki.onap.org/display/DW/R9+Integration+Test+for+E2E+Network+Slicing>`_
+ Integration test plan is available at `Integration Testing in Instanbul Release <https://wiki.onap.org/display/DW/R9+Integration+Test+for+E2E+Network+Slicing>`_
-Operation Guidance
---------------------
+Istanbul Release - Operation Guidance
+-------------------------------------
The steps for E2E network slicing use case will be available at `User Operation Guidance - Istanbul Release <https://wiki.onap.org/pages/viewpage.action?pageId=111118867>`_. It is an update to the user manual created in Honolulu release.
-Known issues and Solutions
----------------------------
-Issue occured during the deployment and integration testing will be listed in `Network Slicing - Issues and Solutions <https://wiki.onap.org/display/DW/Network+Slicing+-+Issues+and+Solutions>`_
\ No newline at end of file
+Istanbul Release - Known issues and Solutions
+---------------------------------------------
+
+**REGISTER 3RD PARTY CONTROLLERS**
+
+The ONAP TSC approved on July 9th, 2020 to change the status of ESR GUI Module
+to an 'unmaintained' project. Further information about 'Unmaintained Projects'
+can be found in the `ONAP Developer Wiki. <https://wiki.onap.org/x/Pw_LBQ>`__
+
+But excluding the ESR GUI module from ONAP does not mean that the “external
+system registration” mechanism is excluded; i.e. only the GUI is not available
+anymore.
+
+Nevertheless, in order to register the 3rd party controllers (like it is done
+in E2E network slicing use case and recently in Cloud Leased Line “CLL” use
+case as part of Intent-Based Networking), AAI’s API are invoked manually.
+
+To do so, please send the following CURL command (PUT) to your AAI, with the
+attached xml payload. In the payload, please adjust the controller name (in
+this case sdnc1) and the controller ip address accordingly based on your
+environment:
+
+CURL COMMAND:
+
+.. code-block:: bash
+
+ curl -k -X PUT https://{{your-onap-ip-address}}:30233/aai/v16/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/sdnc1 -u "AAI:AAI" -H "X-FromAppId:postman" -H "Content-Type:application/xml" -H "Accept: application/xml" -H "X-TransactionId:9999" -d @/home/onap/esr-registration-controller-1.xml
+
+
+PAYLOAD (esr-registration-controller-1.xml):
+
+.. code-block:: xml
+
+ <?xml version="1.0" encoding="UTF-8"?>
+ <esr-thirdparty-sdnc xmlns="http://org.onap.aai.inventory/v16">
+ <thirdparty-sdnc-id>sdnc1</thirdparty-sdnc-id>
+ <location>Core</location>
+ <product-name>TSDN</product-name>
+ <esr-system-info-list>
+ <esr-system-info>
+ <esr-system-info-id>sdnc1</esr-system-info-id>
+ <system-name>sdnc1</system-name>
+ <type>WAN</type>
+ <vendor>Huawei</vendor>
+ <version>V3R1</version>
+ <service-url>http://192.168.198.10:18181</service-url>
+ <user-name>onos</user-name>
+ <password>rocks</password>
+ <system-type>nce-t-controller</system-type>
+ <protocol>RESTCONF</protocol>
+ <ssl-cacert>example-ssl-cacert-val-20589</ssl-cacert>
+ <ssl-insecure>true</ssl-insecure>
+ <ip-address>192.168.198.10</ip-address>
+ <port>26335</port>
+ <cloud-domain>example-cloud-domain-val-76077</cloud-domain>
+ <default-tenant>example-default-tenant-val-71148</default-tenant>
+ <passive>true</passive>
+ <remote-path>example-remotepath-val-5833</remote-path>
+ <system-status>example-system-status-val-23435</system-status>
+ </esr-system-info>
+ </esr-system-info-list>
+ </esr-thirdparty-sdnc>
+
+
+Additional issues occured during the deployment and integration testing will be
+listed in the ONAP Developer Wiki at `Network Slicing - Issues and Solutions <https://wiki.onap.org/display/DW/Network+Slicing+-+Issues+and+Solutions>`_
\ No newline at end of file
Code Review / integration.git / blobdiff