The instance.restore.start and instance.restore.end notifications
are transformed to the versioned framework.
Change-Id: I4459ec05a7153af7a0f04adcccb9d99cb5f661e5
Implements: bp versioned-notification-transformation-newton
After this microversion Nova API allows to get several keypairs
with the help of new optional parameters 'limit' and 'marker'
which were added to GET /os-keypairs request.
Partial-Bug: #1599904
Implements blueprint: keypairs-pagination
Change-Id: Idd3757f5be90ec4af1bd1a7ca3f9c20319dbfd33
keypair object and db_api supports 'limit' and 'marker'
parameters, these changes are required for keypairs pagination
for Nova API.
Part of blueprint keypairs-pagination
Change-Id: I9776efc609f01d053824b31f64126cfcd6dadc18
Previous commit moved exceptions option to central location.
This commit adds additional help text to those options.
Blueprint centralize-config-options-newton
Change-Id: I471216fe5828718f979d1ec3a77add8a258e68e5
Previous commit moved compute options to central location.
This commit adds additional help text to those options.
Blueprint centralize-config-options-newton
Change-Id: Ie78daca2e83968ce337cfe4cd183e762c8da4d83
pre live-migration checks now are done in async way. This patch
updates rest api version to keep this tracked.
bp: async-live-migration-rest-check
Change-Id: I9fed3079d0f1b7de3ad1b3ecd309c93785fd11fe
Added user_id in request parameter section of the
os-keypairs LIST method api-ref docs.
Closes bug: #1599911
Change-Id: Ibb52663b2890f6d46b125903b438c0142aba92f5
This reverts commit 5ce74fa06c0e7a70fdc927b2c1f364af83f7de1d.
We think this is causing a race and the postgres job to fail
since it's erroneously doing local deletes and not cleaning
up from the computes. We're not totally sure why it would
only impact the postgres job though, but the original change
failed the job and was rechecked, and the time it was merged
coincides with when the postgres job started spiking with
failures.
Related-Bug: #1600005
Closes-Bug: #1600031
Change-Id: I0ed184b579b8a8d861e4d2a7c317bf0bc0623d50
Several places raising MarkerNotFound were overwriting the
error message with the marker key. This fixes that by passing
the marker as a kwarg so the message is formatted properly.
Change-Id: I6d5c7048a5636e2cef15a6dab0d568c89e713a87