summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/release-notes/release-notes.rst64
-rw-r--r--docs/userguide/feature.userguide.rst13
2 files changed, 44 insertions, 33 deletions
diff --git a/docs/release-notes/release-notes.rst b/docs/release-notes/release-notes.rst
index f97d3b6..90941d7 100644
--- a/docs/release-notes/release-notes.rst
+++ b/docs/release-notes/release-notes.rst
@@ -1,5 +1,5 @@
===============================================================================
-OPNFV Release Note for the Brahmaputra.3.0 release of OPNFV for SDN VPN feature
+OPNFV Release Note for the Colorado.1.0 release of OPNFV for SDN VPN feature
===============================================================================
License
@@ -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 Brahmaputra
+This document comprises the release notes for the SDN VPN feature contained in the Colorado
release of OPNFV.
Important notes
===============
-In the Brahmaputra release, SDN VPN only supports ODL as a backend. Make sure to always deploy
+In the Colorado 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.
Summary
@@ -34,34 +34,39 @@ Release Data
| **Project** | sdnvpn |
| | |
+--------------------------------------+--------------------------------------+
-| **Repo/tag** | brahmaputra.3.0 |
+| **Repo/tag** | Colorado.1.0 |
| | |
+--------------------------------------+--------------------------------------+
-| **Release designation** | Brahmaputra second stable release |
+| **Release designation** | Colorado 1.0 follow-up release |
| | |
+--------------------------------------+--------------------------------------+
-| **Release date** | March 28, 2016 |
+| **Release date** | September 22 2016 |
| | |
+--------------------------------------+--------------------------------------+
-| **Purpose of the delivery** | Including ODL bugfixes |
+| **Purpose of the delivery** | Including BGP stack - Quagga |
+| | Fuel 9.0 baseline + Bug-fixes |
+| | HEAT integration |
+| | 2 new e2e testcases for Functest |
+| | Documentation |
| | |
+--------------------------------------+--------------------------------------+
Version change
--------------
-Compared to the Brahmaputra base release, a new version of ODL including several critical
-bugfixes is deployed.
+Compared to the Brahmaputra release, a new version of ODL including several critical
+bugfixes is deployed. Together with the new BGP stack and HEAT integration the user
+can use now full stack bgp. New testcases to functest were added to guarantee
+functionality.
Module version changes
~~~~~~~~~~~~~~~~~~~~~~
-ODL has been upgraded to Beryllium SR1. On top of Beryllium SR1, a number of bugfix patches
-are applied which will be contained in Beryllium SR2. The deployment procedure has been
-enhanced to take care of previously required manual post-deployment configuration.
+ODL has been upgraded to Beryllium SR3.
Document changes
~~~~~~~~~~~~~~~~
-A slight readability improvement to the user guide has been made.
+The amount documentation is increased substantially. E2E deployment docu and examples to use bgpvpn
+is added.
Reason for version
------------------
@@ -72,7 +77,6 @@ Feature additions
SDN VPN adds the possibility to create and associate BGP/MPLS based Virtual Private Networks (VPNs)
through the OpenStack Neutron BGPVPN API extension.
-No new features are added in Brahmaputra.3.0
Bug corrections
~~~~~~~~~~~~~~~
@@ -106,26 +110,32 @@ Known Limitations, Issues and Workarounds
System Limitations
------------------
-The currently deployed system does not contain a BGP stack and hence is limited to
-providing connectivity within the domain controlled by one ODL instance (e.g.
-intra-DC communication). Addition of an open source BGP stack is planned for the
-Colorado release.
-
-Feature specific Yardstick test cases have not been implemented, we plan to add
-these in Colorado
+Floating ip will come with the Boron release so yardstick testcases cannot be run
+and the user is only able to access the node through tenat network. Boron is targeted
+for Colorado 2.0.
+Due to lacking support for floating IPs in ODL VPNService (which replaces Netvirt as
+Neutron backend in the SDN VPN scenarios), the following test suites have some restrictions
+and are not executed:
+- Tempest:
+ tempest.api.compute.servers.test_create_server.ServersTestJSON
+ tempest.api.compute.servers.test_create_server.ServersTestManualDisk
+ tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON
+ 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_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern
+ tempest.scenario.test_volume_boot_pattern.TestVolumeBootPatternV2.test_volume_boot_pattern
+
+Yardstick uses the floating ip mechanism to connect to the instances using SSH.
+Therefore, the default test cases have been replaced by the ones running tests on the
+bare-metal servers. Feature specific Yardstick test cases have not been implemented,
+we plan to add these in Colorado 2.0.
Known issues
------------
-The ODL VPN Service does not implement Floating IP, which is used extensively by Yardstick
-to run generic system tests, which do currently not pass for this reason.
-
Workarounds
-----------
-Manual configuration of VPN Service internal transport between multiple compute nodes is needed
-to enable inter-node connectivity.
-
Test results
============
diff --git a/docs/userguide/feature.userguide.rst b/docs/userguide/feature.userguide.rst
index 6b5f4dd..0b45e28 100644
--- a/docs/userguide/feature.userguide.rst
+++ b/docs/userguide/feature.userguide.rst
@@ -158,12 +158,13 @@ and make changes as required.
Installation procedures
-----------------------
-We describe several alternative procedures in the following.
-First, we describe several methods that are based on the deploy.sh script, which is also used by the OPNFV CI system.
-It can be found in the Fuel repository.
+We describe several alternative procedures in the following.
+First, we describe several methods that are based on the deploy.sh script,
+which is also used by the OPNFV CI system.
+It can be found in the Fuel repository.
-In addition, the SDNVPN feature can also be configured manually in the Fuel GUI.
-This is described in the last subsection.
+In addition, the SDNVPN feature can also be configured manually in the Fuel GUI.
+This is described in the last subsection.
Before starting any of the following procedures, go to
::
@@ -183,7 +184,7 @@ node discovery and platform deployment) will take place without any further prom
Full automatic virtual deployment NO High Availability Mode
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The following command will deploy the SDNVPN scenario in its non-high-availability flavor (note the
+The following command will deploy the SDNVPN scenario in its non-high-availability flavor (note the
different scenario name for the -s switch). Otherwise it does the same as described above.
::