summaryrefslogtreecommitdiffstats
path: root/docs/release/onos-release.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/release/onos-release.rst')
-rw-r--r--docs/release/onos-release.rst87
1 files changed, 23 insertions, 64 deletions
diff --git a/docs/release/onos-release.rst b/docs/release/onos-release.rst
index dd45dbdc..f0a255b7 100644
--- a/docs/release/onos-release.rst
+++ b/docs/release/onos-release.rst
@@ -1,11 +1,3 @@
-=========================================
-OPNFV Colorado release note for onosfw
-=========================================
-
- contents:: Table of Contents
- :backlinks: none
-
-
Abstract
========
@@ -33,45 +25,18 @@ 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.
-
-
-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
-|
-| | | | | |
-+---------------------------------------+-------------------------------------------+-------------------------------------------+-------------------------------------------+------------------------------------------------------------
+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.
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
@@ -83,35 +48,29 @@ The scenarios are implemented and integrated with supported installers, and test
compass-os-onos-nofeature-ha
-For Colorado 2.0 the following installer/scenario combinations will be supported:
+ compass-os-onos-sfc-ha
- apex-os-onos-nofeature-ha
+For Colorado 2.0 the following installer/scenario combinations will be supported:
- apex-on-onos-sfc-ha
+ apex-os-onos-nofeature-ha
- compass-os-onos-sfc-ha
+ apex-on-onos-sfc-ha
Limitations
===========
-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.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_reboot_server_hard
- tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern
+ tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_network_basic_ops
- tempest.scenario.test_volume_boot_pattern.TestVolumeBootPatternV2.test_volume_boot_pattern
+ tempest.scenario.test_server_basic_ops.TestServerBasicOps.test_server_basic_ops
+ tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern
-Upstream Projects
-=================
+ tempest.scenario.test_volume_boot_pattern.TestVolumeBootPatternV2.test_volume_boot_pattern
-ONOS Release
-============
+Upstream Requirement _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
@@ -124,13 +83,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
-OpenStack Release
-=================
+Upstream Requirement _OpenStack Release
+=======================================
OpenStack Mitaka wiki page `OpenStack Mitaka wiki`_.