Page Comparison

The document describes the step by step procedure to setup E2E network slicing use case demo setup for Guilin.

1. SDC: 

ONAP Portal: https://portal.api.simpledemo.onap.org:30225/ONAPPORTAL/login.htm (Username:cs0008, Password:demo123456!)

SDC UUI: https://sdc.api.fe.simpledemo.onap.org:30207/sdc1/portal#!/dashboard

Refer for Template Design for Option 1 respective template creation and distribution.

2.UUI Configuration:

Configure CST template UUID and Invariant UUID in slicing.properties file of uui-server microservice

...

curl --user AAI:AAI -X PUT -H "X-FromAppId:AAI" -H  "X-TransactionId:get_aai_subscr" -H "Accept:application/json" -H "Content-Type:application/json" -k https://<worker-vm-ip>:30233/aai/v21/business/customers/customer/5GCustomer/service-subscriptions/service-subscription/5G 

8. Ran-sim Setup steps:

Refer RAN-Sim setup to setup RAN-simulator

Refer RAN-Sim for ransim impacts done for Guilin Release

...

/service-subscription/5G 

8. Ran-sim Setup steps:

Refer RAN-Sim setup to setup RAN-simulator

Refer RAN-Sim for ransim impacts done for Guilin Release

9. Honeycomb:

Repo URL: https://github.com/onap-oof-pci-poc/ran-sim

Build Steps:

If there is a new yang model, build the gnbsim-api with new yang model

Step 1: copy the new yang model to ~/ran-sim/hcsim-content/gnbsim/ransim_rannetwork/ransim/gnbsim/gnbsim-api/src/main/yang
Step 2: Go to directory ~/ran-sim/hcsim-content/gnbsim/ransim_rannetwork/ransim/gnbsim/gnbsim-api/
Step 3: Issue the build command "JAVA_HOME=/usr/lib/jvm/java-1.11.0-openjdk-amd64 mvn clean install -Dcheckstyle.skip"

For code changes in gnbsim-impl directory

Step 1: Do necessary code changes in gnbsim-impl
Step 2: Issue the build command "JAVA_HOME=/usr/lib/jvm/java-1.11.0-openjdk-amd64 mvn clean install -Dcheckstyle.skip"

Once the mvn build is done, build the docker image

Step 1: Go to directory ~/ran-sim/hcsim-content/gnbsim/ransim_rannetwork/ransim/gnbsim/gnbsim-distribution/target/gnbsim-distribution-1.19.08-SNAPSHOT-hc/gnbsim-distribution-1.19.08-SNAPSHOT
Step 2: copy the Dockerfile
cp ~/ran-sim/hcsim-content/gnbsim/ransim_rannetwork/ransim/gnbsim/packages/Dockerfile .
Step 3: Do the docker build
docker build -t gnbsim .

Cross check the docker image
docker images | grep gnbsim

To run the Netconf Servers:

Run the below command from ~/gnbsim/ransim_rannetwork/hc directory.

docker-compose up -d

For slicing setup, 12 netconf servers are required. Copy the hc directory 11 more time and rename it.

Change the external port in the docker-compose files for every netconf server.

While running the docker-compose up -d command, these servers will be mounted in SDNC. 

10.ConfigDB:

Config DB is a spring boot application that works with mariaDB. DB schema details are available at Config DB.

Install config DB application in a separate VM. MariaDB container should be up and running to access the config DB APIs.

Refer https://wiki.onap.org/display/DW/Config+DB+setup for configDB setup.

...

11. Core NF Simulator Setup

Refer Core NF Simulator setup to setup Core NF Simulator.

...

12. SDNC:

Install SDNC using OOM charts and the below pods should be running.

...

Refer SDN-R_impacts for Dmaaps messages that can be used as an SDN-R input for RAN slice instantiation, modification, activation, deactivation and termination.

...

13. VES Collector

VES collector receives the PM data from RAN simulator and posts it in message router.

...

{
	"event": {
		"commonEventHeader": {
			"version": "4.0.1",
			"vesEventListenerVersion": "7.0.1",
			"domain": "notification",
			"eventName": "Notification_RnNode-Slicing_FileReady",
			"eventId": "FileReady_1797490e-10ae-4d48-9ea7-3d7d790b25e1",
			"lastEpochMicrosec": 8745745764578,
			"priority": "Normal",
			"reportingEntityName": "cucpserver2",
			"sequence": 0,
			"sourceName": "cucpserver2",
			"startEpochMicrosec": 8745745764578,
			"timeZoneOffset": "UTC+05.30"
		},
		"notificationFields": {
			"changeIdentifier": "PM_MEAS_FILES",
			"changeType": "FileReady",
			"notificationFieldsVersion": "2.0",
			"arrayOfNamedHashMap": [{
				"name": "A2021-01-15T05-46-30.387-2021-01-15T05-46-30.387-7836-cucpserver2.bin.gz",
				"hashMap": {
					"location": "ftpes://192.168.0.101:22/ftp/rop/A2021-01-15T05-46-30.387-2021-01-15T05-46-30.387-7836-cucpserver2.bin.gz",
					"compression": "gzip",
					"fileFormatType": "org.3GPP.32.435#measCollec",
					"fileFormatVersion": "V10"
				}
			}]
		}
	}
}

...

14. Datafile Collector

Datafile Collector reads the File Ready VES notifications from the message router. It fetches the PM file from the simulator using the FTP/SFTP location in the notification and places it in the data router. PM Mapper reads this PM file (xml format).

Refer DataFile Collector (5G Usecase) for the set up

...

15. PM Mapper

PM Mapper should be in running state.

...

Refer PM-Mapper (5G Usecase) for PM Mapper set up.

...

16. Slice Analysis MS

Refer DCAE R7 Slice Analysis MS (Network Slicing Usecase) for Slice Analysis MS set up.

...

17. Policies for Slice Analysis MS:

Execute these curl requests from any of the running pods.

...