Skip to content

user_guide

Jump to bottom
themis edited this page Apr 7, 2020 · 1 revision

User Guide

Requirements

Install the Slice Manager on any Linux running system with the following software installed:

  • docker version >= 18.09.6
  • docker-compose version >= 1.17.1

Install Katana

To install katana download the katana repository and run the ./install.sh. Note that you need root privileges:

git clone https://github.com/medianetlab/katana-slice_manager.git
cd katana-slice-manager
sudo ./install.sh

This will build the necessary docker container images on the system. It will also install an application for using the katana CLI tool on the system.

Start katana

You can run katana with or without the web UI module. To start the katana slice manager without the web UI, run the ./start.sh. To start both katana and web UI, run the ./start-ui.sh. Note that you might need root privileges, depending on whether your user can run docker commands or not. This will initiate the container images that were built during the previous step.

Use katana

There are three ways to interact with Katana Slice Manager: (1) The Katana CLI tool, (2) REST APIs of NBI and (3) the Web UI.

Katana Admin Configuration

Before start using Katana for the management of network slices, the administrator of Katana has to execute some configuration steps:

  1. Register MANO layer components to the slice manager:
  • VIMs: Register the VIMs in each location of the platform that will be used in each location for hosting network services as part of network slices
  • NFVOs: Register the NFVOs in the platform that will be responsible for the management of the network services
  • WIM (Optional): Register the WIM in the platform that will be responsible for managing the Transport Network part of the Slice. If no WIM is added during a slice creation phase, the slice will still be created, but the Transport Network will not be configured
  • EMS (Optional): Register the EMSs that will be responsible for configuring the RAN functions that will be part of the Slice. If no EMS is added during a slice creation phase, the slice will still be created, but the RAN functions will not be configured
  • PDUs (Optional): Register the PDUs in the platform that will be used for hosting PNFs. It is mandatory to add a PDU if the slice includes the deployment of PNFs

Refer to SBI Documentation Page for details regarding how to configure Southbound components

  1. Add the network functions that are supported by the underlying platform infrastructure. These will be used during the Slice Mapping phase by the Slice Manager in order to map the slice requirements with the actual slices that are supported by the platform.

Refer to Supported Network Functions for further documentation

Slice Creation

Create a GST file based on the Generic network Slice Template and pass it to the slice manager via the CLI tool or the REST API to start the creation of a slice. Katana returns a slice ID for slice monitoring and management purposes.

Stop katana

Stop katana but keep the databases records with any associated data: ./stop.sh Stop katana and clear any associated data: ./clear.sh

Content

Clone this wiki locally