1. ONOSFW User Guide Manaully

1.1. Abstract

This document describes the user guide instruction for onosfw project, including env setup and test case.

1.2. License

ONOSFW User Guide Manaully Docs (c) by Lucius (HUAWEI)

ONOSFW User Guide Manaully Docs are licensed under a Creative Commons Attribution 4.0 International License. You should have received a copy of the license along with this. If not, see <http://creativecommons.org/licenses/by/4.0/>.

1.3. Version history

Date Ver. Author Comment
2016-01-21 1.0.0 Lucius (HUAWEI) Rewritten for ONOSFW C release

1.4. Introduction

ONOSFW addresses integrating an SDN controller of choice based on a target applications or use cases within the OPNFV defined NFVI and VIM framework. It aims to provide end user and open source community with greater flexibility to build service applications, and to help leverage corresponding open source development efforts and results as well. Furthermore, it will create some common framework elements to address multi tenancy support, integration between the network controller and a DPI engine for context-based flow policies. It will also provide driver integration to support the Neutron ML2 & Router plugin.

1.5. ONOSFW User Guide Manaully

1.5.1. ONOSFW Environment Setup

  1. initialize environment:

initialize openstack:delete allthe network, instance and router.

initialize ovs:delete managerand bridge by the following command:

ovs-vsctl del-manager

ovs-vsctl del-br “bridge name”

  1. restart onos,install feature:

feature:install onos-openflow-base

feature:install onos-openflow

feature:install onos-ovsdatabase

feature:install onos-ovsdb-base

feature:install onos-drivers-ovsdb

feature:install onos-ovsdb-provider-host

feature:install onos-app-vtn-onosfw

  1. set the external port name:
onos command:externalportname-set –n “external port name”
  1. create provider network:
set manager on compute node and network node: ovs-vsctl set-manager tcp:“onos ip”:6640
  1. create basic networks and instances on openstack dashboard to verify L2/L3 function
  2. create basic scenarios to verify SFC functions.

1.5.2. Scenario Supported

  • L2 scene:

    • Live Migration
    • With between same node under the same tenant and network wether the vm is conneted
    • With between different nodes under the same tenant and network wether the vm is conneted
    • With between same node under the same tenant and different network wether the vm is not conneted
    • With between different nodes under the same tenant and different network wether the vm is not conneted
    • With between same nodes under the different tenant and different network wether the vm is not conneted
    • With between different nodes under the different tenant and different network wether the vm is not conneted
  • L3 scene:

    • With between same node under the same tenant and network wether the vm is conneted
    • With between different nodes under the same tenant and network wether the vm is conneted
    • With between same node under the same tenant and different network wether the vm is conneted
    • With between different nodes under the same tenant and different network wether the vm is conneted
    • With between same nodes under the different tenant and different network wether the vm is not conneted
    • With between different nodes under the different tenant and different network wether the vm is not conneted

    VM can ping external network well

  • SFC scene:

    • Create 3-4 VNF-nodes service chain, verify with traffic
    • Remove service chain, display service chain info
    • Insert a node(vnf) in the chain, and verify with traffic
    • Remove a node from the chain and verify with traffic
    • Get service chain status

1.5.3. ONOSFW Demo Video

ONOSFW L2 Function Flash video:https://www.youtube.com/watch?v=7bxjWrR4peI

ONOSFW L2 Function Demo video:https://www.youtube.com/watch?v=qP8nPYhz_Mo

ONOSFW L3 Function Demo video:https://www.youtube.com/watch?v=R0H-IibpVxw

ONOSFW SFC Function Demo video: https://www.youtube.com/watch?v=2vWusqd3WJ4

Revision:

Author:Lucius(lukai1@huawei.com)

Build date: August 12, 2016