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
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
Verified the API document with source for methods available
and response codes used.
Part of bp:api-ref-in-rst
Change-Id: Ic3c0dc56a905985a62d719c9d05db1cf4d1c1000
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.
Part of bp:api-ref-in-rst
Change-Id: Ic462bbdd1f559a89aa43707cf510b6cf621ff4b0
Verify and update the response codes for the methods
based on what is in the code.
part of blueprint: api-ref-in-rst
Change-Id: Ib60e82b320ac7db3c2b50005f420db0aa43de492
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
Corrects the error status responses for
os-security-group-default-rules.inc
Part of bp:api-ref-in-rst
Change-Id: I668b6cffaa76db781a75ed0896717b58d58623c5
Jenkins