From 9e22c6f8da4ad0306503fb5b4de7d4379f2169ee Mon Sep 17 00:00:00 2001 From: Sofia Wallin Date: Fri, 19 Aug 2016 14:03:47 +0200 Subject: Adjusted the document structure Adjusted the document structure in accordance to the docs teams directives. I have also adjusted some of the files names and the licence text to get consistency. Change-Id: I3503b3026c8035af4058dc41dbe7afefcc1a4e5b Signed-off-by: Sofia Wallin --- docs/Colorado/design/index.rst | 13 - docs/Colorado/installationprocedure/index.rst | 15 - .../installation.instruction.rst | 324 --------------------- docs/Colorado/release/index.rst | 15 - docs/Colorado/release/onos-release.rst | 112 ------- docs/Colorado/scenario description/index.rst | 15 - .../scenario description/scenario-description.rst | 106 ------- docs/Colorado/userguide/feature.usage.rst | 147 ---------- docs/Colorado/userguide/index.rst | 15 - docs/design/index.rst | 13 + .../feature.configuration.rst | 324 +++++++++++++++++++++ docs/installationprocedure/index.rst | 15 + docs/release/index.rst | 15 + docs/release/onos-release.rst | 112 +++++++ docs/releasenotes/index.rst | 15 + docs/releasenotes/scenario-description.rst | 97 ++++++ docs/userguide/feature.userguide.rst | 143 +++++++++ docs/userguide/index.rst | 15 + 18 files changed, 749 insertions(+), 762 deletions(-) delete mode 100644 docs/Colorado/design/index.rst delete mode 100644 docs/Colorado/installationprocedure/index.rst delete mode 100644 docs/Colorado/installationprocedure/installation.instruction.rst delete mode 100644 docs/Colorado/release/index.rst delete mode 100644 docs/Colorado/release/onos-release.rst delete mode 100644 docs/Colorado/scenario description/index.rst delete mode 100644 docs/Colorado/scenario description/scenario-description.rst delete mode 100644 docs/Colorado/userguide/feature.usage.rst delete mode 100644 docs/Colorado/userguide/index.rst create mode 100644 docs/design/index.rst create mode 100644 docs/installationprocedure/feature.configuration.rst create mode 100644 docs/installationprocedure/index.rst create mode 100644 docs/release/index.rst create mode 100644 docs/release/onos-release.rst create mode 100644 docs/releasenotes/index.rst create mode 100644 docs/releasenotes/scenario-description.rst create mode 100644 docs/userguide/feature.userguide.rst create mode 100644 docs/userguide/index.rst diff --git a/docs/Colorado/design/index.rst b/docs/Colorado/design/index.rst deleted file mode 100644 index e3123080..00000000 --- a/docs/Colorado/design/index.rst +++ /dev/null @@ -1,13 +0,0 @@ -********************************************* -OPNFV(Colorado) ONOSFW design instructions -********************************************* - -.. toctree:: - :numbered: - :maxdepth: 4 - -Revision: _sha1_ - -:Author: Lucius(lukai1@huawei.com) - -Build date: |today| diff --git a/docs/Colorado/installationprocedure/index.rst b/docs/Colorado/installationprocedure/index.rst deleted file mode 100644 index 9088eb59..00000000 --- a/docs/Colorado/installationprocedure/index.rst +++ /dev/null @@ -1,15 +0,0 @@ -********************************************* -OPNFV(Colorado) ONOSFW config instructions -********************************************* - -.. toctree:: - :numbered: - :maxdepth: 4 - - installation.instruction.rst - -Revision: _sha1_ - -:Author: Lucius(lukai1@huawei.com) - -Build date: |today| diff --git a/docs/Colorado/installationprocedure/installation.instruction.rst b/docs/Colorado/installationprocedure/installation.instruction.rst deleted file mode 100644 index 129fd33b..00000000 --- a/docs/Colorado/installationprocedure/installation.instruction.rst +++ /dev/null @@ -1,324 +0,0 @@ -=========================================================================================================== -OPNFV config guide instructions for the Colorado release of OPNFV when using installers to deploy onosfw -=========================================================================================================== - -.. contents:: Table of Contents - :backlinks: none - - -Abstract -======== - -This document describes how to config the Colorado release of OPNFV when -using installers as a deployment tool to deploy onosfw, covering it's limitations, dependencies -and required system resources. - -License -======= - -Colorado release of OPNFV when using installers to deploy onosfw Docs -(c) by Lucius (HUAWEI) - -Colorado release of OPNFV when using installers to deploy 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 . - -Version history -=============== - -+------------+----------+------------+------------------+ -| **Date** | **Ver.** | **Author** | **Comment** | -| | | | | -+------------+----------+------------+------------------+ -| 2016-08-11 | 0.0.1 | Lucius | First draft | -| | | (HUAWEI) | | -+------------+----------+------------+------------------+ - -Introduction -============ - -ONOSFW need to deploy with several installers and each installer have differernt configs. Here is the scenarios ONOSFW need to supported - -+-----------------------------------------+-----------------------------------------+-----------------------------------------+-----------------------------------------+ -| Apex | Compass | Fuel | JOID | -+=========================================+=========================================+=========================================+=========================================+ -| Virtual CentOS 7, ONOS with OpenStack | Virtual Ubuntu 14, ONOS with OpenStack | Virtual Ubuntu 14, ONOS with OpenStack | Virtual Ubuntu 14, ONOS with OpenStack | -| neutron-l3-agent being disabled | neutron-l3-agent being disabled | neutron-l3-agent being disabled | neutron-l3-agent being disabled | -+-----------------------------------------+-----------------------------------------+-----------------------------------------+-----------------------------------------+ -| NA | BM Ubuntu 14, ONOS with OpenStack | NA | NA | -| | neutron-l3-agent being disabled | | | -+-----------------------------------------+-----------------------------------------+-----------------------------------------+-----------------------------------------+ -Below is the detail configuration for them: - -Config for Installers -===================== - -Config Documentation for ONOS with Apex ---------------------------------------- -1. Pyhsical 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 Colorado 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 when 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:: - - ├── 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.2 Edit /etc/opnfv-apex/deploy_settings.yaml and change ODL into ONOS. - - 3.3 Execute sudo opnfv-deploy --virtual [ --no-ha ] -d /etc/opnfv-apex/deploy_settings.yaml -n /etc/opnfv-apex/network_settings.yaml - -4. Baremetal deployment - - 4.1 Install jumphost. - - 4.2 Edit /etc/opnfv-apex/deploy_settings.yaml and change ODL into ONOS. - - 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/deploy_settings.yaml -i /etc/apex-opnfv/inventory.yaml -n /etc/opnfv-apex/network_settings.yaml - -5. Detail of Apex installation `Apex Installation`_. - -.. _Apex Installation : http://artifacts.opnfv.org/apex/docs/installation-instructions/ - -Config Documentation for ONOS with Compass ------------------------------------------- -1. Pyhsical Requirements for install ONOS - - 1.1 Ubuntu Server 14.04 LTS 64-bit (from ISO or self-installed). - - 1.2 minimum 2GB RAM. - - 1.3 minimum 2 processors. - - 1.4 At least 5GB disk space. - - 1.5 The ONOS version 1.4. - -2. How to add ONOS into compass - - 2.1 the script that install ONOS service 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 - │   ├── openstack_mitaka - │ ├── 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 - -3. Virtual deployment - - 3.1 Install jumphost - - 3.2 Build ISO image of compass. Execute ./build.sh - - 3.3 If onos_sfc: 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 - If onos_nofeature: Execute ./deploy.sh --dha /home/compass4nfv/deploy/conf/vm_environment/os-onos-sfc-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=trusty - - export OPENSTACK_VERSION=mitaka - - 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 - - 4.6 If onos_sfc Execute ./deploy.sh --dha $CONFDIR/os-onos-sfc-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`_. - -.. Compass Installation : http://artifacts.opnfv.org/compass4nfv/docs/configguide/installerconfig.html - - -Config Documentation for ONOS with Fuel ---------------------------------------- -1. Pyhsical Requirement - - 1.1 Linux , Microsoft or Mac OS. - - 1.2 Root access or admin access. - - 1.3 libvirt virtualization support. - - 1.4 minimum 2 networks and maximum 4 networks, multiple NIC and/or VLAN combinations are supported. - - 1.5 600G disk at least for no-ha virtual deployment - -2. How to add ONOS into Fuel - 2.1 Fuel provides an intuitive, GUI-driven experience for deployment and management of OpenStack, related community projects and plug-ins. Onos supplies plug-in to manage network of L2/L3 and SFC. - below is the directory:: - - ├── build - │ ├──f_isoroot - │ ├── f_onosfwpluginbuild # add ONOS build url - │ - ├── deploy - │ ├──scenario - │ ├── ha-onos_scenario.yaml # add ONOS ha configuration - │ ├── noha-onos_scenario.yaml # add ONOS noha configuration - │ ├── sfc-onos-ha_scenario.yaml # add ONOS sfc ha configuration - │ ├── sfc-onos-noha_scenario.yaml # add ONOS sfc noha configuration - ├── ci - │ └── deploy.sh #add ONOS scenarion steps inside - - 2.2 Upload fuel-plugin-onos to git for fuel iso/rpm building. - -3. Automatic deployment - - 3.1 Install jumphost and download fuel.iso with ONOS plugin. - - 3.2 git clone https://gerrit.opnfv.org/gerrit/fuel - - 3.3 In fuel/ci, exec ./deploy.sh. For virtual deployment, you can use -b file:///fuel/deploy/config -l devel-popeline -p huawei-ch -s os-onos-sfc-ha -i file://root/iso/fuel.iso. Fore bare metal deployment, modify dha.yaml according to hardware configuration. - -4. Build ONOS plugin into rpm independently. - - 4.1 Install fuel plugin builder( detailed steps can be found in https://wiki.openstack.org/wiki/Fuel/Plugin ). - - 4.2 git clone git://git.openstack.org/openstack/fuel-plugin-onos. For Mitaka deployment, use –b Mitaka. - - 4.3 fpb --build fuel-plugin-onos - - 4.4 Move onos*.rpm in to master and fuel plugins –install onos*.rpm. - - 4.5 Create a new environment and select onos plugin in settings table. As a constraint, you need to select public_network_assignment in network configuration. In addition, if you want to try SFC feature, select ''SFC feature'. - - 4.6 Select a node with the role of controller and ONOS(ONOS must collocate with a controller). - - 4.7 Deploy changes. - -5. Related url for Fuel and ONOS. - - Fuel: https://wiki.openstack.org/wiki/Fuel - - Fuel plugin: https://wiki.openstack.org/wiki/Fuel/Plugins - - Fuel codes: https://gerrit.opnfv.org/gerrit/fuel - - Fuel iso: http://build.opnfv.org/artifacts/ - - Fuel-plugin-onos: http://git.openstack.org/cgit/openstack/fuel-plugin-onos/ - - -Config Documentation for ONOS with JOID ---------------------------------------- - -1、Virtual Machine Deployment - - 1.1、 Hardware Requirement: - OS: Ubuntu Trusty 14.04 LTS - - Memory: 48 GB + - - CPU: 24 cores + - - Hard disk: 1T - - 1.2、Get the joid code from gerrit https://gerrit.opnfv.org/gerrit/p/joid.git - - 1.3、Suggest to create a user ubuntu and use this user, if not,you should edit the file：joid/ci/maas/default/deployment.yaml. Find Virsh power settings and change ubuntu to your own user name. - - 1.4、Deploy Maas - $ cd joid/ci/ - $ ./02-maasdeploy.sh - - 1.5、Deploy OPNFV: - For liberty openstack, ONOS SDN, HA mode - $ ./deploy.sh -o mitaka -s onos -t ha -f sfc -d trusty - -2、Bare Metal Deployment - - 2.1、Pre Requisite: - - 1. have a single node install with Ubuntu OS 14.04 LTS - - 2. Minimum four nodes are needed and they should be preconfigured and integrated with JOID, please refer to this wiki page https://wiki.opnfv.org/joid/get_started - - 2.2、Get the joid code from gerrit : https://gerrit.opnfv.org/gerrit/p/joid.git - - 2.3、Suggest to create a user ubuntu and use this user, if not,you should edit the file：joid/ci/maas/default/deployment.yaml. - Find Virsh power settings and change ubuntu to your own user name. - - 2.4、Deploy MAAS: - - $ ./02-maasdeploy.sh - - 2.5、Deploy OPNFV: - - For liberty openstack, ONOS SDN, HA mode in intel pod5 - $ ./deploy.sh -o liberty -s onos -t ha -f sfc -d trusty -l intelpod5 - -3、How to add ONOS into joid - -create a dir ONOS as below:: - - --onos - ├── 01-deploybundle.sh # deploy bundle define - ├── juju-deployer - │ ├── ovs-onos-ha.yaml # openstack type ha feature define - │ ├── ovs-onos-nonha.yaml # openstack type nosha feature define - │ ├── ovs-onos-tip.yaml # openstack type tip feature define - ├── openstack.sh # create ext-net - ├── config_tpl/bundle_tpl - │ ├── onos.yaml # set ONOS config option - │ ├── subordinate.yaml # set openvswitch-onos config option - └── README # description - -Revision: _sha1_ - -:Author: Lucius(lukai1@huawei.com) - -Build date: |today| diff --git a/docs/Colorado/release/index.rst b/docs/Colorado/release/index.rst deleted file mode 100644 index e3b0bdb2..00000000 --- a/docs/Colorado/release/index.rst +++ /dev/null @@ -1,15 +0,0 @@ -******************** -ONOSFW Release Notes -******************** - -.. toctree:: - :numbered: - :maxdepth: 4 - - onos-release.rst - -Revision: _sha1_ - -:Author: Lucius(lukai1@huawei.com) - -Build date: |today| diff --git a/docs/Colorado/release/onos-release.rst b/docs/Colorado/release/onos-release.rst deleted file mode 100644 index 540dd597..00000000 --- a/docs/Colorado/release/onos-release.rst +++ /dev/null @@ -1,112 +0,0 @@ -========================================= -OPNFV Colorado release note for onosfw -========================================= - -.. contents:: Table of Contents - :backlinks: none - - -Abstract -======== - -This document describes the release note of onosfw project, including upstream project ONOS and OpenStack - -License -======= - -<<<<<<< HEAD:docs/Colorado/release/onos-release.rst -OPNFV Colorado release note for onosfw Docs -======= -OPNFV Colorado release note for onosfw Docs ->>>>>>> 061216d... DOCS-84:docs/Colorado/release/onos-release.rst -(c) by Lucius (HUAWEI) - -OPNFV Colorado 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 . - -Version history -=============== - -+------------+----------+------------+------------------+ -| **Date** | **Ver.** | **Author** | **Comment** | -| | | | | -+------------+----------+------------+------------------+ -| 2016-08-11 | 0.0.1 | Lucius | First draft | -| | | (HUAWEI) | | -+------------+----------+------------+------------------+ - -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. - - - -ONOSFW Test Scenarios -===================== - -+---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------+ -| FuncTest Usecase \ Installers | Apex | Compass | Fuel | JOID | -+=======================================+===========================================+===========================================+===========================================+============================================================+ -| vPing For user metadata | Success | Success | Success | Success | -| | | | | -| -+---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------+ -| vPing | Success | Success | Success | Success | -| | | | | | -+---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------+ -| tempest | Success | Success | Success | Success | -| | | | | | -+---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------+ -| VIMS | NR | NR | NR | NR | -| | | | | | -+---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------+ -| RALLY | Success | Success | Success | Success | -| | | | | | -+---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------+ -| ONOS | Success | Success | Success | Success | -| | | | | | -+---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------+ -| ONOS_SFC | Success | Success | Success | Success -| -| | | | | | -+---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------ - -ONOS Release -============ -ONOS wiki of onosfw : `onosfw proposal in ONOS`_. - -.. _onosfw proposal in ONOS: https://wiki.onosproject.org/login.action?os_destination=%2Fdisplay%2FONOS%2FONOS%2BFramework%2B%28ONOSFW%29%2Bfor%2BOPNFV - -ONOS Goldeneye code:`ONOS Goldeneye Code`_. - -.. _ONOS Goldeneye Code: https://github.com/opennetworkinglab/onos/tree/onos-1.6 - -ONOS Goldeneye Release Note `ONOS Goldeneye Release Note`_. - -.. _ONOS Goldeneye Release Note: https://wiki.onosproject.org/display/ONOS/Goldeneye+Release+Notes - -The APIs docs exist as a submodule in docs/apis. -In order to retrieve them, you must change directories to "apis" and then do a "git pull origin master". -This will pull down all relevant API documents related to the source components in this release". -here is api link: https://github.com/onosfw/apis - -OpenStack Release -================= - -OpenStack Mitaka wiki page `OpenStack Mitaka wiki`_. - -.. _OpenStack Mitaka wiki : https://wiki.openstack.org/wiki/Main_Page - -OpenStack Liberty api page `OpenStack Networking Api`_. - -.. _OpenStack Networking Api : http://developer.openstack.org/api-ref-networking-v2-ext.html - - -Revision: _sha1_ - -:Author: Lucius(lukai1@huawei.com) - -Build date: |today| diff --git a/docs/Colorado/scenario description/index.rst b/docs/Colorado/scenario description/index.rst deleted file mode 100644 index e39d0220..00000000 --- a/docs/Colorado/scenario description/index.rst +++ /dev/null @@ -1,15 +0,0 @@ -******************** -ONOSFW Release Notes -******************** - -.. toctree:: - :numbered: - :maxdepth: 4 - - scenario-description.rst - -Revision: _sha1_ - -:Author: Lucius(lukai1@huawei.com) - -Build date: |today| diff --git a/docs/Colorado/scenario description/scenario-description.rst b/docs/Colorado/scenario description/scenario-description.rst deleted file mode 100644 index 9c167c70..00000000 --- a/docs/Colorado/scenario description/scenario-description.rst +++ /dev/null @@ -1,106 +0,0 @@ -========================================= -OPNFV Colorado release note for onosfw -========================================= - -.. contents:: Table of Contents - :backlinks: none - - -Abstract -======== - -This document describes the testing scenario of onosfw project, including ONOS bare metal and virtual deployment scenario - -License -======= - -<<<<<<< HEAD:docs/Colorado/scenario description/scenario-description.rst -OPNFV Colorado release note for onosfw Docs -======= -OPNFV Colorado release note for onosfw Docs ->>>>>>> 061216d... DOCS-84:docs/Colorado/scenario description/scenario-description.rst -(c) by Lucius (HUAWEI) - -OPNFV Colorado 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 . - -Version history -=============== - -+------------+----------+------------+------------------+ -| **Date** | **Ver.** | **Author** | **Comment** | -| | | | | -+------------+----------+------------+------------------+ -| 2016-08-11 | 0.0.1 | Lucius | First draft | -| | | (HUAWEI) | | -+------------+----------+------------+------------------+ - -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. -In the Colorado release, in addition to the features in the Brahmaputra release, ONOSFW has included more functions in the Goldeneys of ONOS, and added service Function Chaining scenario by integrating the networking-sfc capability of openstack. -Therefore, both features and scenarios configurations are described. - -ONOSFW Test Scenarios -===================== - -Currently Openstack and ODL are using Centralized gateway to reach external network.ONOS takes a different approach, it uses DVR mode, where each compute node has the ability to reach external network, as illustrated below: - -.. image:: /etc/ONOS-DVR.png - - -Secenario 14 ONOS-HA : ----------------------- -1. 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 - -2. 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 - -3. SFC feature - - 3.1 Infrastructure CURD operation of SFC. - - 3.2 traffic through SFC - - -Revision: _sha1_ - -:Author: Lucius(lukai1@huawei.com) - -Build date: |today| diff --git a/docs/Colorado/userguide/feature.usage.rst b/docs/Colorado/userguide/feature.usage.rst deleted file mode 100644 index 6c20843e..00000000 --- a/docs/Colorado/userguide/feature.usage.rst +++ /dev/null @@ -1,147 +0,0 @@ -========================== -ONOSFW User Guide Manaully -========================== - -.. contents:: Table of Contents - :backlinks: none - - -Abstract -======== - -This document describes the user guide instruction for onosfw project, including env setup and test case. - -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 . - -Version history -=============== - -+------------+----------+------------+------------------+ -| **Date** | **Ver.** | **Author** | **Comment** | -| | | | | -+------------+----------+------------+------------------+ -| 2016-01-21 | 1.0.0 | Lucius | Rewritten for | -| | | (HUAWEI) | ONOSFW C release | -+------------+----------+------------+------------------+ - -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. -In the Colorado release, in addition to the features in the Brahmaputra release, ONOSFW has included more functions in the Goldeneys of ONOS, and added service Function Chaining scenario by integrating the networking-sfc capability of openstack. -Therefore, both features and scenarios configurations are described. - -ONOSFW User Guide Manaully -========================== - -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” - - 2. 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 - - 3. set the external port name:: - - ONOS command：externalportname-set –n “external port name” - - 4. create provider network:: - - set manager on compute node and network node: ovs-vsctl set-manager tcp:“onos ip”:6640 - - 5. create basic networks and instances on openstack dashboard to verify L2/L3 function - - 6. create basic scenarios to verify SFC functions. - -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 - -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: _sha1_ - -:Author: Lucius(lukai1@huawei.com) - -Build date: |today| diff --git a/docs/Colorado/userguide/index.rst b/docs/Colorado/userguide/index.rst deleted file mode 100644 index 990b9077..00000000 --- a/docs/Colorado/userguide/index.rst +++ /dev/null @@ -1,15 +0,0 @@ -***************** -ONOSFW User Guide -***************** - -.. toctree:: - :numbered: - :maxdepth: 4 - - feature.usage.rst - -Revision: _sha1_ - -:Author: Lucius(lukai1@huawei.com) - -Build date: |today| diff --git a/docs/design/index.rst b/docs/design/index.rst new file mode 100644 index 00000000..e3123080 --- /dev/null +++ b/docs/design/index.rst @@ -0,0 +1,13 @@ +********************************************* +OPNFV(Colorado) ONOSFW design instructions +********************************************* + +.. toctree:: + :numbered: + :maxdepth: 4 + +Revision: _sha1_ + +:Author: Lucius(lukai1@huawei.com) + +Build date: |today| diff --git a/docs/installationprocedure/feature.configuration.rst b/docs/installationprocedure/feature.configuration.rst new file mode 100644 index 00000000..129fd33b --- /dev/null +++ b/docs/installationprocedure/feature.configuration.rst @@ -0,0 +1,324 @@ +=========================================================================================================== +OPNFV config guide instructions for the Colorado release of OPNFV when using installers to deploy onosfw +=========================================================================================================== + +.. contents:: Table of Contents + :backlinks: none + + +Abstract +======== + +This document describes how to config the Colorado release of OPNFV when +using installers as a deployment tool to deploy onosfw, covering it's limitations, dependencies +and required system resources. + +License +======= + +Colorado release of OPNFV when using installers to deploy onosfw Docs +(c) by Lucius (HUAWEI) + +Colorado release of OPNFV when using installers to deploy 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 . + +Version history +=============== + ++------------+----------+------------+------------------+ +| **Date** | **Ver.** | **Author** | **Comment** | +| | | | | ++------------+----------+------------+------------------+ +| 2016-08-11 | 0.0.1 | Lucius | First draft | +| | | (HUAWEI) | | ++------------+----------+------------+------------------+ + +Introduction +============ + +ONOSFW need to deploy with several installers and each installer have differernt configs. Here is the scenarios ONOSFW need to supported + ++-----------------------------------------+-----------------------------------------+-----------------------------------------+-----------------------------------------+ +| Apex | Compass | Fuel | JOID | ++=========================================+=========================================+=========================================+=========================================+ +| Virtual CentOS 7, ONOS with OpenStack | Virtual Ubuntu 14, ONOS with OpenStack | Virtual Ubuntu 14, ONOS with OpenStack | Virtual Ubuntu 14, ONOS with OpenStack | +| neutron-l3-agent being disabled | neutron-l3-agent being disabled | neutron-l3-agent being disabled | neutron-l3-agent being disabled | ++-----------------------------------------+-----------------------------------------+-----------------------------------------+-----------------------------------------+ +| NA | BM Ubuntu 14, ONOS with OpenStack | NA | NA | +| | neutron-l3-agent being disabled | | | ++-----------------------------------------+-----------------------------------------+-----------------------------------------+-----------------------------------------+ +Below is the detail configuration for them: + +Config for Installers +===================== + +Config Documentation for ONOS with Apex +--------------------------------------- +1. Pyhsical 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 Colorado 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 when 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:: + + ├── 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.2 Edit /etc/opnfv-apex/deploy_settings.yaml and change ODL into ONOS. + + 3.3 Execute sudo opnfv-deploy --virtual [ --no-ha ] -d /etc/opnfv-apex/deploy_settings.yaml -n /etc/opnfv-apex/network_settings.yaml + +4. Baremetal deployment + + 4.1 Install jumphost. + + 4.2 Edit /etc/opnfv-apex/deploy_settings.yaml and change ODL into ONOS. + + 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/deploy_settings.yaml -i /etc/apex-opnfv/inventory.yaml -n /etc/opnfv-apex/network_settings.yaml + +5. Detail of Apex installation `Apex Installation`_. + +.. _Apex Installation : http://artifacts.opnfv.org/apex/docs/installation-instructions/ + +Config Documentation for ONOS with Compass +------------------------------------------ +1. Pyhsical Requirements for install ONOS + + 1.1 Ubuntu Server 14.04 LTS 64-bit (from ISO or self-installed). + + 1.2 minimum 2GB RAM. + + 1.3 minimum 2 processors. + + 1.4 At least 5GB disk space. + + 1.5 The ONOS version 1.4. + +2. How to add ONOS into compass + + 2.1 the script that install ONOS service 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 + │   ├── openstack_mitaka + │ ├── 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 + +3. Virtual deployment + + 3.1 Install jumphost + + 3.2 Build ISO image of compass. Execute ./build.sh + + 3.3 If onos_sfc: 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 + If onos_nofeature: Execute ./deploy.sh --dha /home/compass4nfv/deploy/conf/vm_environment/os-onos-sfc-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=trusty + + export OPENSTACK_VERSION=mitaka + + 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 + + 4.6 If onos_sfc Execute ./deploy.sh --dha $CONFDIR/os-onos-sfc-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`_. + +.. Compass Installation : http://artifacts.opnfv.org/compass4nfv/docs/configguide/installerconfig.html + + +Config Documentation for ONOS with Fuel +--------------------------------------- +1. Pyhsical Requirement + + 1.1 Linux , Microsoft or Mac OS. + + 1.2 Root access or admin access. + + 1.3 libvirt virtualization support. + + 1.4 minimum 2 networks and maximum 4 networks, multiple NIC and/or VLAN combinations are supported. + + 1.5 600G disk at least for no-ha virtual deployment + +2. How to add ONOS into Fuel + 2.1 Fuel provides an intuitive, GUI-driven experience for deployment and management of OpenStack, related community projects and plug-ins. Onos supplies plug-in to manage network of L2/L3 and SFC. + below is the directory:: + + ├── build + │ ├──f_isoroot + │ ├── f_onosfwpluginbuild # add ONOS build url + │ + ├── deploy + │ ├──scenario + │ ├── ha-onos_scenario.yaml # add ONOS ha configuration + │ ├── noha-onos_scenario.yaml # add ONOS noha configuration + │ ├── sfc-onos-ha_scenario.yaml # add ONOS sfc ha configuration + │ ├── sfc-onos-noha_scenario.yaml # add ONOS sfc noha configuration + ├── ci + │ └── deploy.sh #add ONOS scenarion steps inside + + 2.2 Upload fuel-plugin-onos to git for fuel iso/rpm building. + +3. Automatic deployment + + 3.1 Install jumphost and download fuel.iso with ONOS plugin. + + 3.2 git clone https://gerrit.opnfv.org/gerrit/fuel + + 3.3 In fuel/ci, exec ./deploy.sh. For virtual deployment, you can use -b file:///fuel/deploy/config -l devel-popeline -p huawei-ch -s os-onos-sfc-ha -i file://root/iso/fuel.iso. Fore bare metal deployment, modify dha.yaml according to hardware configuration. + +4. Build ONOS plugin into rpm independently. + + 4.1 Install fuel plugin builder( detailed steps can be found in https://wiki.openstack.org/wiki/Fuel/Plugin ). + + 4.2 git clone git://git.openstack.org/openstack/fuel-plugin-onos. For Mitaka deployment, use –b Mitaka. + + 4.3 fpb --build fuel-plugin-onos + + 4.4 Move onos*.rpm in to master and fuel plugins –install onos*.rpm. + + 4.5 Create a new environment and select onos plugin in settings table. As a constraint, you need to select public_network_assignment in network configuration. In addition, if you want to try SFC feature, select ''SFC feature'. + + 4.6 Select a node with the role of controller and ONOS(ONOS must collocate with a controller). + + 4.7 Deploy changes. + +5. Related url for Fuel and ONOS. + + Fuel: https://wiki.openstack.org/wiki/Fuel + + Fuel plugin: https://wiki.openstack.org/wiki/Fuel/Plugins + + Fuel codes: https://gerrit.opnfv.org/gerrit/fuel + + Fuel iso: http://build.opnfv.org/artifacts/ + + Fuel-plugin-onos: http://git.openstack.org/cgit/openstack/fuel-plugin-onos/ + + +Config Documentation for ONOS with JOID +--------------------------------------- + +1、Virtual Machine Deployment + + 1.1、 Hardware Requirement: + OS: Ubuntu Trusty 14.04 LTS + + Memory: 48 GB + + + CPU: 24 cores + + + Hard disk: 1T + + 1.2、Get the joid code from gerrit https://gerrit.opnfv.org/gerrit/p/joid.git + + 1.3、Suggest to create a user ubuntu and use this user, if not,you should edit the file：joid/ci/maas/default/deployment.yaml. Find Virsh power settings and change ubuntu to your own user name. + + 1.4、Deploy Maas + $ cd joid/ci/ + $ ./02-maasdeploy.sh + + 1.5、Deploy OPNFV: + For liberty openstack, ONOS SDN, HA mode + $ ./deploy.sh -o mitaka -s onos -t ha -f sfc -d trusty + +2、Bare Metal Deployment + + 2.1、Pre Requisite: + + 1. have a single node install with Ubuntu OS 14.04 LTS + + 2. Minimum four nodes are needed and they should be preconfigured and integrated with JOID, please refer to this wiki page https://wiki.opnfv.org/joid/get_started + + 2.2、Get the joid code from gerrit : https://gerrit.opnfv.org/gerrit/p/joid.git + + 2.3、Suggest to create a user ubuntu and use this user, if not,you should edit the file：joid/ci/maas/default/deployment.yaml. + Find Virsh power settings and change ubuntu to your own user name. + + 2.4、Deploy MAAS: + + $ ./02-maasdeploy.sh + + 2.5、Deploy OPNFV: + + For liberty openstack, ONOS SDN, HA mode in intel pod5 + $ ./deploy.sh -o liberty -s onos -t ha -f sfc -d trusty -l intelpod5 + +3、How to add ONOS into joid + +create a dir ONOS as below:: + + --onos + ├── 01-deploybundle.sh # deploy bundle define + ├── juju-deployer + │ ├── ovs-onos-ha.yaml # openstack type ha feature define + │ ├── ovs-onos-nonha.yaml # openstack type nosha feature define + │ ├── ovs-onos-tip.yaml # openstack type tip feature define + ├── openstack.sh # create ext-net + ├── config_tpl/bundle_tpl + │ ├── onos.yaml # set ONOS config option + │ ├── subordinate.yaml # set openvswitch-onos config option + └── README # description + +Revision: _sha1_ + +:Author: Lucius(lukai1@huawei.com) + +Build date: |today| diff --git a/docs/installationprocedure/index.rst b/docs/installationprocedure/index.rst new file mode 100644 index 00000000..3320215c --- /dev/null +++ b/docs/installationprocedure/index.rst @@ -0,0 +1,15 @@ +*********************** +Configuration of ONOSFW +*********************** + +.. toctree:: + :numbered: + :maxdepth: 4 + + feature.configuration.rst + +Revision: _sha1_ + +:Author: Lucius(lukai1@huawei.com) + +Build date: |today| diff --git a/docs/release/index.rst b/docs/release/index.rst new file mode 100644 index 00000000..e3b0bdb2 --- /dev/null +++ b/docs/release/index.rst @@ -0,0 +1,15 @@ +******************** +ONOSFW Release Notes +******************** + +.. toctree:: + :numbered: + :maxdepth: 4 + + onos-release.rst + +Revision: _sha1_ + +:Author: Lucius(lukai1@huawei.com) + +Build date: |today| diff --git a/docs/release/onos-release.rst b/docs/release/onos-release.rst new file mode 100644 index 00000000..540dd597 --- /dev/null +++ b/docs/release/onos-release.rst @@ -0,0 +1,112 @@ +========================================= +OPNFV Colorado release note for onosfw +========================================= + +.. contents:: Table of Contents + :backlinks: none + + +Abstract +======== + +This document describes the release note of onosfw project, including upstream project ONOS and OpenStack + +License +======= + +<<<<<<< HEAD:docs/Colorado/release/onos-release.rst +OPNFV Colorado release note for onosfw Docs +======= +OPNFV Colorado release note for onosfw Docs +>>>>>>> 061216d... DOCS-84:docs/Colorado/release/onos-release.rst +(c) by Lucius (HUAWEI) + +OPNFV Colorado 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 . + +Version history +=============== + ++------------+----------+------------+------------------+ +| **Date** | **Ver.** | **Author** | **Comment** | +| | | | | ++------------+----------+------------+------------------+ +| 2016-08-11 | 0.0.1 | Lucius | First draft | +| | | (HUAWEI) | | ++------------+----------+------------+------------------+ + +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. + + + +ONOSFW Test Scenarios +===================== + ++---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------+ +| FuncTest Usecase \ Installers | Apex | Compass | Fuel | JOID | ++=======================================+===========================================+===========================================+===========================================+============================================================+ +| vPing For user metadata | Success | Success | Success | Success | +| | | | | +| ++---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------+ +| vPing | Success | Success | Success | Success | +| | | | | | ++---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------+ +| tempest | Success | Success | Success | Success | +| | | | | | ++---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------+ +| VIMS | NR | NR | NR | NR | +| | | | | | ++---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------+ +| RALLY | Success | Success | Success | Success | +| | | | | | ++---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------+ +| ONOS | Success | Success | Success | Success | +| | | | | | ++---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------+ +| ONOS_SFC | Success | Success | Success | Success +| +| | | | | | ++---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------ + +ONOS Release +============ +ONOS wiki of onosfw : `onosfw proposal in ONOS`_. + +.. _onosfw proposal in ONOS: https://wiki.onosproject.org/login.action?os_destination=%2Fdisplay%2FONOS%2FONOS%2BFramework%2B%28ONOSFW%29%2Bfor%2BOPNFV + +ONOS Goldeneye code:`ONOS Goldeneye Code`_. + +.. _ONOS Goldeneye Code: https://github.com/opennetworkinglab/onos/tree/onos-1.6 + +ONOS Goldeneye Release Note `ONOS Goldeneye Release Note`_. + +.. _ONOS Goldeneye Release Note: https://wiki.onosproject.org/display/ONOS/Goldeneye+Release+Notes + +The APIs docs exist as a submodule in docs/apis. +In order to retrieve them, you must change directories to "apis" and then do a "git pull origin master". +This will pull down all relevant API documents related to the source components in this release". +here is api link: https://github.com/onosfw/apis + +OpenStack Release +================= + +OpenStack Mitaka wiki page `OpenStack Mitaka wiki`_. + +.. _OpenStack Mitaka wiki : https://wiki.openstack.org/wiki/Main_Page + +OpenStack Liberty api page `OpenStack Networking Api`_. + +.. _OpenStack Networking Api : http://developer.openstack.org/api-ref-networking-v2-ext.html + + +Revision: _sha1_ + +:Author: Lucius(lukai1@huawei.com) + +Build date: |today| diff --git a/docs/releasenotes/index.rst b/docs/releasenotes/index.rst new file mode 100644 index 00000000..942fcf4f --- /dev/null +++ b/docs/releasenotes/index.rst @@ -0,0 +1,15 @@ +******************** +ONOSFW Release Notes +******************** + +.. toctree:: + :numbered: + :maxdepth: 4 + + release.notes.rst + +Revision: _sha1_ + +:Author: Lucius(lukai1@huawei.com) + +Build date: |today| diff --git a/docs/releasenotes/scenario-description.rst b/docs/releasenotes/scenario-description.rst new file mode 100644 index 00000000..4e2e2724 --- /dev/null +++ b/docs/releasenotes/scenario-description.rst @@ -0,0 +1,97 @@ +======================== +Release notes for onosfw +======================== + +.. contents:: Table of Contents + :backlinks: none + + +Abstract +======== + +This document describes the testing scenario of onosfw project, including ONOS bare metal and virtual deployment scenario + +License +======= +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) Lucius (HUAWEI) + +Version history +=============== + ++------------+----------+------------+------------------+ +| **Date** | **Ver.** | **Author** | **Comment** | +| | | | | ++------------+----------+------------+------------------+ +| 2016-08-11 | 0.0.1 | Lucius | First draft | +| | | (HUAWEI) | | ++------------+----------+------------+------------------+ + +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. +In the Colorado release, in addition to the features in the Brahmaputra release, ONOSFW has included more functions in the Goldeneys of ONOS, and added service Function Chaining scenario by integrating the networking-sfc capability of openstack. +Therefore, both features and scenarios configurations are described. + +ONOSFW Test Scenarios +===================== + +Currently Openstack and ODL are using Centralized gateway to reach external network.ONOS takes a different approach, it uses DVR mode, where each compute node has the ability to reach external network, as illustrated below: + +.. image:: /etc/ONOS-DVR.png + + +Secenario 14 ONOS-HA : +---------------------- +1. 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 + +2. 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 + +3. SFC feature + + 3.1 Infrastructure CURD operation of SFC. + + 3.2 traffic through SFC + + +Revision: _sha1_ + +:Author: Lucius(lukai1@huawei.com) + +Build date: |today| diff --git a/docs/userguide/feature.userguide.rst b/docs/userguide/feature.userguide.rst new file mode 100644 index 00000000..26943f2d --- /dev/null +++ b/docs/userguide/feature.userguide.rst @@ -0,0 +1,143 @@ +================= +ONOSFW User Guide +================= + +.. contents:: Table of Contents + :backlinks: none + + +Abstract +======== + +This document describes the user guide instruction for onosfw project, including env setup and test case. + +License +======= + +.. This work is licensed under a Creative Commons Attribution 4.0 International License. +.. http://creativecommons.org/licenses/by/4.0 +.. (c) Lucius (HUAWEI) + +Version history +=============== + ++------------+----------+------------+------------------+ +| **Date** | **Ver.** | **Author** | **Comment** | +| | | | | ++------------+----------+------------+------------------+ +| 2016-01-21 | 1.0.0 | Lucius | Rewritten for | +| | | (HUAWEI) | ONOSFW C release | ++------------+----------+------------+------------------+ + +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. +In the Colorado release, in addition to the features in the Brahmaputra release, ONOSFW has included more functions in the Goldeneys of ONOS, and added service Function Chaining scenario by integrating the networking-sfc capability of openstack. +Therefore, both features and scenarios configurations are described. + +ONOSFW User Guide Manaully +========================== + +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” + + 2. 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 + + 3. set the external port name:: + + ONOS command：externalportname-set –n “external port name” + + 4. create provider network:: + + set manager on compute node and network node: ovs-vsctl set-manager tcp:“onos ip”:6640 + + 5. create basic networks and instances on openstack dashboard to verify L2/L3 function + + 6. create basic scenarios to verify SFC functions. + +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 + +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: _sha1_ + +:Author: Lucius(lukai1@huawei.com) + +Build date: |today| diff --git a/docs/userguide/index.rst b/docs/userguide/index.rst new file mode 100644 index 00000000..5f7c67bb --- /dev/null +++ b/docs/userguide/index.rst @@ -0,0 +1,15 @@ +***************** +ONOSFW User Guide +***************** + +.. toctree:: + :numbered: + :maxdepth: 4 + + feature.userguide.rst + +Revision: _sha1_ + +:Author: Lucius(lukai1@huawei.com) + +Build date: |today| -- cgit 1.2.3-korg