E2E Network Slice - Lifecycle

This page covers the steps to reproduce the below scenarios:

E2E Network Slice Instantiation
E2E Network slice Modification (Reuse)
E2E Network Slice Activation (WIP)
E2E Network Slice Deactivation
E2E Network Slice Termination

MANUAL CONFIGURATION:

Other than these all the manual configurations are same as of H release.

Details of the Manual Configuration for Honolulu can be found at Install Minimum Scope for Option 1

1. SDC Template Design:

The template design steps of the E2E Network Slicing use case for Option1 can be found at Template Design for Option 1

2. UUI:

Update the images of the UUI components -

image: onap/usecase-ui-server:4.0.3
image: onap/usecase-ui:4.0.3

For Coverage Area to Coverage Area TA List mapping, provide the coverage Area Number in the service creation(pl note it has to preloaded coverage area number in CPS TBDMT)

3. CPS:

Follow the steps below to setup the CPS environment:

Clone the repo from : https://gerrit.onap.org/r/admin/repos/cps
Build the project – When building the project run from the root cps folder : mvn clean install
From docker-compose folder, run the following after building the images locally : VERSION=latest DB_USERNAME=cps DB_PASSWORD=cps docker-compose up -d
Create the dataspace, schemaset, anchor and datanode using CPS APIs. This file has the sample APIs for CPS and the CPS-TBDMT template creation for the CoverageArea TA list mapping : CPS APIs.txt

Kindly check this page for more details on CPS APIs : R9 TBDMT Enhancements

4. CPS-TBDMT:

Follow the steps below to setup the CPS-TBDMT environment:

Clone the repo from : cps/cps-tbdmt · Gerrit Code Review (onap.org)
Build the project – mvn clean install
Change the docker image name to avoid docker login issues : docker tag nexus3.onap.org:10003/onap/cps-tbdmt:latest cps-tbdmt:latest
From the docker-compose folder, edit the application.yml file

cpsCoreConfiguration url – change to VM's IP and the created dataspace's name

schemaToAnchor mapping – provide the created schemaset and anchor name

From the docker-compose folder, run the following to bring up the containers : docker-compose up -d

5. Configure CPS in OOF deployment <WIP>

In oof/components/oof-has/values.yaml, provide the cps ip as the value for serviceName as below,

In oof/components/oof-has/resources/config/conductor.conf, change the server_url and get_ta_list_url as mentioned below,

After the configuration make OOF component and deploy it.

6. Policy changes for CoverageArea TA List Mapping: <WIP>

Add the below attribute in the NSI policies

"coverage_area_ta_list": {"derive_from":{"method":"get_tracking_area","args": {"coverage_area": {"get_param": "coverage_area_ta_list"}}}}