Better wording for micorversion 2.36
make it follow other descriptions, use start from to make it clear 2.36 is the first microversion deprecate those proxy Implements: blueprint api-ref-in-rst-ocata Change-Id: Iadf4bb6fa8e4a959a734f354206e2e1f4739e367
This commit is contained in:
14 changed files with 14 additions and 14 deletions
@@ -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. These will fail with a 404 after microversion 2.35.
instead. These will fail with a 404 starting from microversion 2.36.
See: `Relevant Image APIs
<http://developer.openstack.org/api-ref-image-v2.html#images-images-v2>`__.
@@ -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. These will fail with a 404 after microversion 2.35.
APIs instead. These will fail with a 404 starting from microversion 2.36.
See: `Relevant Bare metal APIs
<http://developer.openstack.org/api-ref/baremetal/index.html#nodes-nodes>`__.
@@ -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. These will fail with a 404 after microversion 2.35.
instead. These will fail with a 404 starting from microversion 2.36.
Shows data for a fixed IP, such as host name, CIDR, and address. Also,
reserves and releases a fixed IP address.
@@ -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. These will fail with a 404 after microversion 2.35.
instead. These will fail with a 404 starting from microversion 2.36.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref-networking-v2-ext.html>`__.
@@ -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. These will fail with a 404 after microversion 2.35.
instead. These will fail with a 404 starting from microversion 2.36.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref-networking-v2-ext.html>`__.
@@ -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. These will fail with a 404 after microversion 2.35.
instead. These will fail with a 404 starting from microversion 2.36.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref-networking-v2-ext.html>`__.
@@ -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. These will fail with a 404 after microversion 2.35.
instead. These will fail with a 404 starting from microversion 2.36.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref-networking-v2.html#networks>`__.
@@ -8,7 +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.
These will fail with a 404 starting from microversion 2.36.
Pings instances and reports which instances are alive.
@@ -16,7 +16,7 @@
proxies, this is far from perfect compatibility. These
APIs should be avoided in new applications in favor of
using ``neutron`` directly. These will fail with a 404
after microversion 2.35.
starting from microversion 2.36.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref-networking-v2.html#networks>`__.
@@ -10,7 +10,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.
These will fail with a 404 starting from microversion 2.36.
Lists, shows information for, and creates default security group rules.
@@ -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. These will fail with a 404 after microversion 2.35.
instead. These will fail with a 404 starting from microversion 2.36.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref/networking/v2-ext/index.html#security-group-rules-security-group-rules>`__.
@@ -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. These will fail with a 404 after microversion 2.35.
instead. These will fail with a 404 starting from microversion 2.36.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref/networking/v2-ext/index.html#security-groups-security-groups>`__.
@@ -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. These will fail with a 404 after microversion 2.35.
instead. These will fail with a 404 starting from microversion 2.36.
See: `Relevant Network APIs
<http://developer.openstack.org/api-ref-networking-v2-ext.html>`__.
@@ -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. These will fail with a 404 after microversion 2.35.
instead. These will fail with a 404 starting from microversion 2.36.
See: `Relevant Volume APIs
<http://developer.openstack.org/api-ref-blockstorage-v2.html#volumes-v2-volumes>`__.
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.