The instance.resize_revert.start and instance.resize_revert.end
notifications are transformed to the versioned framework.
Change-Id: Ia86c8804b284ed4ad72a1993c454ec373c063b99
Implements: bp versioned-notification-transformation-queens
GET simple_tenant_usage API accept query param to filter the
tenant usage.
This commit adds json schema to validate the valid
query parameters.
There is no change in API behaviour and additionalProperties
is kept True for backward compatibility.
Partially implements blueprint json-schema-validation-for-query-param
Change-Id: I24726fd9a82617798a13597ad9883db22a4a9846
The instance.live_migration_pre.start and instance.live_migration_pre.end
notifications has been transformed to the versioned notification framework.
Co-Authored-By: Elod Illes <elod.illes@ericsson.com>
Change-Id: Ied6e9016e7406365c9d0beb281eeb31b7d0cf71b
Implements: bp versioned-notification-transformation-queens
Replace FakeDriver with FakeLiveMigrateDriver in live migration
related notification functional tests.
Change-Id: I1b2be23cd4d53bb061f4b0abef5e2b554c3ddad1
Change test_live_migrate_force_complete and test_live_migrate_delete to
use FakeDriver instead of mock.side_effect.
Change-Id: I7eae472b9cbef98ed77cdf22141c8332b17d37c2
This patch covers the following two scenarios while checking the
resource allocations at every steps:
* boot a server, soft delete, wait until automatic reclaim
* boot a server, soft delete, restore, normal delete
Change-Id: I635481b944b8a6c73001bbc69f1393a2eeb54527
Starting multiple compute service in a single functional test is
not a single line of code and it repeated multiple times. So
this patch pulls that code out into a common util function.
Change-Id: I204e17fe105f6378f1c9f8a7fc622a1886babecc
The I55edd2c6e4c752dbe675b6d51d71a047bf49597a refactor created a base class
for test cases that are checking allocations. This patch moves additional util
functions from the ServerMovingTest class to the base. The subsequent patch
covering soft delete cases needs these utils for non server moving tests.
Also the utils are made more generic to handle arbitrary number of compute
services. For this to work the setUp of the existing test classes needed
a small enhancement too.
Change-Id: I8430d39b8e8147731080e76f14a1a2b809c9863c
The service token feature is no longer considered experimental. This
change set rewords the help strings in the service_token conf
accordingly (fixing some typographical issues at the same time).
Change-Id: Ibaf06ff4f19283544de720b0b5f01ddf655b0b46
Change the Adapter loading for glance to use the auth from the user
context instead of exposing and requiring it in the conf. With this
change, it is possible to leave the [glance] conf section empty and
still be able to discover the image API endpoint from the service
catalog.
Note that, when we do this, we often end up with the user auth being a
_ContextAuthPlugin, which doesn't conform to the characteristics of
keystoneauth1.identity.base.BaseIdentityPlugin as augmented in
keystoneauth1 3.1.0. This requires a series of workarounds until bug
1709118 is fixed. These, along with workarounds for bugs 1707993 and
1707995, are subsumed with this change set in a (hopefully temporary)
helper method nova.utils.get_endpoint.
This lays the foundation for other services that should use user
context for authentication - those via which Nova is acting on behalf
of the user, i.e. cinder, keystone, and (sometimes) neutron[1].
(Services such as placement and ironic (and sometimes neutron) should
continue to use admin auth context loaded from the conf.)
[1] https://github.com/openstack/nova/blob/bb4faf40dfb02237af119646a5ebd960b072b31e/nova/network/neutronv2/api.py#L149-L160
Co-Authored-By: Eric Fried <efried@us.ibm.com>
Partial-Implements: bp use-ksa-adapter-for-endpoints
Change-Id: I4e755b9c66ec8bc3af0393e81cffd91c56064717
stewie925