openstack
/
ironic
Code Issues Proposed changes

Merge "Update the documentation links - install guide"

This commit is contained in:
Jenkins 2017-08-15 07:42:32 +00:00 committed by Gerrit Code Review
parent 62fd4d1a6e 5ff1e90e93
commit cc79484e86
11 changed files with 25 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/install/configdrive.rst
View File

@ -49,7 +49,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 <http://docs.openstack.org/developer/python-ironicclient/>`_
`ironic client <https://docs.openstack.org/python-ironicclient/latest/>`_
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,
@ -161,7 +161,7 @@ but in order to use it we should follow some rules:
DIB_CLOUD_INIT_DATASOURCES="ConfigDrive, OpenStack" disk-image-create -o fedora-cloud-image fedora baremetal
For more information see `how to configure cloud-init data sources
<http://docs.openstack.org/developer/diskimage-builder/elements/cloud-init-datasources/README.html>`_.
<https://docs.openstack.org/diskimage-builder/latest/elements/cloud-init-datasources/README.html>`_.
.. _`expected format`: http://docs.openstack.org/user-guide/cli_config_drive.html#openstack-metadata-format
.. _disk-image-builder: http://docs.openstack.org/developer/diskimage-builder/
.. _`expected format`: https://docs.openstack.org/nova/latest/user/vendordata.html
.. _disk-image-builder: https://docs.openstack.org/diskimage-builder/latest/

4
doc/source/install/configure-glance-images.rst
View File

@ -15,7 +15,7 @@ them to the Image service:
The `disk-image-builder`_ can be used to create user images required for
deployment and the actual OS which the user is going to run.
.. _disk-image-builder: http://docs.openstack.org/developer/diskimage-builder/
.. _disk-image-builder: https://docs.openstack.org/diskimage-builder/latest/
- Install diskimage-builder package (use virtualenv, if you don't
want to install anything globally):
@ -105,7 +105,7 @@ them to the Image service:
one kernel disk ``coreos_production_pxe.vmlinuz`` and one ram disk
``coreos_production_pxe_image-oem.cpio.gz``.
.. note:: If you want to customize your deploy images, please read `Image Builders <http://docs.openstack.org/developer/ironic-python-agent/index.html#image-builders>`_.
.. note:: If you want to customize your deploy images, please read `Image Builders <https://docs.openstack.org/ironic-python-agent/latest/install/index.html#image-builders>`_.
#. Add the deploy images to the Image service

6
doc/source/install/deploy-ramdisk.rst
View File

@ -12,7 +12,7 @@ the `CoreOS tools`_ at:
* `CoreOS deploy kernel <http://tarballs.openstack.org/ironic-python-agent/coreos/files/coreos_production_pxe.vmlinuz>`_
* `CoreOS deploy ramdisk <http://tarballs.openstack.org/ironic-python-agent/coreos/files/coreos_production_pxe_image-oem.cpio.gz>`_
.. _ironic-python-agent: http://docs.openstack.org/developer/ironic-python-agent/
.. _ironic-python-agent: https://docs.openstack.org/ironic-python-agent/latest/
Building from source
--------------------
@ -97,5 +97,5 @@ disk-image-builder
check the `diskimage-builder documentation`_ for other supported
operational systems.
.. _`diskimage-builder documentation`: http://docs.openstack.org/developer/diskimage-builder
.. _`diskimage-builder installation documentation`: http://docs.openstack.org/developer/diskimage-builder/user_guide/installation.html
.. _`diskimage-builder documentation`: https://docs.openstack.org/diskimage-builder/latest/
.. _`diskimage-builder installation documentation`: https://docs.openstack.org/diskimage-builder/latest/user_guide/installation.html

8
doc/source/install/enabling-https.rst
View File

@ -19,7 +19,7 @@ of the following ways:
<http://docs.openstack.org/security-guide/secure-communication/tls-proxies-and-http-services.html>`_
* `Using native SSL support in swift
<http://docs.openstack.org/developer/swift/deployment_guide.html>`_
<https://docs.openstack.org/swift/latest/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
<http://docs.openstack.org/developer/glance/configuring.html#configuring-ssl-support>`_
<https://docs.openstack.org/glance/latest/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 <http://docs.openstack.org/developer/glance/>`_ documentation,
See the `Glance <https://docs.openstack.org/glance/latest/>`_ 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
<http://docs.openstack.org/developer/glance/configuring.html#configuring-the-swift-storage-backend>`_
<https://docs.openstack.org/glance/latest/configuration/configuring.html#configuring-the-swift-storage-backend>`_
#. :ref:`EnableHTTPSinGlance`

8
doc/source/install/get_started.rst
View File

@ -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: http://docs.openstack.org/developer/python-ironicclient/
.. _ironic-inspector: http://docs.openstack.org/developer/ironic-inspector/
.. _diskimage-builder: http://docs.openstack.org/developer/diskimage-builder/
.. _bifrost: http://docs.openstack.org/developer/bifrost/
.. _python-ironicclient: https://docs.openstack.org/python-ironicclient/latest/
.. _ironic-inspector: https://docs.openstack.org/ironic-inspector/latest/
.. _diskimage-builder: https://docs.openstack.org/diskimage-builder/latest/
.. _bifrost: https://docs.openstack.org/bifrost/latest/

2
doc/source/install/include/configure-ironic-conductor.rst
View File

@ -173,4 +173,4 @@ Configuring ironic-conductor service
Ubuntu:
sudo service ironic-conductor restart
.. _Keystoneauth documentation: http://docs.openstack.org/developer/keystoneauth/
.. _Keystoneauth documentation: https://docs.openstack.org/keystoneauth/latest/

2
doc/source/install/include/local-boot-partition-images.rst
View File

@ -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: http://docs.openstack.org/developer/ironic-python-agent/
.. _ironic-python-agent: https://docs.openstack.org/ironic-python-agent/latest/
Enabling local boot with Compute service

6
doc/source/install/include/notifications.rst
View File

@ -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
<http://docs.openstack.org/developer/oslo.messaging/notifier.html>`_) that
<https://docs.openstack.org/oslo.messaging/latest/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
@ -12,5 +12,5 @@ OpenStack service that uses notifications to index (and make searchable)
resources from the Bare Metal service.
Notifications are disabled by default. For a complete list of available
notifications and instructions for how to enable them, see the `deploy
guide <http://docs.openstack.org/ironic/latest/admin/notifications.html>`_.
notifications and instructions for how to enable them, see the
:doc:`/admin/notifications`.

2
doc/source/install/include/root-device-hints.rst
View File

@ -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 <http://docs.openstack.org/developer/nova/filter_scheduler.html#ComputeCapabilitiesFilter>`_
supported for `legacy reasons <https://docs.openstack.org/nova/latest/user/filter-scheduler.html#filtering>`_
* ``==`` equal to
* ``!=`` not equal to
* ``>=`` greater than or equal to

2
doc/source/install/standalone.rst
View File

@ -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 <http://docs.openstack.org/developer/python-ironicclient/cli.html>`_,
#. To use the `ironic CLI <https://docs.openstack.org/python-ironicclient/latest/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.

2
doc/source/install/troubleshooting.rst
View File

@ -124,4 +124,4 @@ following command.
$ ironic node-set-maintenance $NODE_UUID off
.. _ironic-python-agent: http://docs.openstack.org/developer/ironic-python-agent/
.. _ironic-python-agent: https://docs.openstack.org/ironic-python-agent/latest/