diff options
| author |   CNlucius CNlucius <lukai1@huawei.com> | 2016-09-21 08:55:45 +0000 |
|---|---|---|
| committer | CNlucius CNlucius <lukai1@huawei.com> | 2016-09-21 08:55:45 +0000 |
| commit | a90ca4e74a62656a2b12255e998df1d9cbd90148 (patch) | |
| tree | 4c679d8542f6f815cc2c88e7e9483a6e62694a23 /docs/release/onos-release.rst | |
| parent | 903d07967e478357058eaebc2af10eec54f92ba5 (diff) | |
Revert "Modefiy onosfw release doc"
Change-Id: Ic5d54e58c7375e35da79187d2597428e832b1ab1
Signed-off-by: CNlucius <lukai1@huawei.com>
Diffstat (limited to 'docs/release/onos-release.rst')
| -rw-r--r-- | docs/release/onos-release.rst | 87 |
1 files changed, 64 insertions, 23 deletions
diff --git a/docs/release/onos-release.rst b/docs/release/onos-release.rst index f0a255b7..dd45dbdc 100644 --- a/docs/release/onos-release.rst +++ b/docs/release/onos-release.rst @@ -1,3 +1,11 @@ +========================================= +OPNFV Colorado release note for onosfw +========================================= + + contents:: Table of Contents + :backlinks: none + + Abstract ======== @@ -25,18 +33,45 @@ Version history | | | (HUAWEI) | | +------------+----------+------------+------------------+ -Overview -======== - -In Colorado, ONOSFW project has two main scenarios for each of the four installers, Apex, Compass, Fuel, and JOID. -The first major scenario os-onos-nofeature-ha is to update the ONOS version from Emu to GlodenEye, so that the new ONOS features can be integrated with OPNFV applications. -The second major scenario os-onos-sfc-ha is to demonstrate the integration of SFC functionalities provided by the network-sfc in OpenStack \ -and ONOS sfc client library for service function chaining primitives – create, add, remove and modify. +Overview + +In Colorado, ONOSFW project has two main scenarios for each of the four installers, Apex, Compass, Fuel, and JOID. The first major scenario os-onos-nofeature-ha is to update the ONOS version from Emu to GlodenEye, so that the new ONOS features can be integrated with OPNFV applications. The second major scenario os-onos-sfc-ha is to demonstrate the integration of SFC functionalities provided by the network-sfc in OpenStack and ONOS sfc client library for service function chaining primitives – create, add, remove and modify. + + +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 +| +| | | | | | ++---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------ Scenarios Release Status ======================== -The scenarios are implemented and integrated with supported installers, and tested through OPNFV testing facilities. For Colorado 1.0, the supported installer and scenario combinations are: +The scenarios are implemented and integrated with supported installers, and tested through OPNFV testing facilities. For Colorado 1.0, the supported installer and scenario combinations are: fuel-os-onos-nofeature-ha @@ -48,29 +83,35 @@ The scenarios are implemented and integrated with supported installers, and test compass-os-onos-nofeature-ha - compass-os-onos-sfc-ha +For Colorado 2.0 the following installer/scenario combinations will be supported: -For Colorado 2.0 the following installer/scenario combinations will be supported: + apex-os-onos-nofeature-ha - apex-os-onos-nofeature-ha + apex-on-onos-sfc-ha - apex-on-onos-sfc-ha + compass-os-onos-sfc-ha Limitations =========== - tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_reboot_server_hard +The GlodenEye release of ONOS does not support the following test cases: + + tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_reboot_server_hard + + tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops + + tempest.scenario.test_server_basic_ops.TestServerBasicOps.test_server_basic_ops - tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops + tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern - tempest.scenario.test_server_basic_ops.TestServerBasicOps.test_server_basic_ops + tempest.scenario.test_volume_boot_pattern.TestVolumeBootPatternV2.test_volume_boot_pattern - tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern - tempest.scenario.test_volume_boot_pattern.TestVolumeBootPatternV2.test_volume_boot_pattern +Upstream Projects +================= -Upstream Requirement _ONOS Release -================================== +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 @@ -83,13 +124,13 @@ 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. +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 -Upstream Requirement _OpenStack Release -======================================= +OpenStack Release +================= OpenStack Mitaka wiki page `OpenStack Mitaka wiki`_. |