The maximum page size is 1k in nsxv3 API response. Current read
logical resources only return maximum 1k. Change the nsxv3 client
to read all of the logical resources.
The update applies to GET API calls of logical resources.
Change-Id: I4d1f51c900e5ca89f1da8a5df13a535991765720
To support Native DHCP test cases, add the following methods to
nsxv3 service client.
- get_logical_dhcp_servers
- get_logical_dhcp_server
- get_dhcp_server_static_bindings
Change-Id: I595525370982e85d00b433e163c9d9c1dd0f843b
1. implement tags_client, complying to tempest framework
2. test tag-add CRUD operation
3. test tag-remove CRUD operation
4. test tag-replace CRUD operation
5. test filtering networks with combination of
tags querying parameters:
tags,
tags-any,
not-tags and
not-tags-any
Change-Id: I0c4583dcdc77a402e597a249b419e37a06d18dfc
NSX-v lbaas requires lbaas's network attached to an exclusive router.
To run lbaas tests on upstream implemantion, we need to remove
rotuer_type attributes at creating router.
Fixed lbaas API:
delete-all load-balanacer resources without deleting listeners.
wait for status function is now at load_balancers client.
Lbaas scenario tests replace urllib2 with urllib3.
Change-Id: Ief935eff8007c4c46115309f55ab3447ce146340
1. Port QoS clients from neutron qos and compliys with
tempest network service client format.
2. Port QoS API tests from neutron qos to be part of
vmware_nsx_tempest test suites.
3. Both NSX-v and NSX-t support QoS.
Change-Id: I20c90229a733b1b3a9ec4a623493298ec96c663b
Basic lbaasv2 ROUND_ROUBIN http forwording testing.
Add method wait_for_load_balancers_status which must
be called by every lbaasv2 resource update/delete to
indicate lbaasv2 operation is completed.
Change-Id: Ie04e7f4b864d74833d9ac4da9a17c0ff8749a082
vmware_nsx_tempest/services/nsxv3_client.py is a module, not a
scripts, hence no need to set it to be execuable.
Change-Id: Id8f361777cf4be096df687258eb070bba930c5d0
- Restructured function to reuse some of the function in various module
- Move pass and fail test verification within the test functions.
- Added L2GW connection API tests
- Added negative test cases
Change-Id: I9ac67b8ae0473dfc5b855744d2a4ca429b0045a6
Ported LBaasV2 clients and API tests from repo neutron_lbaas.
1. LBaasV2 core network is updated to reflect that nsxv
requiring subnet attached to exclusive router.
2. Modified to comply with tempest service client standard.
3. bugs opened to trace differences against upstream
1638148, 1637877, 1638571(p0), 1639223,
1638601(p0), 1639340, 1641643, 1641652, 1641902
Change-Id: I46d9dec3e8e23b9df6561acecf929fc0fd99686b
Added L2 gateway API tests into tempest.
Test l2 gateway create,
Test l2 gateway create with segmentation id,
Test l2 gateway delete,
Test l2 gateway update interface,
Test l2 gateway update l2gw name,
test l2 gateway show
Change-Id: Ibfd08960bb0828b4a7b1fe7c84b4abef1e22723f
Due to a recent upstream change, tempest project switched to
using in-tree tempest lib instead of tempest_lib. We need to
change our NSX tempest plugin test to use in-tree tempest lib too.
Upstream change:
https://review.openstack.org/#/c/284911
Fixes-Bug: #1552453
Change-Id: I522d234d948f5b7a6f70dec69c98c44eb5d7582f
Add a method in nsxv3 client to get firewall rule in a firewall
section based on name. The name of the firewall rule is the uuid
of the security group rule created from OpenStack.
Change-Id: I33c9c44cfd716cb91579b598ba8fbcc777f2c467
To run NSX tempest test cases, we need a NSX client to communicate
with NSX backend. Right now it supports the current NSX resource
- logical switch
- firewall section
- nsgroup
- logical router
Change-Id: I15f3a0bc659d0b2c417e0b14a062ee536b5fb967
installation procedure & tech-notes at vmware_nsx_tempest/README.rst
With this plugin method, vmware_nsx_tempest tests can be treated as
tempest tests and executed under tempest environment.
Fix nsxv_client to support multiple transport zones.
Change-Id: Id103c0ce03d75749fe6295108db48493f565b05a
Implements: blueprint vmware-nsx-tempest-plugin
