Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The document describes the steps that can be used These sub pages describe the procedure to setup E2E network slicing use case demo setup for Guilin.

1. SDC: 

Steps for creating Service Templates:

View file
nameR7 Option 1 Templates.zip
height150

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 Design Service Templates for respective template creation and distribution.

It need to be created according to this diagram and to the templates description.

Add the properties according to the template description

2. SO:

Copy subnetCapabilities.json to SO-API Handler pod, Refer https://gerrit.onap.org/r/c/so/+/114735/1/mso-api-handlers/mso-api-handler-infra/src/test/resources/Onap3gppServiceInstancesTest/subnetCapability.json for sample subnet Capabilities file

Code Block
languagebash
themeEmacs
kubectl cp subnetCapabilities.json -n onap <so-apih-pod-name>:/app

2. Policy Creation Steps

Refer Optimization Policy Creation Steps for optimization policy creation and deployment steps

Refer Policy Models and Sample policies - NSI selection for sample policies 

NOTE:

...

You need to restart the OOF docker container once you updated the slicing_config.yaml, you can do it using the following steps,

Template Design for Option 1

This page explains the steps to be followed to create the templates needed for supporting option 1 deployment.

Manual Configurations

This page covers the configuration to be taken in various ONAP components after the installation.

Core & RAN Simulators

This page contains the reference to set up the simulators for E2E network slicing use case.

ClosedLoop Setup

This page is contains the reference for additional ONAP components that are needed to support closed loop.

  • Login to the worker VM where the OOF container is running. You can find the worker node by running (kubectl get pods -n onap -o wide | grep dev-oof)
  • Find the container using docker ps | grep optf-osdf
  • Restart the container using docker restart <container id>

3. Ransim Setup steps:

Refer RAN-Sim setup to setup RAN-simulator

Refer RAN-Sim for ransim impacts done for Guilin Release

...