This verifies all the parts of keypairs, including filling out all the
details for microversion 2.2 and 2.10 which change it.
Part of bp:api-ref-in-rst
Change-Id: Iab88dc75cdb7b5f91e46afd29ee61e38b325e180
After modifying the evacuate action, we now add a new microversion
change for modifying the live-migrate call so that the scheduler is
called when the admin user provides an hostname unless the force
field is provided.
APIImpact
Implements: blueprint check-destination-on-migrations-newton
Change-Id: I212cbb44f46d7cb36b5d8c74a79065d38fc526d8
As discussed at summit, the version part of the URL is not really
relevant, or a thing a user should be filling out themselves, this
should instead be set by the service catalog and extracted from the
token.
This removes it's reference in all documented REST urls, and adds a
new section describing how one gets the base URL for all calls.
Change-Id: I4306b8c3de0225e54f3909dd8a1fb293c4e5944c
Adding a new microversion for changing the evacuate action behaviour
to call the scheduler anyway unless the admin user provides a force
flag that then keeps the previous behaviour by forcing the conductor
to call the destination without verifying it.
Implements: blueprint check-destination-on-migrations
APIImpact
Change-Id: I9ecbe3d481bf17b12072511da4bb106ff1b6404e
verify the parameters of os-migrations.inc including response and
request. And, add warning for deprecation and incorrect wording of
policy default rule.
looks like the new migration is missing in doc, follow up patch will
add it.
Part of bp:api-ref-in-rst
Change-Id: I8fed7374c34c5c857c8c55f56f86ad4c744844e9
The legacy v2 API allow the 'null' value for user_data. Unfortunately
the v2.1 API didn't match that in the input validation. This patch
enables 'null' value, at sametime, it enables for v2.1 compat mode
also.
Change-Id: Iae614035efd4b37c214754ad12b17ca224b8fd92
Closes-Bug: #1582911
This completes the verification of flavors.inc across all
phases. References to the 500 error that create could do have been
removed because it turns out that code isn't reachable any more (see
Ic848db8c3df75054c389e87b2405134262b531e2)
Part of bp:api-ref-in-rst
Change-Id: I9e89a737df558c930a2ca028ed169a5b3e383a3d
This cleans up the baremetal proxy, which was horribly inaccurate (the
paths weren't right after the method verification)
A warning is stuck in the preamble, we really don't want people using
this. Parameters are documented as best as we could from Nova
source. Honestly, people should just talk to ironic directly and use
their docs.
Part of bp:api-ref-in-rst
Change-Id: I66e85f414e5f0edbf052ba56691294a94615c619
This completes the parameter, example and body verification
for the os-flavor-access API.
The tenant_id_body parameter description was made more generic
to be able to reuse it here.
Part of blueprint api-ref-in-rst
Change-Id: I78755f0f92f8e742b668102b98ae15d94f8bf941
This processes all 4 phases of the crash-dump action
* method verified, error codes cleaned up (extra explanation added where appropriate)
* action parameter added
* example verified
* body adds warning and versionadded stanzas
Part of bp:api-ref-in-rst
Change-Id: I6571a3981d25ab4b5459715c9d2061ad19f07f26
This reorder's parameters.yaml to the correct sort order, and turns
the info message about incorrect ordering into a warning. After this
lands parameters.yaml changes will always require that the items stay
in the sorted order enforced by the extension.
Part of bp:api-ref-in-rst
Change-Id: Ib890d369a8b50a8cd920f7b19ef13f44b3e657df
This completes the validation for the admin event interface, including
detailing the codes we currently return in the parameter list.
Because os-service was incorrectly using the 'status' key, when I
renamed status => event_status I needed to also create a
service_status to make things compile. It's accurate enough to move
forward.
Because this is really a Neutron only API, this is moved towards the
bottom of the API list, to make it clear this isn't really designed to
be used by end user apps.
Part of bp:api-ref-in-rst
Change-Id: I3ed46eec1c33a63b7a89d6d6b5eeda574effdc56
This completes all 4 phases of the extensions resource.
* List method was added
* Error codes updated as exist in code
* Updates parameters.yaml to match actual descriptions for parameters
* Update body to be a lot stronger about what our deprecation means and why.
Part of bp:api-ref-in-rst
Change-Id: I003fc1cc84cd429fbdc0c4f0847be81d920d3561
Verified the API document with source for methods available and
response codes used. Recorded HTTP methods to match wiki.
Marked the associate/disassociate sections as deprecated (as they are
nova-net only), and added some warnings in the docs about their use.
Part of bp:api-ref-in-rst
Change-Id: I63c56a546fe3a97eaa16ce41999593eaf650b538
Jenkins