Bases: neutron.tests.unit.extensions.test_extra_dhcp_opt.TestExtraDhcpOpt, vmware_nsx.tests.unit.nsx_mh.test_plugin.NsxPluginV2TestCase
Bases: vmware_nsx.tests.unit.nsx_mh.test_plugin.NsxPluginV2TestCase, neutron.tests.unit.extensions.test_l3_ext_gw_mode.ExtGwModeIntTestCase
Bases: neutron.tests.unit.extensions.test_l3.L3BaseForIntTests, vmware_nsx.tests.unit.nsx_mh.test_plugin.NsxPluginV2TestCase
Bases: vmware_nsx.tests.unit.nsx_mh.test_plugin.NsxPluginV2TestCase, neutron.tests.unit.extensions.test_l3.L3NatTestCaseMixin, neutron.tests.unit.extensions.test_securitygroup.SecurityGroupsTestCase
Bases: neutron.tests.unit.db.test_db_base_plugin_v2.NeutronDbPluginV2TestCase
Bases: neutron.tests.unit.extensions.test_securitygroup.SecurityGroupDBTestCase
Bases: neutron.tests.unit.db.test_db_base_plugin_v2.TestBasicGet, vmware_nsx.tests.unit.nsx_mh.test_plugin.NsxPluginV2TestCase
Bases: object
Bases: vmware_nsx.tests.unit.nsx_mh.test_plugin.L3NatTest, neutron.tests.unit.extensions.test_l3.L3NatDBIntTestCase, vmware_nsx.tests.unit.nsx_mh.test_plugin.NsxPluginV2TestCase, vmware_nsx.tests.unit.extensions.test_metadata.MetaDataTestCase
This tests that if multiple API requests arrive to create floating IPs on same external network to same port with one fixed ip, the latter API requests would be blocked at database side.
This tests that it is possible to delete a port that has multiple floating ip addresses associated with it (each floating address associated with a unique fixed address).
Ensure external gateway set doesn’t add excess IPs on router gw
Setting the gateway of a router to an external network with more than one IPv4 and one IPv6 subnet should only add an address from the first IPv4 subnet, an address from the first IPv6-stateful subnet, and an address from each IPv6-stateless (SLAAC and DHCPv6-stateless) subnet
Test router-interface-add for in-valid ipv6 subnets.
Verify that an appropriate error message is displayed when an IPv6 subnet configured to use an external_router for Router Advertisements (i.e., ipv6_ra_mode is None and ipv6_address_mode is not None) is attempted to associate with a Neutron Router.
This tests that if multiple routers add one port as their interfaces. Only the first router’s interface would be added to this port. All the later requests would return exceptions.
Ensure unique IPv6 router ports per network id.
Adding a router port containing one or more IPv6 subnets with the same network id as an existing router port should fail. This is so there is no ambiguity regarding on which port to add an IPv6 subnet when executing router-interface-add with a subnet and no port.
Test router-interface-add for valid ipv6 subnets.
Verify the valid use-cases of an IPv6 subnet where we are allowed to associate to the Neutron Router are successful.
Test adding router port with multiple IPv4 subnets fails.
Multiple IPv4 subnets are not allowed on a single router port. Ensure that adding a port with multiple IPv4 subnets to a router fails.
Test router-interface-add for multiple ipv4 subnets.
Verify that adding multiple ipv4 subnets from the same network to a router places them all on different router interfaces.
A port with multiple IPv6 subnets can be added to a router
Create a port with multiple associated IPv6 subnets and attach it to a router. The action should succeed.
Test router-interface-add for ipv6 subnets on different networks.
Verify that adding multiple ipv6 subnets from different networks to a router places them on different router interfaces.
Test router-interface-add for multiple ipv6 subnets on a network.
Verify that adding multiple ipv6 subnets from the same network to a router places them all on the same router interface.
Delete a subnet from a router interface
Verify that deleting a subnet with router-interface-delete removes that subnet when there are multiple subnets on the interface and removes the interface when it is the last subnet on the interface.
Create subnet should not cause excess fixed IPs on router gw
If a router gateway port has the maximum of one IPv4 and one IPv6 fixed, create subnet should not add any more IP addresses to the port (unless this is the subnet is a SLAAC/DHCPv6-stateless subnet in which case the addresses are added automatically)
Bases: vmware_nsx.tests.unit.nsx_mh.test_plugin.TestL3ExtensionManager
A fake extension manager for L3 and Security Group extensions.
Includes also NSX specific L3 attributes.
Bases: neutron.tests.unit.db.test_db_base_plugin_v2.TestNetworksV2, vmware_nsx.tests.unit.nsx_mh.test_plugin.NsxPluginV2TestCase
Bases: vmware_nsx.tests.unit.nsx_mh.test_plugin.NsxPluginV2TestCase, neutron.tests.unit.db.test_db_base_plugin_v2.TestPortsV2, neutron.tests.unit._test_extension_portbindings.PortBindingsTestCase, neutron.tests.unit._test_extension_portbindings.PortBindingsHostTestCaseMixin, neutron.tests.unit._test_extension_portbindings.PortBindingsVnicTestCaseMixin
Test port create with multiple IPv4, IPv6 DHCP/SLAAC subnets.
Tests that we continue to gracefully delete the network even if a neutron:dhcp-owned port was deleted concurrently.
Test that a port with an IPv6 SLAAC address can be deleted.
Test update of port with additional IP.
Test port update excluding IPv6 SLAAC subnet from fixed ips.
Test update of port IP.
Check that a configured IP 10.0.0.2 is replaced by 10.0.0.10.
Update IP and associate new IP on port.
Check a port update with the specified subnet_id’s. A IP address will be allocated for each subnet_id.
Test port update with an IPv6 SLAAC subnet in fixed IPs.
Test port update with a new IPv6 SLAAC subnet in fixed IPs.
Bases: neutron.tests.unit.extensions.test_securitygroup.TestSecurityGroups, vmware_nsx.tests.unit.nsx_mh.test_plugin.SecurityGroupsTestCase
Bases: neutron.tests.unit.db.test_db_base_plugin_v2.TestV2HTTPResponse, vmware_nsx.tests.unit.nsx_mh.test_plugin.NsxPluginV2TestCase
If a field used by policy is selected, do not duplicate it.
Verifies that if the field parameter explicitly specifies a field which is used by the policy engine, then it is not duplicated in the response.