Document updates for Fraser

Change-Id: I002848374caf28c0e6f4184bc9bd9e87b1918255
Signed-off-by: nikoskarandreas <nick@intracom-telecom.com>

Document updates for Fraser

Fixed wrong release date.
Removed a closed issue and a reference to it.

Change-Id: I002848374caf28c0e6f4184bc9bd9e87b1918255
Signed-off-by: nikoskarandreas <nick@intracom-telecom.com>
(cherry picked from commit b7221d90abe4a735f606bfbf464e8c6512fc3a67)

3 files changed, 28 insertions, 44 deletions

diff --git a/docs/development/overview/index.rst b/docs/development/overview/index.rst
index e932f9a..021ace9 100644
--- a/docs/development/overview/index.rst
+++ b/docs/development/overview/index.rst
@@ -30,22 +30,22 @@ An overview of the SDNVPN Test is depicted here. More details for each test case
 https://wiki.opnfv.org/display/sdnvpn/SDNVPN+Testing
 
     BGPVPN Tempest test cases
-        Create BGPVPN passes
-        Create BGPVPN as non-admin fails
-        Delete BGPVPN as non-admin fails
-        Show BGPVPN as non-owner fails
-        List BGPVPNs as non-owner fails
-        Show network associated BGPVPNs as non-owner fails
-        List network associated BGPVPNs as non-owner fails
-        Associate/Deassociate a network to a BGPVPN resource passes
-        Update route targets on a BGPVPN passes
-        Update route targets on a BGPVPN as non-admin fails
-        Reject the creation of BGPVPN with invalid route targets passes
-        Reject the update of BGPVPN with invalid route targets passes
-        Reject the association on an invalid network to a BGPVPN passes
-        Reject the diassociation on an invalid network to a BGPVPN passes
-        Associate/Deassociate a router to a BGPVPN resource passes
-        Attach the subnet of an associated network to an associated router of the same BGVPN passes
+        - Create BGPVPN passes
+        - Create BGPVPN as non-admin fails
+        - Delete BGPVPN as non-admin fails
+        - Show BGPVPN as non-owner fails
+        - List BGPVPNs as non-owner fails
+        - Show network associated BGPVPNs as non-owner fails
+        - List network associated BGPVPNs as non-owner fails
+        - Associate/Deassociate a network to a BGPVPN resource passes
+        - Update route targets on a BGPVPN passes
+        - Update route targets on a BGPVPN as non-admin fails
+        - Reject the creation of BGPVPN with invalid route targets passes
+        - Reject the update of BGPVPN with invalid route targets passes
+        - Reject the association on an invalid network to a BGPVPN passes
+        - Reject the diassociation on an invalid network to a BGPVPN passes
+        - Associate/Deassociate a router to a BGPVPN resource passes
+        - Attach the subnet of an associated network to an associated router of the same BGVPN passes
 
 
 
diff --git a/docs/release/installation/index.rst b/docs/release/installation/index.rst
index 78bdc8d..2625ef9 100644
--- a/docs/release/installation/index.rst
+++ b/docs/release/installation/index.rst
@@ -92,7 +92,7 @@ version of OPNFV, checkout the appropriate branch:
 ::
 
  cd fuel
- git checkout stable/<colorado|danube|euphrates>
+ git checkout stable/<colorado|danube|euphrates|fraser>
 
 Now download the corresponding OPNFV Fuel ISO into an appropriate folder from
 the website
diff --git a/docs/release/release-notes/release-notes.rst b/docs/release/release-notes/release-notes.rst
index 9f4ad21..58f929d 100644
--- a/docs/release/release-notes/release-notes.rst
+++ b/docs/release/release-notes/release-notes.rst
@@ -12,13 +12,13 @@ License. .. http://creativecommons.org/licenses/by/4.0 ..
 Abstract
 ========
 
-This document comprises the release notes for the SDN VPN feature contained in the Euphrates
+This document comprises the release notes for the SDN VPN feature contained in the Fraser
 release of OPNFV.
 
 Important notes
 ===============
 
-In the Euphrates release, SDN VPN only supports ODL as a backend. Make sure to always deploy
+In the Fraser release, SDN VPN only supports ODL as a backend. Make sure to always deploy
 SDN VPN and ODL together. Make use of deployment scenarios including the SDNVPN feature such as os_odl_bgpvpn_{ha|noha}.
 
 Summary
@@ -36,39 +36,31 @@ Release Data
 | **Project**                          | sdnvpn                                    |
 |                                      |                                           |
 +--------------------------------------+-------------------------------------------+
-| **Repo/tag**                         | Euhprates 1.0                             |
+| **Repo/tag**                         | Fraser 6.0                                |
 |                                      |                                           |
 +--------------------------------------+-------------------------------------------+
-| **Release designation**              | Euphrates 1.0 - initial release           |
+| **Release designation**              | Fraser 6.0 - initial release              |
 |                                      |                                           |
 +--------------------------------------+-------------------------------------------+
-| **Release date**                     | Oct 20 2017                               |
+| **Release date**                     | Apr 20 2018                               |
 |                                      |                                           |
 +--------------------------------------+-------------------------------------------+
-| **Purpose of the delivery**          | Rebased to new upstream versions          |
-|                                      | Removed Fuel deployment scenario          |
-|                                      | Couple of new test cases                  |
+| **Purpose of the delivery**          | New test cases                            |
 |                                      |                                           |
 +--------------------------------------+-------------------------------------------+
 
 Version change
 --------------
 
-Compared to the Colorado release, a new version of ODL including
-several critical bugfixes is deployed. Together with the new BGP
-stack, integration with Apex, the Horizon dashboards and bugfixes the
-user has even more features available. New testcases were added to
+Compared to the Euphrates release, new testcases were added to
 functest to guarantee functionality.
 
 Module version changes
 ~~~~~~~~~~~~~~~~~~~~~~
-ODL has been upgraded to Carbon SR2.
+ODL has been upgraded to Nitrogen.
 
 Document changes
 ~~~~~~~~~~~~~~~~
-The previous monolithic user guide, which was also covering install and
-config, has been broken up into multiple documents.
-
 
 Reason for version
 ------------------
@@ -80,7 +72,7 @@ SDN VPN adds the possibility to create and associate BGP/MPLS based
 Virtual Private Networks (VPNs) through the OpenStack Neutron BGPVPN
 API extension.
 
-There has been no functional scope change in the Euphrates release, the
+There has been no functional scope change in the Fraser release, the
 main deliverable is newer upstream versions and additional test
 coverage.
 
@@ -104,8 +96,6 @@ Software deliverables
 Documentation deliverables
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-- Paragraph on SDN VPN feature for platform overview
-
 - Configuration guide
 
 - User guide
@@ -135,10 +125,9 @@ around by assigning a Floating IP to the instance [1].
 Currently we observe non-deterministic failures of individual tests within the
 SDNVPN section of the Functest suite, which are not reproducible in the development
 environment. In a development environment all Functest tests are successful.
-Sporadic failures have been observed in test cases 1,4 and 8. Furthermore, the
+Sporadic failures have been observed in test cases 4 and 8. Furthermore, the
 check of bgpd service running on Controller node, in test case 3, has a constant
-failure trend for Apex environment. Also for Apex environment we observe constant
-failure in refstack, during the server action test_reboot_server_hard [2].
+failure trend for Apex environment.
 
 Workarounds
 -----------
@@ -149,9 +138,6 @@ by not network associating subnets attached to routers.
 The NAT issues are worked around by assigning floating IPs to VMs that require
 external connectivity.
 
-For the failures observed in CI, no workaround is required since the faults were
-not reproducible in live deployments.[3]
-
 Test results
 ============
 
@@ -163,5 +149,3 @@ References
 ==========
 [0] https://jira.opnfv.org/projects/SDNVPN/issues/SDNVPN-94
 [1] https://jira.opnfv.org/projects/SDNVPN/issues/SDNVPN-99
-[2] https://jira.opnfv.org/projects/SDNVPN/issues/SDNVPN-172
-[3] https://jira.opnfv.org/projects/SDNVPN/issues/SDNVPN-170