openstack
/
nova
Code Issues Proposed changes

Mention proxy API deprecation microversion in api-ref 

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
This commit is contained in:
ghanshyam 2016-08-01 14:59:53 +09:00
parent eab62c0d8a
commit b4d0b9a11c
14 changed files with 15 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
api-ref/source/images.inc
View File

@ -8,7 +8,7 @@
These APIs are proxy calls to the Image service. Nova has
deprecated all the proxy APIs and users should use the native APIs
instead.
instead. These will fail with a 404 after microversion 2.35.
See: `Relevant Image APIs
<http://developer.openstack.org/api-ref-image-v2.html#images-images-v2>`__.

2
api-ref/source/os-baremetal-nodes.inc
View File

@ -9,7 +9,7 @@
These APIs are proxy calls to the Ironic service. They exist for
legacy compatibility, but no new applications should use them.
Nova has deprecated all the proxy APIs and users should use the native
APIs instead.
APIs instead. These will fail with a 404 after microversion 2.35.
See: `Relevant Bare metal APIs
<http://developer.openstack.org/api-ref/baremetal/index.html#nodes-nodes>`__.

2
api-ref/source/os-fixed-ips.inc
View File

@ -8,7 +8,7 @@
These APIs are proxy calls to the Network service. Nova has
deprecated all the proxy APIs and users should use the native APIs
instead.
instead. These will fail with a 404 after microversion 2.35.
Shows data for a fixed IP, such as host name, CIDR, and address. Also,
reserves and releases a fixed IP address.

2
api-ref/source/os-floating-ip-dns.inc
View File

@ -11,7 +11,7 @@
These APIs are proxy calls to the Network service. Nova has
deprecated all the proxy APIs and users should use the native APIs
instead.
instead. These will fail with a 404 after microversion 2.35.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref-networking-v2-ext.html>`__.

2
api-ref/source/os-floating-ip-pools.inc
View File

@ -8,7 +8,7 @@
These APIs are proxy calls to the Network service. Nova has
deprecated all the proxy APIs and users should use the native APIs
instead.
instead. These will fail with a 404 after microversion 2.35.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref-networking-v2-ext.html>`__.

2
api-ref/source/os-floating-ips-bulk.inc
View File

@ -8,7 +8,7 @@
These APIs are proxy calls to the Network service. Nova has
deprecated all the proxy APIs and users should use the native APIs
instead.
instead. These will fail with a 404 after microversion 2.35.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref-networking-v2-ext.html>`__.

2
api-ref/source/os-floating-ips.inc
View File

@ -11,7 +11,7 @@
These APIs are proxy calls to the Network service. Nova has
deprecated all the proxy APIs and users should use the native APIs
instead.
instead. These will fail with a 404 after microversion 2.35.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref/networking/v2-ext/index.html#layer-3-networking-routers-floatingips>`__.

1
api-ref/source/os-fping.inc
View File

@ -8,6 +8,7 @@
This API only works with ``nova-network`` which is
deprecated. It should be avoided in any new applications.
These will fail with a 404 after microversion 2.35.
Pings instances and reports which instances are alive.

3
api-ref/source/os-networks.inc
View File

@ -15,7 +15,8 @@
``neutron`` when appropriate, but as with all translation
proxies, this is far from perfect compatibility. These
APIs should be avoided in new applications in favor of
using ``neutron`` directly.
using ``neutron`` directly. These will fail with a 404
after microversion 2.35.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref-networking-v2.html#networks>`__.

1
api-ref/source/os-security-group-default-rules.inc
View File

@ -11,6 +11,7 @@
This API only available with ``nova-network`` which is
deprecated. It should be avoided in any new applications.
These will fail with a 404 after microversion 2.35.
Lists, shows information for, and creates default security group rules.

2
api-ref/source/os-security-group-rules.inc
View File

@ -10,7 +10,7 @@
These APIs are proxy calls to the Network service. Nova has
deprecated all the proxy APIs and users should use the native APIs
instead.
instead. These will fail with a 404 after microversion 2.35.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref/networking/v2-ext/index.html#security-group-rules-security-group-rules>`__.

2
api-ref/source/os-security-groups.inc
View File

@ -11,7 +11,7 @@
These APIs are proxy calls to the Network service. Nova has
deprecated all the proxy APIs and users should use the native APIs
instead.
instead. These will fail with a 404 after microversion 2.35.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref/networking/v2-ext/index.html#security-groups-security-groups>`__.

2
api-ref/source/os-tenant-network.inc
View File

@ -11,7 +11,7 @@
These APIs are proxy calls to the Network service. Nova has
deprecated all the proxy APIs and users should use the native APIs
instead.
instead. These will fail with a 404 after microversion 2.35.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref-networking-v2-ext.html>`__.

2
api-ref/source/os-volumes.inc
View File

@ -8,7 +8,7 @@
These APIs are proxy calls to the Volume service. Nova has
deprecated all the proxy APIs and users should use the native APIs
instead.
instead. These will fail with a 404 after microversion 2.35.
See: `Relevant Volume APIs
<http://developer.openstack.org/api-ref-blockstorage-v2.html#volumes-v2-volumes>`__.