All the Neutron Stadium projects are importing Tempest code from the
neutron-tempest-plugin repo. We can now safely remove the remaining
bits of Tempest code.
Depends-On: I34efe893b93240c4689de1dda978209926022dfd
Change-Id: I2cf6e1f60926f36384bf056066bcdd4e0301494f
The plugin has been split into its own repository[1] in accordance with
Queens Goal "Split Tempest Plugins into Separate Repos/Projects[2]".
This patch removes the local copy as well as the setuptools entry point.
We can also now remove the autodoc_tree_excludes pbr option since
there's no more plugin to exclude and it defaults to [setup.py].
The patch leaves still in-tree base classes and constants in order to
avoid breakage of projects depending on such code. In the future, we
will deprecate those and gradually move affected subprojects to the new
repo.
List of affected repositories:
- neutron-vpnaas
- openstack-ansible-os_neutron
- tripleo-quickstart-extras
- networking-midonet
- networking-l2gw
- neutron-dynamic-routing
- networking-vsphere
- networking-plumgrid
- networking-zvm
[1] http://git.openstack.org/cgit/openstack/neutron-tempest-plugin
[2] https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html
Depends-On: I371aa4d5f043f695df04b98b0f485c8f0548f2b3
Change-Id: Ia21aad29d0bbf779583964db6f1665c9b3b83161
The Qos extension's API definition was rehomed into neutron-lib with
commit I8ab3712850ec02278b3efb9161fc03236926b842
This patch consumes the API definition from neutron-lib.
NeutronLibImpact
Change-Id: I3bb987920008d5a1d73cf4c5f37895d7f917c368
The new test added is a negative test that verifies
the inability of deleting in-use security group.
Change-Id: I118f1998df2184f9a688213cbaf01006f0426909
The metering extension's API definition was rehomed into neutron-lib
with commit I1b3285287be2429f7cf9913a7e6204db26371ced. This patch
consumes the API definition removing the rehomed code from neutron
and updating references to use lib's code.
NeutronLibImpact
Change-Id: Iacd69a3b332ee494946befc2f35638410e27cfb9
Configuring non-default remote_ip_prefix parameter in the rule list
for testing connectivity between VMs with such a rule.
Change-Id: I3f4b59f4fd3a0279d76cda2d2bf535c6e819adae
neutron-lib contains the QoS constants. This patch removes them from
neutron and replaces all such uses to lib's QoS constants.
NeutronLibImpact
Change-Id: I6ed379b178a2b79fd14385a1d1e87d87eb04bfb9
The following operations are enforced by this change:
* all v4 names/ints can be created in both v4 and v6 networks
* all v6 names/ints can be created in v6 networks
* no v6 names/ints can be created in v4 networks
This patch is a follow up to the doc chage:
Iff56c9290d8e86cfc0e2bfa24176f8d1e338a06e
Change-Id: I78dee3b665185d7da9d854a23f1a7c9d6dbe96de
Closes-Bug: #1692134
It already adds it between prefix/name and randomly generated number.
As a nice side effect, this fixes test_dhcp_port_status_active test case
for plugins that don't support router names longer than 15 characters
(Cisco for Cisco Virtual Topology System is such a plugin).
If we need a test case that validates long names, there should be a
separate one that will validate it.
Change-Id: Ief08475787cb8fe2f13a78faac666fcad344f1f0
The neutron-lib commit I360545b6ee4291547e0c5c8e668ad03d3efa4725 moved
the externally consumed globals from neutron.common.constants into lib.
With the exception of PROVISIONAL_IPV6_PD_PREFIX all other constants
in neutron.common.constants should only be used in neutron, and will
hopefully remain that way. External consumers needing access to other
common constants should move them into lib first.
NeutronLibImpact
Change-Id: Ie4bcffccf626a6e1de84af01f3487feb825f8b65
As explained in the bug, tempest DVR and HA migration scenario
tests are failing intermittently, as we are not checking if the
new router interfaces are ready after migration and might try
to use the old dataplane if the pre-migration router resources
(like interfaces, namespaces, etc) still exist and are not yet
destroyed.
We need to check that the pre-migration router interfaces are
deleted and the new interfaces are created and active (as we
can't check namespace existence on other nodes, we rely on port
status set by L2 agent after wiring the port) before
attempting ssh connectivity.
Closes-Bug: 1714802
Change-Id: I2a933d4cdd6de4e5ff31c8e3f97477819ba27afa
The old (tempest.test.requires_ext) location is deprecated in Pike.
Somehow missed in a previous change.
Change-Id: I8e18732443b1f01649a0a98a4765dafc5dc9bb7a
As existence of default subnetpool is required for auto allocated tests
and other tests in Nova, it is created by devstack. Default subnetpool
API tests perform create operations and tests are skipped in case
default subnetpool already exsits in the system.
This patch replaces coverage of skipped API tests, that are never run on
the gate, with unittests using extension testing.
Change-Id: I04986aaf06525db45290b0b838cc491ee99b751f
1) Creating VM with 2 security groups on its port
2) Check that both security groups with their rules apply, meaning
ICMP and ssh connectivity work as expected
3) Update port to have only security group with ssh rule
4) Check ICMP is not working anymore, while ssh does.
Change-Id: I9897722b7858071207a196a53ffb727e6cb1d436
The original code asserts that gw port's fixed_ips allocated from
the first subnet of external network. This will fails if external
network have multiple subnets.
Change-Id: I1a2d433b36a0cb72fc3e6dc3b377e0ca56fc6f7a
Closes-Bug: #1714007
The default security group can be deleted and updating
a port will recreate it. However, we should do this in
the BEFORE_UPDATE event handler rather than waiting for
it to happen inside of the port update transaction which
violates the transaction semantics of the security group
callbacks.
Closes-Bug: #1718282
Change-Id: I1ce8b558b0a831adcebead512d97554173423955
Having environment that supports different MTUs for networks,
check connectivity between 2 VMs with such networks
Change-Id: I5721a9ee35235c15bef1a9e8d62568abbfb5dc45
This patch added some api tests for tag resource with standard
attribute, which are securitygroup, floatingip, trunk, and policy.
In TagFilter test, identifier of resource was changed from name to
id because floatingip doesn't have name attribute.
Change-Id: I3a20abe00d4cb32b1a84aeb7b05429e776244c3e
Related-bug: #1682775
The tempest.test.is_extension_enabled() has moved to
tempest.common.utils.is_extension_enabled() in Pike.
Change-Id: I82cf40f5c11f8c20dcf7437f42d9fa526ccc5947
Instead of providing 'icmp' str in security rule creation, we test
that providing appropriate number instead works as well.
Change-Id: I094e964c19835d2c66a44abe41c9675fd87ceeee
1) Testing connectivity after adding ssh security rule
2) Testing that with ssh security rule you can't ping VM
3) Testing ICMP connectivity between 2 VMs
4) Testing connectivity to external network
Change-Id: I9e8a698f896089b530210735e1243bfff3afcdb7
Similar to I52428262276c16dbe077fcf77b1890f12dccc97d,
any subnets created with another client were failing to delete
with an HTTPNotFound which was silently ignored. So
we were implicitly depending on deletion of the network to
actually cleanup the subnet.
This adjusts the logic to use the admin_client to delete the subnet
whenever a different client is used.
Change-Id: Ie7d733a501b87fd2334054e72c86b8dae36da37c
There are some calls to create project in API tests.
This patch prepares create_project method so that the tests use.
Change-Id: I16a1936c04dca206b50026e796d512cf76f1bebb
QoS policy can't be removed from Neutron if it is used by
port or network. Because of this restriction there was method
to disassociate QoS policy from network/port and it had to be
called in each test where policy was attached to network/port.
This patch changes order of cleaning resources that QoS rules and
policies are always cleaned after all networks and ports are removed.
Thanks that there is no need to disassociate QoS policy from
network or port manually in each test.
Change-Id: Id9f6952fb68e1ad35fcd9ce99b9602247e3a229a
In case when network was created with different than default
client (like admin_client) network wasn't properly removed in
cleanup_resources method because default client was used to
delete function and 'NotFound' error returned from Neutron
was silently ignored in such case.
Now networks created by different than default client are
added to "admin_networks" list and are cleaned by admin_client.
Change-Id: I52428262276c16dbe077fcf77b1890f12dccc97d
In _create_network_policy(), policy object is passed into _get_policy_obj()
although it expects to be passed policy id. This patch passes policy id
instead of policy object and adds a unit test and API tests.
Change-Id: Ic4c755c54d93d7ca3312b432b7c1e6770f25c359
Closes-bug: #1712278
Miguel Lavalle