Update links in docs to latest

To avoid links to OpenStack docs getting out of date in our docs, use
the latest version.

Ideally after cutting each stable branch we should change these links to
use the current release.

Co-Authored-By: Isaiah Inuwa
Change-Id: Ia1e3c720f4e688861b8f76874a3943b0f4e50b17
This commit is contained in:
Mark Goddard 2019-02-28 09:29:42 +00:00
parent 3a5ef38f3b
commit fba5e1ce7d
5 changed files with 11 additions and 9 deletions

View File

@ -166,4 +166,4 @@ OpenStack HyperV services can be inspected and managed from PowerShell:
For more information on OpenStack HyperV, see For more information on OpenStack HyperV, see
`Hyper-V virtualization platform `Hyper-V virtualization platform
<https://docs.openstack.org/ocata/config-reference/compute/hypervisor-hyper-v.html>`__. <https://docs.openstack.org/nova/latest/admin/configuration/hypervisor-hyper-v.html>`__.

View File

@ -271,5 +271,5 @@ KVM/QEMU deployment.
For more information on OpenStack vSphere, see For more information on OpenStack vSphere, see
`VMware vSphere `VMware vSphere
<https://docs.openstack.org/ocata/config-reference/compute/hypervisor-vmware.html>`__, <https://docs.openstack.org/nova/latest/admin/configuration/hypervisor-vmware.html>`__,
`VMware-NSX package <https://github.com/openstack/vmware-nsx>`_. `VMware-NSX package <https://github.com/openstack/vmware-nsx>`_.

View File

@ -165,7 +165,8 @@ dmesg on the compute node where the instance was placed.
[ 2896.850028] ixgbe 0000:05:00.0: Setting VLAN 1000, QOS 0x0 on VF 3 [ 2896.850028] ixgbe 0000:05:00.0: Setting VLAN 1000, QOS 0x0 on VF 3
[ 2897.403367] vfio-pci 0000:05:10.4: enabling device (0000 -> 0002) [ 2897.403367] vfio-pci 0000:05:10.4: enabling device (0000 -> 0002)
For more information see `OpenStack SRIOV documentation <https://docs.openstack.org/neutron/pike/admin/config-sriov.html>`_. For more information see `OpenStack SRIOV documentation
<https://docs.openstack.org/neutron/latest/admin/config-sriov.html>`_.
Nova SRIOV Nova SRIOV
~~~~~~~~~~ ~~~~~~~~~~
@ -221,4 +222,5 @@ Start a new instance using the flavor:
Verify VF devices were created and the instance starts successfully as in Verify VF devices were created and the instance starts successfully as in
the Neutron SRIOV case. the Neutron SRIOV case.
For more information see `OpenStack PCI passthrough documentation <https://docs.openstack.org/nova/pike/admin/pci-passthrough.html>`_. For more information see `OpenStack PCI passthrough documentation
<https://docs.openstack.org/nova/latest/admin/pci-passthrough.html>`_.

View File

@ -171,8 +171,8 @@ To generate Swift container ring, run the following commands:
/etc/kolla/config/swift/${ring}.builder rebalance; /etc/kolla/config/swift/${ring}.builder rebalance;
done done
For more information, see For more information, see `the Swift documentation
https://docs.openstack.org/project-install-guide/object-storage/ocata/initial-rings.html <https://docs.openstack.org/swift/latest/install/initial-rings.html>`__.
Deploying Deploying
~~~~~~~~~ ~~~~~~~~~

View File

@ -305,15 +305,15 @@ There are a few options that are required to deploy Kolla-Ansible:
kolla_install_type: "source" kolla_install_type: "source"
To use DockerHub images, the default image tag has to be overridden. Images are To use DockerHub images, the default image tag has to be overridden. Images are
tagged with release names. For example to use stable Pike images set tagged with release names. For example to use stable Rocky images set
.. code-block:: console .. code-block:: console
openstack_release: "pike" openstack_release: "rocky"
It's important to use same version of images as kolla-ansible. That It's important to use same version of images as kolla-ansible. That
means if pip was used to install kolla-ansible, that means it's latest stable means if pip was used to install kolla-ansible, that means it's latest stable
version so ``openstack_release`` should be set to queens. If git was used with version so ``openstack_release`` should be set to rocky. If git was used with
master branch, DockerHub also provides daily builds of master branch (which is master branch, DockerHub also provides daily builds of master branch (which is
tagged as ``master``): tagged as ``master``):