x/vmware-nsx
Code Issues Proposed changes
e86347e3a0
vmware-nsx/vmware_nsx_tempest
History
Devang Doshi ab184b53f8 Tempest: Tempest test NSX security groups failing 
- NSX firewall realization takes longer time than 2 sec. I increased
to 20 and it test cases started passing

Change-Id: I409878b4a7d0b40405977790cdb34c518bd80453
2017-05-19 12:36:26 -07:00
..
common [Tempest]: Adding of more cases for FWaaS 2017-05-18 02:29:29 +00:00
doc Tempest: admin-policy scenario basic operation test 2017-03-05 11:34:48 +00:00
lib Tempest:Deploy and Validate Neutron resources using HEAT Template on NSXT|V 2017-04-27 12:04:16 +00:00
services [Tempest]: Adding of FWaaS api testcases. 2017-05-13 21:22:46 +00:00
tests Tempest: Tempest test NSX security groups failing 2017-05-19 12:36:26 -07:00
__init__.py Fixes vmware_nsx_tempest tempest plugin issues with tempest 2017-05-17 10:24:53 +00:00
_i18n.py Drop log translations 2017-03-26 05:09:02 -07:00
config.py Fixes vmware_nsx_tempest tempest plugin issues with tempest 2017-05-17 10:24:53 +00:00
plugin.py Fixes vmware_nsx_tempest tempest plugin issues with tempest 2017-05-17 10:24:53 +00:00
README.rst Removing irrelevant note in README file 2017-03-29 10:54:05 +00:00

README.rst

Welcome!

vmware_nsx_tempest is a plugin module to openstack tempest project.

If you are not familiar with tempest, please refer to:

https://docs.openstack.org/developer/tempest

It is implemented with tempest external plugin. The official design sepcification is at:

https://review.openstack.org/#/c/184992/

Overview

vmware_nsx_tempest hosts vmware_nsx's functional api and scenario tests.

All vmware_nsx_tempest tests are in "master" branch. For this reason, it is recommended to have your own developer version of vmware-nsx repo installed outside the devstack folder, /opt/stack/.

For example at /opt/devtest folder. In doing so, you can install editable vmware-nsx repo under tempest VENV environemnt.

Installation:

  1. On your own development folder, for example /opt/devtest/, install your own tempest development env at /opt/devtest/os-tempest/:

    $ cd /opt/devtest
$ git clone https://github.com/openstack/tempest os-tempest

  2. Install virtualenv with the following command:

    $ cd /opt/devtest/os-tempest
$ ./run_tempest.sh -u not_exist_tests

  3. Install vmware-nsx master branch at /opt/devtest/vmware-nsx:

    $ cd /opt/devtest
$ git clone https://github.com/openstack/vmware-nsx

  4. Install vmware_nsx_tempest in your tempest development environment:

    $ cd /opt/devtest/os-tempest
$ source .venv/bin/activate
$ pip install -e /opt/devtest/vmware-nsx/

    Run command:

    $ pip show vmware-nsx

    You should observe the following statements:

    Location: /opt/devtest/vmware-nsx

    and under section of Entry-points:

    [tempest.test_plugins]
vmware-nsx-tempest-plugin = vmware_nsx_tempest.plugin:VMwareNsxTempestPlugin

  5. Validate installed vmware_nsx_tempest successfully do:

    $ cd /opt/devtest/os-tempest
$ tools/with_venv.sh testr list-tests vmware_nsx_tempest.*l2_gateway

Your installation failed, if no tests are shown.

Execution:

vmware_nsx_tempest tests are tempest tests, you need to run from tempest directory. For example, to run only l2-gateway tests:

$ cd /opt/devtest/os-tempest
$ ./run_tempest.sh -t vmware_nsx_tempest.*test_l2_gateway
$ ./run_tempest.sh -d vmware_nsx_tempest.tests.nsxv.api.test_l2_gateway_connection.L2GatewayConnectionTest.test_csuld_single_device_interface_vlan

TechNote on vmware_nsx_tempest:

vmware_nsx_tempest is a plugin to tempest, not neutron, nor vmware_nsx.

It is defined by tempest.test_plugins.

Modules within vmware_nsx_tempest can not see resources defined by vmware_nsx. Commands like following are not acceptable, unless vmware_nsx is installed in your tempest environment:

import vmware_nsx.shell.admin.plugins.common.utils as admin_utils