From 3bee66ed9be2e78b1c11b095deb2205ce6ff4865 Mon Sep 17 00:00:00 2001 From: Georg Kunz Date: Thu, 14 Jun 2018 15:25:46 +0200 Subject: Running BGPVPN Tempest tests as tempest_custom test We need to disable one BGPVPN tempest test due to a bug in ODL. Since the SDNVPN test framework does not allow for disabling a single test case, we are switching to tempest_custom. Change-Id: Ifbd7c1dc5e799d6a6c774e08e9fc1a3b2294b47c Signed-off-by: Georg Kunz --- docs/testing/user/userguide/testing_guide.rst | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) (limited to 'docs/testing/user') diff --git a/docs/testing/user/userguide/testing_guide.rst b/docs/testing/user/userguide/testing_guide.rst index e8430601..17c5431f 100644 --- a/docs/testing/user/userguide/testing_guide.rst +++ b/docs/testing/user/userguide/testing_guide.rst @@ -278,7 +278,17 @@ Here is an example of what this file should contain. # Expected device name when a volume is attached to an instance. volume_device_name: vdb -Use the listing above at a minimum to execute the mandatory test areas. +Use the listing above as a minimum to execute the mandatory test areas. + +If the optional BGPVPN Tempest API tests shall be run, Tempest needs to be told +that the BGPVPN service is available. To do that, add the following to the +``$DOVETAIL_HOME/pre_config/tempest_conf.yaml`` configuration file: + +.. code-block:: bash + + service_available: + bgpvpn: True + Configuration for Running HA Test Cases (Mandatory) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -- cgit 1.2.3-korg