summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/development/overview/index.rst32
-rw-r--r--docs/release/installation/index.rst2
-rw-r--r--docs/release/release-notes/release-notes.rst53
-rw-r--r--docs/release/scenarios/os-odl-bgpvpn/index.rst17
-rw-r--r--docs/release/scenarios/os-odl-bgpvpn/scenario.description.rst29
5 files changed, 63 insertions, 70 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..1a3e9a5 100644
--- a/docs/release/release-notes/release-notes.rst
+++ b/docs/release/release-notes/release-notes.rst
@@ -1,3 +1,11 @@
+.. _-os-odl-bgpvpn-noha:
+
+.. _-os-odl-bgpvpn-ha:
+
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com> and others
+
=====================
SDN VPN Release Notes
=====================
@@ -12,13 +20,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 +44,31 @@ Release Data
| **Project** | sdnvpn |
| | |
+--------------------------------------+-------------------------------------------+
-| **Repo/tag** | Euhprates 1.0 |
+| **Repo/tag** | opnfv-6.2.0 |
| | |
+--------------------------------------+-------------------------------------------+
-| **Release designation** | Euphrates 1.0 - initial release |
+| **Release designation** | Fraser 6.2 |
| | |
+--------------------------------------+-------------------------------------------+
-| **Release date** | Oct 20 2017 |
+| **Release date** | June 29 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 +80,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.
@@ -100,12 +100,14 @@ Software deliverables
- Integration of VPN Service functional tests and BGPVPN API tests into Functest framework.
- Enabling performance tests in Yardstick.
- Changes to 6Wind Zrpcd to enable integration with Apex.
+- Intra Datacenter ECMP (Equal Cost Multi Pathing) Testcase.
+- OpenDaylight and Open vSwitch Resynchronization Testcase.
+- Improved quality and stability of Testcase runs in CI environment.
+- External BGPVPN scenario added for XCI based deployment for BGPVPN scenarios.
Documentation deliverables
~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Paragraph on SDN VPN feature for platform overview
-
- Configuration guide
- User guide
@@ -125,7 +127,7 @@ Known issues
Moving to the new NetVirt has caused a regression in which a subnet
cannot be both attached to a Router and Network associated to a VPN.
This has been worked around in the tests and the upstream bug is being
-tracked [0].
+tracked [0] and [2].
NAT for a VM which is in a private neutron network does not work. Instances
created in subnets that are connected to the public network via a gateway
@@ -135,10 +137,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 +150,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 +161,4 @@ 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
+[2] https://jira.opendaylight.org/browse/NETVIRT-932
diff --git a/docs/release/scenarios/os-odl-bgpvpn/index.rst b/docs/release/scenarios/os-odl-bgpvpn/index.rst
index b50ac21..1c9c74b 100644
--- a/docs/release/scenarios/os-odl-bgpvpn/index.rst
+++ b/docs/release/scenarios/os-odl-bgpvpn/index.rst
@@ -1,14 +1,15 @@
-.. _sdnvpn-os-odl-bgpvpn-noha:
-
-.. _sdnvpn-os-odl-bgpvpn-ha:
-
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
-.. (c) Tim Irnich <tim.irnich@ericsson.com> and others
+.. (c) Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com> and others
+
+.. _os-odl-bgpvpn-noha:
+
+.. _os-odl-bgpvpn-ha:
+
+================================================================
+os-odl-bgpvpn-noha and os-odl-bgpvpn-ha overview and description
+================================================================
-=========================================
-os-odl_l2-bgpvpn overview and description
-=========================================
.. This document will be used to provide a description of the scenario for an end user.
.. You should explain the purpose of the scenario, the types of capabilities provided and
.. the unique components that make up the scenario including how they are used.
diff --git a/docs/release/scenarios/os-odl-bgpvpn/scenario.description.rst b/docs/release/scenarios/os-odl-bgpvpn/scenario.description.rst
index 2641d82..5d6c06d 100644
--- a/docs/release/scenarios/os-odl-bgpvpn/scenario.description.rst
+++ b/docs/release/scenarios/os-odl-bgpvpn/scenario.description.rst
@@ -1,6 +1,6 @@
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
-.. (c) Tim Irnich (tim.irnich@ericsson.com) and Nikolas Hermanns (nikolas.hermanns@ericsson.com)
+.. (c) Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com> and others
Introduction
============
@@ -72,28 +72,23 @@ Scenario usage overview
Configuring SDNVPN features
---------------------------
-Each installer has specific procedures to deploy the OPNFV platform so that the SDNVPN feature is enabled.
+Apex installer has specific procedures to deploy the OPNFV platform so that the SDNVPN feature is enabled.
-Fuel installer configuration
+APEX installer configuration
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-To install the SDNVPN feature using Fuel, follow the Fuel installation guide ensuring to select the SDNVPN
-feature when prompted <add link to Fuel docs once artifact locations are known>.
+To install the SDNVPN feature using the APEX installer, follow the APEX installation guide
+(https://wiki.opnfv.org/display/apex/Integration+Guide) and activate the SDNVPN feature when prompted (step "# Now execute a deployment")
-This will trigger installation of the OpenStack BGPVPN API extension for
-Neutron, set up for using the ODL driver, in addition to vanilla Neutron.
-In addition, the required karaf features will be activated when ODL is installed and the compute nodes
-will be configured including the VPN Service internal transport tunnel mesh.
+For os-odl-bgpvpn-noha deployment:
+----------------------------------
-No post-deploy configuration is necessary. The Fuel BGPVPN plugin and the ODL plugin
-should set up the cluster ready for BGPVPNs being created.
+python3 deploy.py -v -n ../config/network/network_settings.yaml -d ../config/deploy/os-odl-bgpvpn-noha.yaml --deploy-dir ../build --lib-dir ../lib --image-dir ../.build --virtual-computes 2 --virtual-default-ram 16
-APEX installer configuration
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+For os-odl-bgpvpn-ha deployment:
+--------------------------------
-To install the SDNVPN feature using the APEX installer, follow the APEX installation guide
-(https://wiki.opnfv.org/display/apex/Integration+Guide) and activate the SDNVPN feature when prompted (step "# Now execute a deployment")
-i.e. python3 deploy.py -v -n ../config/network/network_settings.yaml -d ../config/deploy/os-odl-bgpvpn-noha.yaml --deploy-dir ../build --lib-dir ../lib --image-dir ../.build --virtual-computes 2 --virtual-default-ram 16
+python3 deploy.py -v -n ../config/network/network_settings.yaml -d ../config/deploy/os-odl-bgpvpn-ha.yaml --deploy-dir ../build --lib-dir ../lib --image-dir ../.build --virtual-computes 2 --virtual-default-ram 16
Limitations, Issues and Workarounds
===================================
@@ -112,5 +107,5 @@ Integration with data center gateway will not work due to missing OVS patches fo
References
==========
-For more information on the OPNFV Danube release, please visit
+For more information on the OPNFV Fraser release, please visit
https://www.opnfv.org/software