aboutsummaryrefslogtreecommitdiffstats
path: root/docs/userguide
diff options
context:
space:
mode:
authorCNlucius <lukai1@huawei.com>2016-09-21 02:06:42 -0400
committerCNlucius <lukai1@huawei.com>2016-09-21 03:21:24 -0400
commit8a9ee0bc846aa992a14aea3d0539512e55aa9305 (patch)
treebda5ff90cb746b02a4112851051ebb4ce3a0b988 /docs/userguide
parent7f88859c426f804565cbef961a975c9e63ce68ae (diff)
Modefiy onosfw release doc
Change-Id: Ia688815fa7c6f4a4578c6bf71e6137a37fd2bee5 Signed-off-by: CNlucius <lukai1@huawei.com>
Diffstat (limited to 'docs/userguide')
-rw-r--r--docs/userguide/feature.userguide.rst22
1 files changed, 11 insertions, 11 deletions
diff --git a/docs/userguide/feature.userguide.rst b/docs/userguide/feature.userguide.rst
index 26943f2d..68c1a17e 100644
--- a/docs/userguide/feature.userguide.rst
+++ b/docs/userguide/feature.userguide.rst
@@ -32,9 +32,9 @@ 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.
-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 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
==========================
@@ -91,11 +91,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:
@@ -103,13 +103,13 @@ 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
@@ -124,7 +124,7 @@ Scenario Supported
* Remove a node from the chain and verify with traffic
* Get service chain status
-
+
ONOSFW Demo Video
-----------------