diff options
| author |   CNlucius <lukai1@huawei.com> | 2016-09-21 03:38:17 -0400 |
|---|---|---|
| committer | CNlucius <lukai1@huawei.com> | 2016-09-21 03:39:00 -0400 |
| commit | 695059a0b17a3c64859d6cdff11f4530b01df6dd (patch) | |
| tree | bda5ff90cb746b02a4112851051ebb4ce3a0b988 /docs/userguide/feature.userguide.rst | |
| parent | 7f88859c426f804565cbef961a975c9e63ce68ae (diff) | |
Modify onos release doc
Change-Id: I325ddfbcfdc30f22dbeaa570bc4518c8091c62ec
Signed-off-by: CNlucius <lukai1@huawei.com>
Diffstat (limited to 'docs/userguide/feature.userguide.rst')
| -rw-r--r-- | docs/userguide/feature.userguide.rst | 22 |
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 ----------------- |