Change doc links for pike branch
Part of the release process dictates that we update documentation links to point to the state on the pike branch Change-Id: I9dc33929bd071697ac96b6ab39bb855264625ae0
This commit is contained in:
parent
1f0e1e0885
commit
40fa86a5e2
|
@ -16,7 +16,7 @@ Currently booting from a volume requires:
|
|||
|
||||
- Bare Metal service version 9.0.0
|
||||
- Bare Metal API microversion 1.33 or later
|
||||
- A driver that utilizes the `PXE boot mechanism <https://docs.openstack.org/ironic/latest/install/configure-pxe.html>`_.
|
||||
- A driver that utilizes the `PXE boot mechanism <https://docs.openstack.org/ironic/pike/install/configure-pxe.html>`_.
|
||||
Currently booting from a volume is supported by the reference drivers that
|
||||
utilize PXE boot mechanisms when iPXE is enabled.
|
||||
- iPXE is an explicit requirement, as it provides the mechanism that attaches
|
||||
|
|
|
@ -88,7 +88,7 @@ The ``ilo`` hardware type supports following hardware interfaces:
|
|||
|
||||
.. note::
|
||||
``ilo`` is the default ``inspect`` interface for ``ilo``
|
||||
hardware type. `Ironic Inspector <https://docs.openstack.org/ironic-inspector/latest/>`_
|
||||
hardware type. `Ironic Inspector <https://docs.openstack.org/ironic-inspector/pike/>`_
|
||||
needs to be configured to use ``inspector`` as the inspect interface.
|
||||
|
||||
* management
|
||||
|
|
|
@ -204,7 +204,7 @@ RAID interface. For example, to update all nodes use:
|
|||
the ramdisk (more specifically, a `hardware manager`_ used in it),
|
||||
not on the driver.
|
||||
|
||||
.. _hardware manager: https://docs.openstack.org/ironic-python-agent/latest/contributor/hardware_managers.html
|
||||
.. _hardware manager: https://docs.openstack.org/ironic-python-agent/pike/contributor/hardware_managers.html
|
||||
|
||||
Network and storage
|
||||
~~~~~~~~~~~~~~~~~~~
|
||||
|
|
|
@ -47,7 +47,7 @@ and provide the file or HTTP URL to the Bare Metal service.
|
|||
For the format of the configuration drive, Bare Metal service expects a
|
||||
``gzipped`` and ``base64`` encoded ISO 9660 [*]_ file with a ``config-2``
|
||||
label. The
|
||||
`ironic client <https://docs.openstack.org/python-ironicclient/latest/>`_
|
||||
`ironic client <https://docs.openstack.org/python-ironicclient/pike/>`_
|
||||
can generate a configuration drive in the `expected format`_. Just pass a
|
||||
directory path containing the files that will be injected into it via the
|
||||
``--config-drive`` parameter of the ``node-set-provision-state`` command,
|
||||
|
@ -158,5 +158,5 @@ but in order to use it we should follow some rules:
|
|||
For more information see `how to configure cloud-init data sources
|
||||
<https://docs.openstack.org/diskimage-builder/latest/elements/cloud-init-datasources/README.html>`_.
|
||||
|
||||
.. _`expected format`: https://docs.openstack.org/nova/latest/user/vendordata.html
|
||||
.. _`expected format`: https://docs.openstack.org/nova/pike/user/vendordata.html
|
||||
.. _disk-image-builder: https://docs.openstack.org/diskimage-builder/latest/
|
||||
|
|
|
@ -12,7 +12,7 @@ the `CoreOS tools`_ at:
|
|||
* `CoreOS deploy kernel <https://tarballs.openstack.org/ironic-python-agent/coreos/files/coreos_production_pxe.vmlinuz>`_
|
||||
* `CoreOS deploy ramdisk <https://tarballs.openstack.org/ironic-python-agent/coreos/files/coreos_production_pxe_image-oem.cpio.gz>`_
|
||||
|
||||
.. _ironic-python-agent: https://docs.openstack.org/ironic-python-agent/latest/
|
||||
.. _ironic-python-agent: https://docs.openstack.org/ironic-python-agent/pike/
|
||||
|
||||
Building from source
|
||||
--------------------
|
||||
|
|
|
@ -313,4 +313,4 @@ See :doc:`/admin/drivers` for the required configuration of each driver.
|
|||
.. _driver composition reform specification: https://specs.openstack.org/openstack/ironic-specs/specs/approved/driver-composition-reform.html
|
||||
.. _setup.cfg: https://git.openstack.org/cgit/openstack/ironic/tree/setup.cfg
|
||||
.. _iSCSI: https://en.wikipedia.org/wiki/ISCSI
|
||||
.. _ironic-inspector: https://docs.openstack.org/ironic-inspector/latest/
|
||||
.. _ironic-inspector: https://docs.openstack.org/ironic-inspector/pike/
|
||||
|
|
|
@ -19,7 +19,7 @@ of the following ways:
|
|||
<https://docs.openstack.org/security-guide/secure-communication/tls-proxies-and-http-services.html>`_
|
||||
|
||||
* `Using native SSL support in swift
|
||||
<https://docs.openstack.org/swift/latest/deployment_guide.html>`_
|
||||
<https://docs.openstack.org/swift/pike/deployment_guide.html>`_
|
||||
(recommended only for testing purpose by swift).
|
||||
|
||||
.. _EnableHTTPSinGlance:
|
||||
|
@ -32,7 +32,7 @@ image service does not use HTTPS, but it is required for secure communication.
|
|||
It can be enabled by making the following changes to ``/etc/glance/glance-api.conf``:
|
||||
|
||||
#. `Configuring SSL support
|
||||
<https://docs.openstack.org/glance/latest/configuration/configuring.html#configuring-ssl-support>`_
|
||||
<https://docs.openstack.org/glance/pike/configuration/configuring.html#configuring-ssl-support>`_
|
||||
|
||||
#. Restart the glance-api service::
|
||||
|
||||
|
@ -42,7 +42,7 @@ It can be enabled by making the following changes to ``/etc/glance/glance-api.co
|
|||
Debian/Ubuntu:
|
||||
sudo service glance-api restart
|
||||
|
||||
See the `Glance <https://docs.openstack.org/glance/latest/>`_ documentation,
|
||||
See the `Glance <https://docs.openstack.org/glance/pike/>`_ documentation,
|
||||
for more details on the Image service.
|
||||
|
||||
Enabling HTTPS communication between Image service and Object storage
|
||||
|
@ -56,7 +56,7 @@ To enable secure HTTPS communication between Image service and Object storage fo
|
|||
#. :ref:`EnableHTTPSinSwift`
|
||||
|
||||
#. `Configure Swift Storage Backend
|
||||
<https://docs.openstack.org/glance/latest/configuration/configuring.html#configuring-the-swift-storage-backend>`_
|
||||
<https://docs.openstack.org/glance/pike/configuration/configuring.html#configuring-the-swift-storage-backend>`_
|
||||
|
||||
#. :ref:`EnableHTTPSinGlance`
|
||||
|
||||
|
|
|
@ -451,7 +451,7 @@ To move a node from ``manageable`` to ``available`` provision state:
|
|||
For more details on the Bare Metal service's state machine, see the
|
||||
:doc:`/contributor/states` documentation.
|
||||
|
||||
.. _ComputeCapabilitiesFilter: https://docs.openstack.org/nova/latest/user/filter-scheduler.html
|
||||
.. _ComputeCapabilitiesFilter: https://docs.openstack.org/nova/pike/user/filter-scheduler.html
|
||||
|
||||
Logical names
|
||||
-------------
|
||||
|
|
|
@ -74,8 +74,8 @@ bifrost_
|
|||
A set of Ansible playbooks that automates the task of deploying a base image
|
||||
onto a set of known hardware using ironic in a standalone mode.
|
||||
|
||||
.. _python-ironicclient: https://docs.openstack.org/python-ironicclient/latest/
|
||||
.. _ironic-inspector: https://docs.openstack.org/ironic-inspector/latest/
|
||||
.. _python-ironicclient: https://docs.openstack.org/python-ironicclient/pike/
|
||||
.. _ironic-inspector: https://docs.openstack.org/ironic-inspector/pike/
|
||||
.. _diskimage-builder: https://docs.openstack.org/diskimage-builder/latest/
|
||||
.. _bifrost: https://docs.openstack.org/bifrost/latest/
|
||||
.. _bifrost: https://docs.openstack.org/bifrost/pike/
|
||||
|
||||
|
|
|
@ -171,4 +171,4 @@ Configuring ironic-conductor service
|
|||
Ubuntu:
|
||||
sudo service ironic-conductor restart
|
||||
|
||||
.. _Keystoneauth documentation: https://docs.openstack.org/keystoneauth/latest/
|
||||
.. _Keystoneauth documentation: https://docs.openstack.org/keystoneauth/pike/
|
||||
|
|
|
@ -18,7 +18,7 @@ Enabling the local boot is different when Bare Metal service is used with
|
|||
Compute service and without it.
|
||||
The following sections will describe both methods.
|
||||
|
||||
.. _ironic-python-agent: https://docs.openstack.org/ironic-python-agent/latest/
|
||||
.. _ironic-python-agent: https://docs.openstack.org/ironic-python-agent/pike/
|
||||
|
||||
|
||||
Enabling local boot with Compute service
|
||||
|
|
|
@ -4,7 +4,7 @@ Notifications
|
|||
The Bare Metal service supports the emission of notifications, which are
|
||||
messages sent on a message broker (like RabbitMQ or anything else supported by
|
||||
the `oslo messaging library
|
||||
<https://docs.openstack.org/oslo.messaging/latest/reference/notifier.html>`_) that
|
||||
<https://docs.openstack.org/oslo.messaging/pike/reference/notifier.html>`_) that
|
||||
indicate various events which occur, such as when a node changes power states.
|
||||
These can be consumed by an external service reading from the message bus. For
|
||||
example, `Searchlight <https://wiki.openstack.org/wiki/Searchlight>`_ is an
|
||||
|
|
|
@ -55,7 +55,7 @@ and ``s==`` (for string values). The supported operators are:
|
|||
* For numerical values:
|
||||
|
||||
* ``=`` equal to or greater than. This is equivalent to ``>=`` and is
|
||||
supported for `legacy reasons <https://docs.openstack.org/nova/latest/user/filter-scheduler.html#filtering>`_
|
||||
supported for `legacy reasons <https://docs.openstack.org/nova/pike/user/filter-scheduler.html#filtering>`_
|
||||
* ``==`` equal to
|
||||
* ``!=`` not equal to
|
||||
* ``>=`` greater than or equal to
|
||||
|
|
|
@ -62,7 +62,7 @@ There are however some limitations for different drivers:
|
|||
|
||||
Steps to start a deployment are pretty similar to those when using Compute:
|
||||
|
||||
#. To use the `ironic CLI <https://docs.openstack.org/python-ironicclient/latest/cli/>`_,
|
||||
#. To use the `ironic CLI <https://docs.openstack.org/python-ironicclient/pike/cli/>`_,
|
||||
set up these environment variables. Since no authentication strategy is
|
||||
being used, the value can be any string for OS_AUTH_TOKEN. IRONIC_URL is
|
||||
the URL of the ironic-api process.
|
||||
|
|
|
@ -124,4 +124,4 @@ following command.
|
|||
$ ironic node-set-maintenance $NODE_UUID off
|
||||
|
||||
|
||||
.. _ironic-python-agent: https://docs.openstack.org/ironic-python-agent/latest/
|
||||
.. _ironic-python-agent: https://docs.openstack.org/ironic-python-agent/pike/
|
||||
|
|
Loading…
Reference in New Issue