path: root/docs
diff options
Diffstat (limited to 'docs')
2 files changed, 22 insertions, 33 deletions
diff --git a/docs/release/release-notes/releasenotes.rst b/docs/release/release-notes/releasenotes.rst
index a02b82b..22ae740 100644
--- a/docs/release/release-notes/releasenotes.rst
+++ b/docs/release/release-notes/releasenotes.rst
@@ -5,21 +5,20 @@
-This document compiles the release notes for the Gambia release of
+This document compiles the release notes for the Hunter release of
Important notes
These notes provide release information for the use of SFC with the
-Apex installer, xci tool and Compass4NFV for the Gambia release of OPNFV.
+Apex installer and xci tool for the Hunter release of OPNFV.
The goal of the SFC release is to integrate the OpenDaylight SFC project
-into an OPNFV environment, with either the Apex installer, xci tool or
+into an OPNFV environment, with either the Apex installer or xci tool.
More information about OpenDaylight and SFC can be found here.
@@ -46,18 +45,16 @@ Release Data
| **Project** | sfc |
| | |
-| **Repo/tag** | opnfv-7.2.0 |
+| **Repo/tag** | opnfv-8.0.0 |
| | |
-| **Release designation** | Gambia 7.2 |
+| **Release designation** | Hunter 8.0 |
| | |
-| **Release date** | January 25th, 2019 |
+| **Release date** | May 10th, 2019 |
| | |
-| **Purpose of the delivery** | Move to OpenStack Rocky, ODL FLuorine|
-| | and OVS 2.9.2 (NSH native support) |
-| | Move to odl_v2 driver in n-sfc |
+| **Purpose of the delivery** | Project maintenance |
Version change
@@ -75,7 +72,7 @@ This release of OPNFV sfc is based on following upstream versions:
Document changes
-This is the first tracked version of OPNFV SFC Gambia. It comes with
+This is the first tracked version of OPNFV SFC Hunter. It comes with
the following documentation:
- :ref:`Design document <sfc-design>`
@@ -90,11 +87,6 @@ Reason for version
Feature additions
-- `Use odl_v2 driver for n-sfc`
-- `Unit test creation`
-- `Code refactored`
-- `Tests can be run without tacker and with n-sfc directly`
Bug corrections
@@ -104,7 +96,7 @@ Deliverables
Software deliverables
-No specific deliverables are created, as SFC is included with Apex and Compass4NFV.
+No specific deliverables are created, as SFC is included with Apex
Documentation deliverables
@@ -120,32 +112,18 @@ Known Limitations, Issues and Workarounds
System Limitations
-The Gambia 2.0 release has a few limitations:
-1 - The testcase sfc_two_chains_SSH_and_HTTP is disabled in this release due to
-a missing feature in ODL. We are unable to currently update a chain config
Known issues
-1 - When tacker is deployed without Mistral, there is an ERROR in the logs and
-the VIM is always in 'PENDING' state because tacker cannot monitor its health.
-However, everything works and SFs can be created.
-2 - When tacker is deployed without barbican, it cannot be in HA mode because
-barbican is the only way to fetch the fernet keys.
Test results
-The Gambia release of SFC has undergone QA test runs with Functest tests on the
-Apex and Compass installers and xci utility
-For more information on the OPNFV Gambia release, please see:
+For more information on the OPNFV Hunter release, please see:
@@ -154,7 +132,7 @@ OPNFV
2) `OPNFV documentation- and software downloads <https://www.opnfv.org/software/download>`_
-3) `OPNFV Gambia release <https://docs.opnfv.org/en/stable-gambia/index.html>`_
+3) `OPNFV Hunter release <https://docs.opnfv.org/en/latest/index.html>`_
diff --git a/docs/release/userguide/feature.userguide.rst b/docs/release/userguide/feature.userguide.rst
index 0e9ce2c..050a0c8 100644
--- a/docs/release/userguide/feature.userguide.rst
+++ b/docs/release/userguide/feature.userguide.rst
@@ -36,6 +36,17 @@ SFC capabilities and usage
The OPNFV SFC feature can be deployed with either the "os-odl-sfc-ha" or the
"os-odl-sfc-noha" scenario. SFC usage for both of these scenarios is the same.
+Once the deployment has been completed, the SFC test cases use information
+(e.g. INSTALLER IP, Controller IP, etc) of the environment which have been
+retrieved first from the installer in order to execute the SFC test cases properly.
+This is the default behavior.
+In case there is not an installer in place and the server for the SFC test execution
+has been prepared manually, installing all necessary components (e.g. OpenStack OpenDayLight etc)
+by hand. The user should update the "pod.yaml" file, including the all necessary details
+for each node which participates in the scenario.
+In case the dovetail project triggers the SFC test scenarios, the "pod.yaml" file will be prepared
+by dovetail project automatically.
As previously mentioned, Tacker is used as a VNF Manager and SFC Orchestrator. All
the configuration necessary to create working service chains and classifiers can
be performed using the Tacker command line. Refer to the `Tacker walkthrough <https://github.com/trozet/sfc-random/blob/master/tacker_sfc_apex_walkthrough.txt>`_