Update api-ref location

The api documentation is now published on docs.openstack.org instead
of developer.openstack.org. Update all links that are changed to the
new location.

Note that Neutron publishes to api-ref/network, not networking anymore.

Note that redirects will be set up as well but let's point now to the
new location.

For details, see:
http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007828.html

Change-Id: Id2cf3aa252df6db46575b5988e4937ecfc6792bb

1 files changed, 5 insertions, 5 deletions

diff --git a/api-ref/source/servers-actions.inc b/api-ref/source/servers-actions.inc
index 22871e6ed6..4e162d2cf4 100644
--- a/api-ref/source/servers-actions.inc
+++ b/api-ref/source/servers-actions.inc
@@ -38,7 +38,7 @@ A pool of floating IP addresses, configured by the cloud administrator,
 is available in OpenStack Compute. The project quota defines the maximum
 number of floating IP addresses that you can allocate to the project.
 After you `create (allocate) a floating IPaddress
-<http://developer.openstack.org/api-ref/compute/#create-allocate-floating-ip-address>`__
+<https://docs.openstack.org/api-ref/compute/#create-allocate-floating-ip-address>`__
 for a project, you can associate that address with the server. Specify
 the ``addFloatingIp`` action in the request body.
 
@@ -380,23 +380,23 @@ Specify the ``lock`` action in the request body.
 Most actions by non-admin users are not allowed to the server
 after this operation is successful and the server is locked.
 See the "Lock, Unlock" item in `Server actions
-<https://developer.openstack.org/api-guide/compute/server_concepts.html#server-actions>`_
+<https://docs.openstack.org/api-guide/compute/server_concepts.html#server-actions>`_
 for the restricted actions.
 But administrators can perform actions on the server
 even though the server is locked. Note that from microversion 2.73 it is
 possible to specify a reason when locking the server.
 
 The `unlock action
-<https://developer.openstack.org/api-ref/compute/#unlock-server-unlock-action>`_
+<https://docs.openstack.org/api-ref/compute/#unlock-server-unlock-action>`_
 will unlock a server in locked state so additional actions can
 be performed on the server by non-admin users.
 
 You can know whether a server is locked or not and the ``locked_reason``
 (if specified, from the 2.73 microversion) by the `List Servers Detailed API
-<https://developer.openstack.org/api-ref/compute/#list-servers-detailed>`_
+<https://docs.openstack.org/api-ref/compute/#list-servers-detailed>`_
 or
 the `Show Server Details API
-<https://developer.openstack.org/api-ref/compute/#show-server-details>`_.
+<https://docs.openstack.org/api-ref/compute/#show-server-details>`_.
 
 Policy defaults enable only users with the administrative role or
 the owner of the server to perform this operation. Cloud providers