ONOSFW Release Notes¶

1. OPNFV Brahmaputra release note for onosfw¶

Table of Contents

OPNFV Brahmaputra release note for onosfw

1.1. Abstract¶

This document describes the testing scenario of onosfw project, including ONOS bare metal and virtual deployment scenario

1.2. License¶

OPNFV Brahmaputra release note for onosfw Docs (c) by Henry (HUAWEI)

OPNFV Brahmaputra release note for onosfw 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-02-14	0.0.1	Henry (HUAWEI)	First draft

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 Test Scenarios¶

For now, Openstack and ODL are using Centralized gateway to reach external network, but for ONOS, we are using DVR mode, which means we make each compute node has the ability to reach external network, just like pic below:

1.5.1. Secenario 14 ONOS-HA :¶

L2 feature

1.1 Infrastructure network setup; including CURD operation of bridge, interface, controller, port, etc.

1.2 L2 traffic between different subnets in same network

1.3 Traffic isolation between different tenants
L3 feature

2.1 L3 east - west function

2.1.1 Ping between VMs between differernt subnets belong to different tenants is OK

2.1.2 isolated by different networks belong to differernt tenants is OK

2.1.3 Related flow rule deleted when VM is deleted is OK

2.2 L3 south - north function

2.2.1. Ping external network (such as google) from VM by allocating a floating IP is OK

2.2.2. Binding an external port to OVS is OK

2.2.3. VM hot migration is supported

2.3 Improvements

2.3.1 Add p2any vxlan config to ovs is OK

2.3.2. Ovsdb support multiple nodes is OK

2.3.3. All nicira extension api has been extended

Revision:

Author:	Henry(jiangrui1@huawei.com)

Build date: October 20, 2016