summaryrefslogtreecommitdiffstats
path: root/docs/release/release-notes
diff options
context:
space:
mode:
authorpanageo2 <panageo@intracom-telecom.com>2017-07-11 13:47:04 +0000
committerNikolas Hermanns <nikolas.hermanns@ericsson.com>2017-07-13 12:59:58 +0200
commit05f2a546505b643b0301517587680bf5d7e0936a (patch)
treea5b40265380633572a2f0a95972a4e8324220640 /docs/release/release-notes
parent58a0249ab01b1c66c71bc402a6ea7f53e34b6c35 (diff)
Update release notes
Uplifting docs to D-3. Update release-notes to reflect the remaining issues we have not been able to resolve. JIRA: SDNVPN-169 Change-Id: I5997f1495fc37ecbc06a8c7b8071a7ba7f2c099c Signed-off-by: panageo2 <panageo@intracom-telecom.com>
Diffstat (limited to 'docs/release/release-notes')
-rw-r--r--docs/release/release-notes/release-notes.rst27
1 files changed, 19 insertions, 8 deletions
diff --git a/docs/release/release-notes/release-notes.rst b/docs/release/release-notes/release-notes.rst
index 1e7f489..d6816d0 100644
--- a/docs/release/release-notes/release-notes.rst
+++ b/docs/release/release-notes/release-notes.rst
@@ -1,5 +1,5 @@
==========================================================================
-OPNFV Release Note for the Danube.1.0 release of OPNFV for SDN VPN feature
+Release Note for the Danube.3.0 release of OPNFV for SDN VPN feature
==========================================================================
License
@@ -137,12 +137,18 @@ 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].
-OpenStack NAT does not work. Instances created in subnets that are connected to
-the public network via a gateway should have external connectivity. This does
-not work and can be worked around by assigning a Floating IP to the instance [1].
+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
+should have external connectivity. This does not work and can be worked
+around by assigning a Floating IP to the instance [1].
-For Apex the peering with the virtual Peer is not working due to limitation
-of apex networking.
+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
+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].
Workarounds
-----------
@@ -153,14 +159,19 @@ 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
============
The deployment scenarios have successfully deployed in OPNFV CI many
-times and all Functest tests (general and feature specific) are
-passing.
+times and all Functest tests (general and feature specific) are passing,
+with the exceptions described above.
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