This commits define new parameter sort_key_flavor
and sort_dir_flavor for flavor List API and define
the correct default values for those.
Partially implements blueprint api-ref-in-rst
Change-Id: I2915a5bccebfeddf66c825b0272af86e3fd7da19
'osapi_hide_server_address_states' does not hide the
address field in server/ips APIs so address paramater
for this API is wrong and this commit fis the same.
Also fixing the 'version' parameter.
Partially implements blueprint api-ref-in-rst
Change-Id: I22d6ab97d14779fe3a32c23a5148b4eb59f1034f
The parameter 'name' is for security group, not server group.
This patch fixes the description.
Partially implements blueprint api-ref-in-rst
Change-Id: I954b91c47bf4766be430ace2783089c7f59f9324
This patch verifies the example & parameters of
os-security-group-default-rules.inc
part of bp:api-ref-in-rst
Change-Id: I1e94aad4c9f763c41d921d761c215cc2de03af5a
The openstackdocstheme includes a bug reference link, which defaults
to openstack manuals. We want to update this to be a Nova bug instead.
This also cleans up the pre openstackdocstheme support code
Change-Id: Iace4619c37b04b1504a7051e9e5274b2a3b77c24
Modified type of block_migration from input params
of os-migrateLive API based on API version 2.25
Change-Id: I82c6537d137b462dbe6d05c07a9b3afb5a1501d5
Closes-Bug: #1551782
We need some magic to keep the build working as we move away from
oslosphinx and towards openstackdocstheme, the theme we are going to
use for all the docs.
For more details see:
http://lists.openstack.org/pipermail/openstack-dev/2016-August/101996.html
Change-Id: I378b1afade4725758c024e06b239b0af64d1b19a
This adds the 2.37 microversion to the REST API for automatically
allocating a network, i.e. get me a network.
The majority of the changes to the REST API concern request
validation. 'networks' is now required in the server POST body
after this microversion. The 'auto' or 'none' special network
uuid values are used, but if specified, can not be specified
with any other requested network values.
The other special case that is checked is when the minimum
compute service version is not new enough to support this change,
i.e. a Mitaka compute will not have the network API code that
knows how to deal with the special auto/none network IDs. Because
the REST API is checking the service version, the service caches
the service version after the first check. Once all computes are
updated to Newton then a restart of the nova-api service(s) will
be required to flush the cache. A release note is provided for
this situation.
The api-ref docs are also updated for this microversion including
an example API sample request.
The matching Tempest change to test this is here:
I89b18709e0cfbbcbf9be96a91a13a1356cdf85b0
The matching python-novaclient change is here:
I6636ddcd3be7bf393d2d69cc6c1ba5c7d65ff674
Implements blueprint get-me-a-network
Change-Id: I89b18709e0cfbbcbf9be96a91a13a1356cdf85b0
Currently imageRef in server create, rebuild and rescue
operation can be accepted as random url which contains image
UUID and fetch the UUID from that.
As /images proxy APIs are deprecated, and ImageRef in
server creation etc are UUID only and valid against glance.
This patch makes imageRef handling as UUID only and
return 400 if non UUID are requested.
NOTE- Previously nova use to allow the empty string which was
ok in case of boot from volume.
We will keep the same behavior of allowing empty string in case of
boot from volume only and 400 in all other case.
Closes-Bug: #1607229
Change-Id: I49f4da62c1b5b3fd8c5f67039ae113f76722b26c
os-certificates API has been deprecated in
I0ffa9200d8b4f52da4751e731aecffe09fd3d4be
This patch just add 'DEPRECATED' in its heading in api-ref
to make it more clear.
Change-Id: I5ef30330e033eeb0576d3b4d31441d5481cc7d2e
Proxy APIs are deprecated in microversion 2.36 which means
all proxy APIs will return 404 after 2.35 version.
It will be nice to mention that explicitly in api-ref too.
Partially implements blueprint deprecate-api-proxies
Change-Id: Iad210d215fb98bc247f049b23b97d8d7d4265c82
Coming out of the Nova midcycle we decided we really needed to
deprecate the os-certificates API and service. It is not used by any
of the rest of Nova. It's an API that requires a dedicated daemon to
be run. It's making Nova assume the responsibility for generating
secure certificates, even though it's not really managing entropy in
any sane way (which is why nova-cert is a service, so you could stick
these on all your computes so as to not run out of entropy).
Change-Id: I0ffa9200d8b4f52da4751e731aecffe09fd3d4be
This fixes the direct links to the security groups, security
group rules and floating IPs (layer 3) extensions in the
neutron api-ref.
Part of blueprint deprecate-api-proxies
Change-Id: Ib2c4ed478714b187fde8b7c42da15cc56b26675e
verified all sample files is correct and adjust
some format of the request Json file
part of bp:api-ref-in-rst
Change-Id: Ie9dd24858056337bcae9b03259d4f84de4fc1ab8
All proxy APIs are now deprecated which includes
sec grp APIs also.
But list sec grps by server API-
(/servers/{server_id}/os-security-groups) is not
deprecated so this should be separated from deprecated
sec grp APIs in api-ref.
Partially implements blueprint deprecate-api-proxies
Change-Id: I9f9e2cf5f8e390cecd9e1794a0af1a3fcc24f149
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
Jenkins