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 the api-ref lives at
https://docs.openstack.org/api-ref/network/ and not /networking (that
was changed years ago). This change fixes this as well.

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: I492ee1fe97ef0cdae0db0524d5b4df373ba07d41
This commit is contained in:
Andreas Jaeger 2019-07-25 17:40:06 +02:00
parent 6d9283c1bc
commit faf7923a8e
12 changed files with 27 additions and 27 deletions

View File

@ -11,7 +11,7 @@ to the Networking service must provide an authentication token in
authenticating with the Identity service endpoint. For more information
about authentication with the Identity service, see `OpenStack Identity
service API v3
Reference <https://developer.openstack.org/api-ref/identity/v3/>`__.
Reference <https://docs.openstack.org/api-ref/identity/v3/>`__.
When the Identity service is enabled, it is not mandatory to specify the
project ID for resources in create requests because the project ID is
derived from the authentication token.

View File

@ -12,7 +12,7 @@ firewalls, and IPsec VPN.
For a detailed description of the Networking API abstractions and their
attributes, see the `OpenStack Networking API v2.0
Reference <https://developer.openstack.org/api-ref/networking/v2/>`__.
Reference <https://docs.openstack.org/api-ref/network/v2/>`__.
.. note::

View File

@ -65,7 +65,7 @@ Health monitor
LBaaS v2 has multiple implementations via different service plug-ins. The two
most common implementations use either an agent or the Octavia services. Both
implementations use the `LBaaS v2 API <https://developer.openstack.org/api-ref/networking/v2/#lbaas-2-0-stable>`_.
implementations use the `LBaaS v2 API <https://docs.openstack.org/api-ref/network/v2/#lbaas-2-0-stable>`_.
Configurations
~~~~~~~~~~~~~~

View File

@ -84,7 +84,7 @@ Limitations
resize, evacuate, live-migrate and unshelve after shelve-offload) is to be
implemented later. For the definitive documentation please refer to the
`Port with Resource Request chapter
<https://developer.openstack.org/api-guide/compute/port_with_resource_request.html>`_
<https://docs.openstack.org/api-guide/compute/port_with_resource_request.html>`_
of the OpenStack Compute API Guide.
* If an SR-IOV physical function is configured for use by the
@ -202,7 +202,7 @@ per-agent basis by setting
:oslo.config:option:`ovs.resource_provider_inventory_defaults`.
Valid values are all the
`optional parameters of the update resource provider inventory call
<https://developer.openstack.org/api-ref/placement/?expanded=update-resource-provider-inventory-detail#update-resource-provider-inventory>`_.
<https://docs.openstack.org/api-ref/placement/?expanded=update-resource-provider-inventory-detail#update-resource-provider-inventory>`_.
``/etc/neutron/plugins/ml2/ovs_agent.ini`` (on compute and network nodes):
@ -554,7 +554,7 @@ Links
* Nova documentation on using a port with ``resource_request``
* `API Guide <https://developer.openstack.org/api-guide/compute/port_with_resource_request.html>`_
* `API Guide <https://docs.openstack.org/api-guide/compute/port_with_resource_request.html>`_
* `Admin Guide <https://docs.openstack.org/nova/latest/admin/port_with_resource_request.html>`_
* Neutron spec: QoS minimum bandwidth allocation in Placement API
@ -571,9 +571,9 @@ Links
* Relevant OpenStack Networking API references
* https://developer.openstack.org/api-ref/network/v2/#agent-resources-synced-extension
* https://developer.openstack.org/api-ref/network/v2/#port-resource-request
* https://developer.openstack.org/api-ref/network/v2/#qos-minimum-bandwidth-rules
* https://docs.openstack.org/api-ref/network/v2/#agent-resources-synced-extension
* https://docs.openstack.org/api-ref/network/v2/#port-resource-request
* https://docs.openstack.org/api-ref/network/v2/#qos-minimum-bandwidth-rules
* Microversion histories

View File

@ -61,7 +61,7 @@ provider networks. We recommend using the following procedure:
* Segmentation ID
For example, ``provider1``, ``VLAN``, and ``2016``. See the
`API reference <https://developer.openstack.org/api-ref/networking/v2/#segments>`__
`API reference <https://docs.openstack.org/api-ref/network/v2/#segments>`__
for more information.
Within a network, use a unique physical network name for each segment which

View File

@ -251,5 +251,5 @@ Further Reading
* `Packet Pushers - Neutron Network Implementation on Linux <http://packetpushers.net/openstack-quantum-network-implementation-in-linux/>`_
* `OpenStack Networking Guide <../../admin/index.html>`_
* `Neutron - Layer 3 API extension <https://developer.openstack.org/api-ref/networking/v2/index.html#layer-3-networking>`_
* `Neutron - Layer 3 API extension <https://docs.openstack.org/api-ref/network/v2/index.html#layer-3-networking>`_
* `Darragh O'Reilly - The Quantum L3 router and floating IPs <http://techbackground.blogspot.com/2013/05/the-quantum-l3-router-and-floating-ips.html>`_

View File

@ -80,7 +80,7 @@ mature OpenStack projects:
* Exhaustive documentation: it is expected that each project will have a
:doc:`developer </contributor/index>`,
:doc:`user/operator </admin/index>`
and `API <http://developer.openstack.org/api-ref/networking/>`_
and `API <https://docs.openstack.org/api-ref/network/>`_
documentations available.
* Exhaustive OpenStack CI coverage: unit, functional, and tempest coverage
@ -229,7 +229,7 @@ Checklist
#. https://review.opendev.org/#/c/359143/
* How to port api-ref over to neutron-lib: to publish the subproject
API reference into the `Networking API guide <http://developer.openstack.org/api-ref/networking/>`_
API reference into the `Networking API guide <https://docs.openstack.org/api-ref/network/>`_
you must contribute the API documentation into neutron-lib's api-ref
directory as done in the `WADL/REST transition patch <https://review.opendev.org/#/c/327510/>`_.
Once this is done successfully, a link to the subproject API will

View File

@ -41,7 +41,7 @@ status=required
api=core
cli=openstack network *
notes=The ability to create, modify and delete networks.
https://developer.openstack.org/api-ref/networking/v2/#networks
https://docs.openstack.org/api-ref/network/v2/#networks
networking-ovs=complete
networking-linux-bridge=complete
networking-odl=complete
@ -54,7 +54,7 @@ status=required
api=core
cli=openstack subnet *
notes=The ability to create and manipulate subnets and subnet pools.
https://developer.openstack.org/api-ref/networking/v2/#subnets
https://docs.openstack.org/api-ref/network/v2/#subnets
networking-ovs=complete
networking-linux-bridge=complete
networking-odl=complete
@ -67,7 +67,7 @@ status=required
api=core
cli=openstack port *
notes=The ability to create and manipulate ports.
https://developer.openstack.org/api-ref/networking/v2/#ports
https://docs.openstack.org/api-ref/network/v2/#ports
networking-ovs=complete
networking-linux-bridge=complete
networking-odl=complete
@ -80,7 +80,7 @@ status=required
api=router
cli=openstack router *
notes=The ability to create and manipulate routers.
https://developer.openstack.org/api-ref/networking/v2/#routers-routers
https://docs.openstack.org/api-ref/network/v2/#routers-routers
networking-ovs=complete
networking-linux-bridge=complete
networking-odl=complete
@ -94,7 +94,7 @@ api=security-group
cli=openstack security group *
notes=Security groups are set by default, and can be modified to control
ingress & egress traffic.
https://developer.openstack.org/api-ref/networking/v2/#security-groups-security-groups
https://docs.openstack.org/api-ref/network/v2/#security-groups-security-groups
networking-ovs=complete
networking-linux-bridge=complete
networking-odl=complete
@ -142,7 +142,7 @@ title=Quality of Service
status=mature
api=qos
notes=Support for Neutron Quality of Service policies and API.
https://developer.openstack.org/api-ref/networking/v2/#qos-policies-qos
https://docs.openstack.org/api-ref/network/v2/#qos-policies-qos
networking-ovs=complete
networking-linux-bridge=partial
networking-odl=partial
@ -152,7 +152,7 @@ networking-ovn=complete
[operation.BGP]
title=Border Gateway Protocol
status=immature
notes=https://developer.openstack.org/api-ref/networking/v2/#bgp-mpls-vpn-interconnection
notes=https://docs.openstack.org/api-ref/network/v2/#bgp-mpls-vpn-interconnection
networking-ovs=complete
networking-linux-bridge=unknown
networking-odl=unknown
@ -177,7 +177,7 @@ status=mature
api=trunk
notes=Neutron extension to access lots of neutron networks over
a single vNIC as tagged/encapsulated traffic.
https://developer.openstack.org/api-ref/networking/v2/#trunk-networking
https://docs.openstack.org/api-ref/network/v2/#trunk-networking
networking-ovs=complete
networking-linux-bridge=complete
networking-odl=incomplete
@ -189,7 +189,7 @@ title=Metering
status=mature
api=metering
notes=Meter traffic at the L3 router levels.
https://developer.openstack.org/api-ref/networking/v2/#metering-labels-and-rules-metering-labels-metering-label-rules
https://docs.openstack.org/api-ref/network/v2/#metering-labels-and-rules-metering-labels-metering-label-rules
networking-ovs=complete
networking-linux-bridge=complete
networking-odl=incomplete

View File

@ -9,7 +9,7 @@ General Feature Support
This document covers the maturity and support of the Neutron API
and its API extensions. Details about the API can be found at
`Networking API v2.0 <http://developer.openstack.org/api-ref/networking/v2/>`_.
`Networking API v2.0 <https://docs.openstack.org/api-ref/network/v2/>`_.
When considering which capabilities should be marked as mature the
following general guiding principles were applied:

View File

@ -21,7 +21,7 @@ Neutron is an OpenStack project to provide "network connectivity as a service"
between interface devices (e.g., vNICs) managed by other OpenStack services
(e.g., nova). It implements the `Neutron API`_.
.. _`Neutron API`: https://developer.openstack.org/api-ref/networking/
.. _`Neutron API`: https://docs.openstack.org/api-ref/network/
This documentation is generated by the Sphinx toolkit and lives in the source
tree. Additional documentation on Neutron and other components of OpenStack
@ -84,7 +84,7 @@ Contributor Guide
API Extensions
--------------
Go to https://developer.openstack.org/api-ref/network/ for information about the OpenStack Network API and its extensions.
Go to https://docs.openstack.org/api-ref/network/ for information about the OpenStack Network API and its extensions.
Search
------

View File

@ -70,7 +70,7 @@ sriov_nic_opts = [
"max_unit:int, min_unit:int, "
"reserved:int, step_size:int, "
"See also: "
"https://developer.openstack.org/api-ref/placement/"
"https://docs.openstack.org/api-ref/placement/"
"#update-resource-provider-inventories")),
]

View File

@ -88,7 +88,7 @@ ovs_opts = [
"max_unit:int, min_unit:int, "
"reserved:int, step_size:int, "
"See also: "
"https://developer.openstack.org/api-ref/placement/"
"https://docs.openstack.org/api-ref/placement/"
"#update-resource-provider-inventories")),
cfg.BoolOpt('use_veth_interconnection', default=False,
help=_("Use veths instead of patch ports to interconnect the "