The intent of this patch is to update the vmware-nsx-tempest-plugin
project so that it's capable of being published to PYPI. To do so
the doc requirements are separated from test-requirements, tox.ini is
updated in a few places and .gitignore file is included for good
measure.
Also see https://review.openstack.org/#/c/584498/
Change-Id: If02713fd427613433f554272c9962e0ebb95b1d6
Added vlan provider network ens based cases
Added MDProxy ens overlay based cases
Added Router NAT-NoNAt ens overlay based cases
Added some of the upstream scenario cases for ens overlay
Added some of the upstream scenario cases for ens vlan
Added Lbaas cases
Change-Id: I980d0e9fd89a000aaa60cab5c672f22d2f3f3fef
Earlier we were fetching first element of port and check mdproxy
irrespective of mdproxy exists on port or not.
Now it has changed.
Change-Id: I1dce88a83d148b01132c08578f0802d07c983bf6
SOme of the provider security group cases are failing due to operation
doesn't get reflected at the backend and we check check traffic in between.
This patch will overcome above problem.
Change-Id: Idd7b53a78a9a54641f911d867154fac2cafb177b
Tempest config updated with ens parameter
Changes to new tempest design to work with ens
Includes a basic scenario with N-S and E-W traffic
{0} vmware_nsx_tempest.tests.nsxv3.scenario.test_ens.EnsScenarioTest.test_ens_overlay_traffic_scenario [196.270294s] ... ok
======
Totals
======
Ran: 1 tests in 203.0000 sec.
- Passed: 1
Change-Id: I2bdeac7c334b539c39b9dbb576c181634e571d82
Base class : BaseAdminNetworkTest in create and delete network
root@localhost:/tmp/jenkins/workspace/end2end-precommit/tempest# ./tools/with_venv.sh stestr run vmware_nsx_tempest.tests.dvs.api.test_networks_admin_actions.AdminNetworksTestJSON
{0} vmware_nsx_tempest.tests.dvs.api.test_networks_admin_actions.AdminNetworksTestJSON.test_create_update_delete_flat_network_subnet [4.502624s] ... ok
{0} vmware_nsx_tempest.tests.dvs.api.test_networks_admin_actions.AdminNetworksTestJSON.test_create_update_delete_vlan_network_subnet [3.449882s] ... ok
{0} vmware_nsx_tempest.tests.dvs.api.test_networks_admin_actions.AdminNetworksTestJSON.test_list_networks [0.147079s] ... ok
{0} vmware_nsx_tempest.tests.dvs.api.test_networks_admin_actions.AdminNetworksTestJSON.test_show_network [0.112556s] ... ok
{0} vmware_nsx_tempest.tests.dvs.api.test_networks_admin_actions.AdminNetworksTestJSON.test_show_subnet [0.615493s] ... ok
======
Totals
======
Ran: 5 tests in 27.0000 sec.
- Passed: 5
- Skipped: 0
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 8.8276 sec.
Change-Id: Iea50f16e1c427e82f91405d1909a50dae800b930
Updated dhcp server with static routes using dhcp_121 option when
lbaas laodbalancer uses same dhcp server
{0} vmware_nsx_tempest.tests.nsxv.scenario.test_lbaas_static_routes_dhcp.LBaasWithStaticRouteOnDhcpServerTest.test_lbaas_http_traffic_roundrobin_with_http_health_type [691.743366s] ... ok
======
Totals
======
Ran: 1 tests in 715.0000 sec.
- Passed: 1
- Skipped: 0
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 691.7434 sec.
Issue: 2031971
Change-Id: I06369b43998d9817eb2ddbc4a07116d59e2b4c2e
With earlier code tests were failing with
AttributeError: 'Manager' object has no attribute 'volumes_client'
Tested the change with some tests
root@prome-mdt-dhcp412:/opt/stack/tempest# ostestr --pdb vmware_nsx_tempest.tests.nsxv3.scenario.test_allowed_address_pair.TestAllowedAddressPair
{0} vmware_nsx_tempest.tests.nsxv3.scenario.test_allowed_address_pair.TestAllowedAddressPair.test_allowed_adddress_pair_on_vms_with_single_ip [95.735889s] ... ok
{0} vmware_nsx_tempest.tests.nsxv3.scenario.test_allowed_address_pair.TestAllowedAddressPair.test_allowed_adddress_pair_ports_attach_as_interface_on_vms [114.847243s] ... ok
{0} vmware_nsx_tempest.tests.nsxv3.scenario.test_allowed_address_pair.TestAllowedAddressPair.test_allowed_adddress_with_ip_mac_attach_as_interface_on_vms [181.927796s] ... ok
{0} vmware_nsx_tempest.tests.nsxv3.scenario.test_allowed_address_pair.TestAllowedAddressPair.test_allowed_address_pair_on_vms_with_multiple_ips [97.630669s] ... ok
{0} vmware_nsx_tempest.tests.nsxv3.scenario.test_allowed_address_pair.TestAllowedAddressPair.test_vm_accessible_using_allowed_adddress_pair_port_fip [60.466328s] ... ok
======
Totals
======
Ran: 5 tests in 555.0000 sec.
- Passed: 5
- Skipped: 0
- Expected Fail: 0
- Unexpected Success: 0
- Failed: 0
Sum of execute time for each test: 550.6079 sec.
Change-Id: I4d58cd136496306755f105719ebc5c634bd5d3d9
Earlier ICMP rule were added to ports due to this
even after applying port security to instane port vms were able to
communicate with each other.
Change-Id: Iaea4fd3e0533f14b157b95a5cf17eefed771281d
Currently includes tests for below scenarios
- Test bandwidth-limit rule for both network and port
- Test dscp rule for both network and port
- Test qos policy with both rules for both network and port
- Resolved the conflict with fwaas change
Change-Id: I1d7dc355632ea05dcbb80cdf1ea41fbc380fb5bc
1) Handling of Provider sec group precedence at the backend
2) Handling of L7 policy rule position for redirect_url.
Change-Id: I5012aecedd2168d512f8e0296f6a534d4868cfa5
- Added ping to its own ip address test case
- Fixed bug: added delete router method for cleanup
- Fixed bug: provider security, only admin can update the provider sec
on a port
Change-Id: I7f63e332ff47db397f2474d90fd2bf7ea58a53a8
direction attribute is introduced from 'pike' series and does not work with ocata
reverting the changes back to make it backward compatible
Change-Id: I333e12b508c0743fe01ad3b009a40288b8f32fd7
