2065418288
1. add lbaas l7 switching clients
2. enhance to delete l7 resources if present
3. enhance NSX-v scenario to support l7 switching testing
3.1 check floatingip assiged to server before ping test
NSX-v3 can take 500+ second to assign floatingip to VM
3.2 enhance test_lbaas_round_robin to support l7 test
3.3 test_lbaas_l7_switching_ops only test URL starts_with
validation.
4. l7_switching_ops requires around 2000 seconds. When run test
set OS_TEST_TIMEOUT=2400 to avoid fixture timeout.
5. add CONF.nsxv.bugs_to_resolve to skip tests that can not be
run at sepcific NSX plugin environment.
6. doc/README-LBaaS.rst describes limitation and how to run
tests at different plugin's and backends.
Change-Id: Ib2ee4ce57d45882d76e25ce7b7bba3d825bf34ab
This folder contains services for managing NSX-v, NSX-v3.
Services provided:
# Openstack tempest service clients l2_gateway_client.py based on tempest BaseNetworkClient implements client APIs to manage neutron l2-gateway resources
- l2_gateway_connection_client.py
-
based on tempest BaseNetworkClient implements client APIs to manage neutron l2-gateway-connection resources
- lbaas v2 clients: ported from neutron_lbaas to comply with tempest services.
-
lbaas/load_balancers_client.py lbaas/listeners_client.py lbaas/pools_client.py lbaas/health_monitorys_client.py lbaas/members_client.py
- lbv1_client.py
-
based on tempest BaseNetworkClient implements client APIs to manage neutron v1 load-balancer resources
- network_client_base.py
-
due to tempest network services are in the process of migrating to tempest-lib, some features to be used by tests are not in BaseNetworkClient. Inherent here and used by all vmware-nsx-tempest client for now.
# NSX speific services nsxv_client.py implements API to manage NSX-v components - Logical switch (Tenant network) - Edge (Service edge, DHCP edge, and VDR edge) - DFW firewall rules (Security group) - SpoofGuard
- nsxv3_client.py implements API to manage NSX backend resources:
-
- logical switch
- firewall section
- nsgroup
- logical router