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
* Add doc for request without version in the url
* Add a link reference for microversion detail
Part of bp:api-ref-in-rst
Change-Id: Iadee4623fe70c43ad38c087e027f7e4cf01fea12
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
These methods were already verified in another change. The author forgot to
remove the needs:method_verification line from their change.
See change#314255
Part of bp:api-ref-in-rst
Change-Id: I13fb305f58df0b864bc27db5107601e4ee8842de
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
os-api-ref is released on pypi now, so we can move to using it instead
of our in tree version. All future extension fixes will happen over
there instead of here.
Change-Id: Iee4b9c94b8b66a5b0481dd0b15beda03328c4f31
Depends-On: I0e615d36a2e5a8fa0d83f20bdcc2c33ad868ebd5
There have been at least a couple of bugs about not being able
to create egress security group rules in Nova, which is because
nova-network does not support them. Neutron does, but Nova does
not proxy this to Neutron, nor will it.
So add a note in the api-ref docs for creating security group
rules about the egress rule limitation with nova-network.
Change-Id: Idc79cd1718b52db8611fd108b23f176f925221a6
Related-Bug: #1579749
Related-Bug: #1267140
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
Jenkins