ONOSFW Release Notes

1. ONOSFW User Guide

1.1. ONOSFW User Guide

1.1.1. Abstract

This user guide describes how to manually setup test environment for testing ONOSFW supported features.

1.1.2. License

1.1.3. Version history

Date Ver. Author Comment
2016-01-21 1.0.0 Lucius (HUAWEI) Rewritten for ONOSFW C release
2017-02-15 1.0.1 Bob (HUAWEI) For Danube 1.0
2017-02-15 1.0.2 Saravana (HUAWEI) For Danube 1.0

1.1.4. Introduction

ONOSFW integrats ONOS SDN controller for OPNFV defined NFVI and VIM framework.

In the Danube releases, all the previously ONOSFW supported features are updated to use Openstack Newton and ONOS Ibis. For auto-installation procedures, please refer to the installation document. Herethere is the manual setup instruction.

1.1.5. ONOSFW User Guide Manaully

1.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-optical-model

feature:install onos-providers-openflow-base

feature:install onos-providers-openflow-message

feature:install onos-providers-ovsdb-base

feature:install onos-drivers-ovsdb

feature:install onos-providers-ovsdb-host

feature:install onos-apps-vtn

  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
1.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.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

Revision:

Author:Lucius(lukai1@huawei.com)

Build date: July 15, 2017

Revision:

Author:Lucius(lukai1@huawei.com)

Build date: July 15, 2017

2. Configuration of ONOSFW

2.1. ONOSFW Installation Guide for the OPNFV Danube Release

2.1.1. Abstract

This document describes how to use various OPNFV installers to install and configure OPNFV Danube release with ONOS as the SDN controller. It also outlines the system resource requirements, dependencies and limitations.

2.1.2. License

Using Installers to Deploy ONOSFW for OPNFV Danube Release (c) by Lucius (HUAWEI)

The Using Installers to Deploy ONOSFW for OPNFV Danube Release document is 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/>.

2.1.3. Version history

Date Ver. Author Comment
2016-08-11 0.0.1 Lucius (HUAWEI) First draft
2017-02-15 1.0.0 Bob (HUAWEI) For Danube 1.0
2017-03-31 1.0.1 Saravana (HUAWEI) For Danube 1.0

2.1.4. Introduction

ONOSFW can be deployed on OPNFV Danube Releases using several installers. Each installer has its own system requirements and configuration procedures. The following table lists the basic system requirements when installing ONOSFW using each of the supported installers.

Apex Compass
Virtual CentOS 7, ONOS with OpenStack neutron-l3-agent being disabled Virtual Ubuntu 14, ONOS with OpenStack neutron-l3-agent being disabled
NA BM Ubuntu 14, ONOS with OpenStack neutron-l3-agent being disabled

Below are the detail configuration procedures for each installer:

2.1.5. Installer Configuration

2.1.5.1. Apex Configuration for ONOS

  1. Resource Requirements

    1.1 CentOS 7 (from ISO or self-installed).

    1.2 Root access.

    1.3 libvirt virtualization support.

    1.4 minimum 2 networks and maximum 6 networks, multiple NIC and/or VLAN combinations are supported. This is virtualized for a VM deployment.

    1.5 The Danube Apex RPM.

    1.6 16 GB of RAM for a bare metal deployment, 56 GB of RAM for a VM deployment.

  2. How to add ONOS into Apex

    2.1 Apex will download two images instack.qcow2 and overcloud-full.qcow2 to build Apex rpm. The instack.qcow2 is used for installation of instack virtual machine. The overcloud-full.qcow2 is used for installation of openstack nodes. The opnfv-tripleo-heat-templates.patch will update tripleo-heat scripts in instack.qcow2. And it will call puppet deployment scripts in overcloud-full.qcow2 to finish deployment. Those two files will be patch up and store into the two images during Apex rpm building process in instack.sh.

    Below is the directory Structure:

    ├── build
│   ├── overcloud-onos.sh   # add ONOS build steps
│   ├── opnfv-tripleo-heat-templates.patch   # add ONOS deployment scripts
│
├── ci
│   └── deploy.sh   #add ONOS build steps inside

    2.2 Upload puppet-onos to github for Apex iso/rpm building.

  3. Virtual deployment

    3.1 Install jumphost.

    3.3 Execute sudo opnfv-deploy –virtual [ –no-ha ] -d /etc/opnfv-apex/os-onos-nofeature-ha.yaml -n /etc/opnfv-apex/network_settings.yaml

  4. Baremetal deployment

    4.1 Install jumphost.

    4.3 Edit /etc/apex-opnfv/inventory.yaml and change mac_address, ipmi_ip, ipmi_user, ipmi_password etc base on your physical server and network.

    4.4 Execute sudo opnfv-deploy -d /etc/opnfv-apex/os-onos-nofeature-ha.yaml -i /etc/apex-opnfv/inventory.yaml -n /etc/opnfv-apex/network_settings.yaml

  5. Detail of Apex installation Apex Installation.

2.1.5.2. Compass Configuration for ONOS

  1. Resource Requirements

    1.1 Ubuntu Server 14.04 LTS 64-bit (from ISO or self-installed).

    1.2 16 GB of RAM for a Bare Metal deployment, 64 GB of RAM for a VM deployment.

    1.3 Root access.

    1.4 libvirt virtualization support.

    1.5 Minimum 2 NIC Card.PXE installation Network,IPMI Network,External Network (Optional: Internet access)

    1.6 At least 100GB disk space.

    1.7 The ONOS version 1.8.4.

  2. How to add ONOS into compass

    2.1 The ONOS installaion script is added into the compass4nfv project. and the onos will be started when compass calls the onos script. the script is included in the directory of compass4nfv project below:

    commpass4nfv
   ├── deploy
   │   ├── adapters
   │       ├── ansible
   │              ├── roles # include the sdn script
   │                 ├── onos_cluster # include the ONOS script
   │                     ├── handlers # include the opertaion of restart ONOS service
   │                     ├── tasks # include the task of installing ONOS
   │                     ├── templates # include the templates of ONOS
   │                     ├── vars # include the var of ONOS used
   │                     ├── files # include the files of ONOS used

  3. Virtual deployment

    3.1 Install jumphost

    3.2 Build ISO image of compass. Execute ./build.sh

    3.3 If onos_nofeature: Execute ./deploy.sh –dha /home/compass4nfv/deploy/conf/vm_environment/os-onos-nofeature-ha.yml

    –network /home/compass4nfv/deploy/conf/vm_environment/huawei-virtual1/network_onos.yml –iso-url file:///home/compass4nfv/work/building/compass.iso

  4. Baremetal deployment

    4.1 Install jumphost

    4.2 Build ISO image of compass. Execute ./build.sh

    4.3 Config the envionment variables

    export WORKSPACE=”/home/jenkins/jenkins-slave/workspace/compass-deploy-bare-huawei-us-master”

    export BUILD_DIRECTORY=$WORKSPACE/build_output

    export CONFDIR=$WORKSPACE/deploy/conf/hardware_environment/huawei-pod1

    export ISO_URL=file://$BUILD_DIRECTORY/compass.iso

    export EXTERNAL_NIC=eth0

    export INSTALL_NIC=eth1

    export OS_VERSION=xenial

    export OPENSTACK_VERSION=newton

    4.4 Execute cd $WORKSPACE

    4.5 If onos_nofeature Execute ./deploy.sh –dha $CONFDIR/os-onos-nofeature-ha.yml –network $CONFDIR/network_onos.yml –iso-url file:///home/compass4nfv/work/building/compass.iso

  5. For the details of compass installation `Compass Installation`_.

Revision:

Author:Lucius(lukai1@huawei.com)

Build date: July 15, 2017

Revision:

Author:Lucius(lukai1@huawei.com)

Build date: July 15, 2017

Revision:

Author:Lucius(lukai1@huawei.com)

Build date: July 15, 2017