diff options
Diffstat (limited to 'docs/Brahmaputra')
| -rw-r--r-- | docs/Brahmaputra/configguide/config-for-installer.rst | 38 | ||||
| -rw-r--r-- | docs/Brahmaputra/release/onos-release.rst | 9 | ||||
| -rw-r--r-- | docs/Brahmaputra/scenario description/scenario-description.rst | 9 | ||||
| -rw-r--r-- | docs/Brahmaputra/userguide/index.rst | 2 | ||||
| -rw-r--r-- | docs/Brahmaputra/userguide/onosfw-userguide.rst | 21 |
5 files changed, 46 insertions, 33 deletions
diff --git a/docs/Brahmaputra/configguide/config-for-installer.rst b/docs/Brahmaputra/configguide/config-for-installer.rst index a41acbbc..89f2e0c3 100644 --- a/docs/Brahmaputra/configguide/config-for-installer.rst +++ b/docs/Brahmaputra/configguide/config-for-installer.rst @@ -87,13 +87,13 @@ Config Documentation for onos with apex ├── build │ ├── instack.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. Virtual deployment 3.1 Install jumphost. @@ -114,10 +114,10 @@ Config Documentation for onos with apex 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 Requirement for install ONOS +1. Pyhsical Requirement for install ONOS 1.1 Ubuntu Server 14.04 LTS 64-bit (from ISO or self-installed). @@ -145,7 +145,7 @@ Config Documentation for onos with Compass │ ├── templates # include the templates of onos │ ├── vars # include the var of onos used -3. Virtual deployment +3. Virtual deployment 3.1 Install jumphost @@ -175,8 +175,8 @@ Config Documentation for onos with Compass export OS_VERSION=trusty - export OPENSTACK_VERSION=liberty - + export OPENSTACK_VERSION=liberty + 4.4 Execute cd $WORKSPACE 4.5 Execute ./deploy.sh --dha $CONFDIR/dha.yml --network $CONFDIR/network.yml @@ -196,7 +196,7 @@ Config Documentation for onos with Fuel 1.3 libvirt virtualization support. - 1.4 minimum 2 networks and maximum 4 networks, multiple NIC and/or VLAN combinations are supported. + 1.4 minimum 2 networks and maximum 4 networks, multiple NIC and/or VLAN combinations are supported. 1.5 250G disk at least for no-ha virtual deployment @@ -207,11 +207,11 @@ Config Documentation for onos with Fuel below is the directory:: ├── build - │ ├──f_isoroot + │ ├──f_isoroot │ ├── f_onosfwpluginbuild # add onos build url - │ + │ ├── deploy - │ ├──scenario + │ ├──scenario │ ├── ha-onos_scenario.yaml # add onos ha configuration │ ├── noha-onos_scenario.yaml # add onos noha configuration ├── ci @@ -219,21 +219,25 @@ Config Documentation for onos with Fuel 2.2 Upload fuel-plugin-onos to git for fuel iso/rpm building. -3. Automatic deployment +3. Automatic deployment 3.1 Install jumphost. - + 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 no-ha_onos_heat_ceilmeter_scenario_0.0.0.2.yaml -i file://root/iso/fuel.iso. Fore bare metal deployment, change parameters correspondingly and use no-ha_onos scenario_0.0.1.yaml. + 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 no-ha_onos_heat_ceilmeter_scenario_0.0.0.2.yaml -i file://root/iso/fuel.iso. + + For bare metal deployment, change parameters correspondingly and use no-ha_onos scenario_0.0.1.yaml. 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.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 Kilo deployment, use –b Kilo. - 4.3 fpb --build fuel-plugin-onos + 4.3 fpb --build fuel-plugin-onos 4.4 Move onos*.rpm in to master and fuel plugins –install onos*.rpm. @@ -253,7 +257,7 @@ Config Documentation for onos with Fuel Fuel iso: http://build.opnfv.org/artifacts/ - Fuel-plugin-onos: http://git.openstack.org/cgit/openstack/fuel-plugin-onos/ + Fuel-plugin-onos: http://git.openstack.org/cgit/openstack/fuel-plugin-onos/ Config Documentation for onos with JOID diff --git a/docs/Brahmaputra/release/onos-release.rst b/docs/Brahmaputra/release/onos-release.rst index 2037781f..d5455c57 100644 --- a/docs/Brahmaputra/release/onos-release.rst +++ b/docs/Brahmaputra/release/onos-release.rst @@ -42,7 +42,10 @@ Version history 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 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. @@ -110,9 +113,9 @@ ONOS Emu Release Note `ONOS Emu Release Note`_. .. _ONOS Emu Release Note: https://wiki.onosproject.org/display/ONOS/Release+Notes+-+Emu+1.4.0 -The APIs docs exist as a submodule in docs/apis. +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". +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 diff --git a/docs/Brahmaputra/scenario description/scenario-description.rst b/docs/Brahmaputra/scenario description/scenario-description.rst index cd8ae7ba..4ed86b34 100644 --- a/docs/Brahmaputra/scenario description/scenario-description.rst +++ b/docs/Brahmaputra/scenario description/scenario-description.rst @@ -36,7 +36,10 @@ Version history 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 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. @@ -67,7 +70,7 @@ Secenario 14 ONOS-HA : 2.1.3 Related flow rule deleted when VM is deleted is OK - + 2.2 L3 south - north function @@ -77,7 +80,7 @@ Secenario 14 ONOS-HA : 2.2.3. VM hot migration is supported - + 2.3 Improvements diff --git a/docs/Brahmaputra/userguide/index.rst b/docs/Brahmaputra/userguide/index.rst index 38247f02..40b61c78 100644 --- a/docs/Brahmaputra/userguide/index.rst +++ b/docs/Brahmaputra/userguide/index.rst @@ -12,4 +12,4 @@ Revision: _sha1_ :Author: Henry(jiangrui1@huawei.com) -Build date: |today|
\ No newline at end of file +Build date: |today| diff --git a/docs/Brahmaputra/userguide/onosfw-userguide.rst b/docs/Brahmaputra/userguide/onosfw-userguide.rst index 6b9ce7e7..248bc641 100644 --- a/docs/Brahmaputra/userguide/onosfw-userguide.rst +++ b/docs/Brahmaputra/userguide/onosfw-userguide.rst @@ -42,7 +42,10 @@ Version history 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 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 User Guide Manaully @@ -92,11 +95,11 @@ Scenario Supported * 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: @@ -104,16 +107,16 @@ Scenario Supported * 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 - + ONOSFW Demo Video ----------------- |