diff --git a/doc/config-reference/setup.cfg b/doc/config-reference/setup.cfg index 772fb69637..12743a21a0 100644 --- a/doc/config-reference/setup.cfg +++ b/doc/config-reference/setup.cfg @@ -3,7 +3,7 @@ name = configurationreference summary = OpenStack Configuration Reference author = OpenStack author-email = openstack-docs@lists.openstack.org -home-page = http://docs.openstack.org/ +home-page = https://docs.openstack.org/ classifier = Environment :: OpenStack Intended Audience :: Information Technology diff --git a/doc/config-reference/source/block-storage/drivers/coho-data-driver.rst b/doc/config-reference/source/block-storage/drivers/coho-data-driver.rst index 909a3e5444..4fad81f6ca 100644 --- a/doc/config-reference/source/block-storage/drivers/coho-data-driver.rst +++ b/doc/config-reference/source/block-storage/drivers/coho-data-driver.rst @@ -40,7 +40,7 @@ following capabilities in the OpenStack Block Storage API The QoS keys above must be created and associated with a volume type. For information about how to set the key-value pairs and associate them with a volume type, see the `volume qos -`_ +`_ section in the OpenStackClient command list. .. note:: diff --git a/doc/config-reference/source/block-storage/drivers/dell-equallogic-driver.rst b/doc/config-reference/source/block-storage/drivers/dell-equallogic-driver.rst index f5f54003f9..013ee26612 100644 --- a/doc/config-reference/source/block-storage/drivers/dell-equallogic-driver.rst +++ b/doc/config-reference/source/block-storage/drivers/dell-equallogic-driver.rst @@ -157,4 +157,4 @@ In this example: For information on configuring multiple back ends, see `Configure a multiple-storage back -end `__. +end `__. diff --git a/doc/config-reference/source/block-storage/drivers/emc-vmax-driver.rst b/doc/config-reference/source/block-storage/drivers/emc-vmax-driver.rst index 31a073fc91..03597e6328 100644 --- a/doc/config-reference/source/block-storage/drivers/emc-vmax-driver.rst +++ b/doc/config-reference/source/block-storage/drivers/emc-vmax-driver.rst @@ -1135,7 +1135,7 @@ these snapshots. The functionality to backup snapshots provides another layer of data protection. Please refer to `backup and restore volumes and -snapshots ` +snapshots ` for more more information. Enable attach and detach snapshot functionality diff --git a/doc/config-reference/source/block-storage/drivers/emc-vnx-driver.rst b/doc/config-reference/source/block-storage/drivers/emc-vnx-driver.rst index be3f74cdc8..81fb7293ad 100644 --- a/doc/config-reference/source/block-storage/drivers/emc-vnx-driver.rst +++ b/doc/config-reference/source/block-storage/drivers/emc-vnx-driver.rst @@ -179,7 +179,7 @@ The value of the option ``storage_protocol`` can be either ``fc`` or ``iscsi``, which is case insensitive. For more details on multiple back ends, see `Configure multiple-storage -back ends `_ +back ends `_ Required configurations ----------------------- diff --git a/doc/config-reference/source/block-storage/drivers/kaminario-driver.rst b/doc/config-reference/source/block-storage/drivers/kaminario-driver.rst index 22e2a29350..160436db18 100644 --- a/doc/config-reference/source/block-storage/drivers/kaminario-driver.rst +++ b/doc/config-reference/source/block-storage/drivers/kaminario-driver.rst @@ -100,8 +100,8 @@ Cinder Driver for single FC or iSCSI backend. scheduler_default_filters = DriverFilter,CapabilitiesFilter See following links for more information: - ``_ - ``_ + ``_ + ``_ #. Under the ``[DEFAULT]`` section, set the enabled_backends parameter with the iSCSI or FC back-end group @@ -189,7 +189,7 @@ The following steps are required to configure multiple K2 iSCSI/FC backends: ``Configure single Kaminario iSCSI/FC back end`` See `Configure multiple-storage back ends - `__ + `__ for additional information. #. Restart the cinder volume service for the changes to take effect. diff --git a/doc/config-reference/source/block-storage/drivers/solidfire-volume-driver.rst b/doc/config-reference/source/block-storage/drivers/solidfire-volume-driver.rst index 1e46bb9063..7ddaa870de 100644 --- a/doc/config-reference/source/block-storage/drivers/solidfire-volume-driver.rst +++ b/doc/config-reference/source/block-storage/drivers/solidfire-volume-driver.rst @@ -94,7 +94,7 @@ following capabilities in the OpenStack Block Storage API The QoS keys above no longer require to be scoped but must be created and associated to a volume type. For information about how to set the key-value pairs and associate them with a volume type, see the `volume qos -`_ +`_ section in the OpenStackClient command list. .. note:: diff --git a/doc/config-reference/source/block-storage/schedulers.rst b/doc/config-reference/source/block-storage/schedulers.rst index d9cd9a1278..31f1128093 100644 --- a/doc/config-reference/source/block-storage/schedulers.rst +++ b/doc/config-reference/source/block-storage/schedulers.rst @@ -6,6 +6,6 @@ Block Storage service uses the ``cinder-scheduler`` service to determine how to dispatch block storage requests. For more information, see `Cinder Scheduler Filters -`_ +`_ and `Cinder Scheduler Weights -`_. +`_. diff --git a/doc/config-reference/source/block-storage/volume-encryption.rst b/doc/config-reference/source/block-storage/volume-encryption.rst index 93cd9834fe..d3a50a9472 100644 --- a/doc/config-reference/source/block-storage/volume-encryption.rst +++ b/doc/config-reference/source/block-storage/volume-encryption.rst @@ -88,7 +88,7 @@ the volume. The OpenStack dashboard (horizon) supports creating the encrypted volume type as of the Kilo release. For instructions, see `Create an encrypted volume type -`_. +`_. Create an encrypted volume ~~~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/doc/config-reference/source/common-configurations/cache.rst b/doc/config-reference/source/common-configurations/cache.rst index ef876bc040..de95682d95 100644 --- a/doc/config-reference/source/common-configurations/cache.rst +++ b/doc/config-reference/source/common-configurations/cache.rst @@ -15,4 +15,4 @@ These options are supported by: For a complete list of all available cache configuration options, see `olso.cache configuration options -`_. +`_. diff --git a/doc/config-reference/source/common-configurations/cors.rst b/doc/config-reference/source/common-configurations/cors.rst index e4a2197b44..daca173eaf 100644 --- a/doc/config-reference/source/common-configurations/cors.rst +++ b/doc/config-reference/source/common-configurations/cors.rst @@ -7,12 +7,12 @@ a browser (JavaScript for example) to make requests to a domain, other than the one it was originated from. OpenStack services support CORS requests. For more information, see `cross-project features -`_ +`_ in OpenStack Administrator Guide, `CORS in Dashboard -`_, +`_, and `CORS in Object Storage service -`_. +`_. For a complete list of all available CORS configuration options, see `CORS configuration options -`_. +`_. diff --git a/doc/config-reference/source/compute/hypervisor-xen-libvirt.rst b/doc/config-reference/source/compute/hypervisor-xen-libvirt.rst index ef56900e46..f6ee2ec1ee 100644 --- a/doc/config-reference/source/compute/hypervisor-xen-libvirt.rst +++ b/doc/config-reference/source/compute/hypervisor-xen-libvirt.rst @@ -146,7 +146,7 @@ Use the following as a guideline for configuring Xen for use in OpenStack: #. **Image formats**: Xen supports raw, qcow2 and vhd image formats. For more information on image formats, refer to the `OpenStack Virtual - Image Guide `__ + Image Guide `__ and the `Storage Options Guide on the Xen Project Wiki `_. @@ -166,7 +166,7 @@ Use the following as a guideline for configuring Xen for use in OpenStack: For more more information on image metadata, refer to the `OpenStack Virtual Image Guide - `__. + `__. #. **Libguestfs file injection**: OpenStack compute nodes can use `libguestfs `_ to inject files into an instance's image prior diff --git a/doc/config-reference/source/compute/hypervisors.rst b/doc/config-reference/source/compute/hypervisors.rst index 61d41b3bac..64f352a918 100644 --- a/doc/config-reference/source/compute/hypervisors.rst +++ b/doc/config-reference/source/compute/hypervisors.rst @@ -20,7 +20,7 @@ for you to choose one. Most installations use only one hypervisor. However, you can use :ref:`ComputeFilter` and :ref:`ImagePropertiesFilter` to schedule different hypervisors within the same installation. The following links help you choose a hypervisor. -See http://docs.openstack.org/developer/nova/support-matrix.html +See https://docs.openstack.org/developer/nova/support-matrix.html for a detailed list of features and support across the hypervisors. The following hypervisors are supported: diff --git a/doc/config-reference/source/compute/resize.rst b/doc/config-reference/source/compute/resize.rst index c4e8ee5198..4cd7fd2a83 100644 --- a/doc/config-reference/source/compute/resize.rst +++ b/doc/config-reference/source/compute/resize.rst @@ -16,7 +16,7 @@ and passwordless ssh access between your compute hosts. Direct access from one compute host to another is needed to copy the VM file across. Cloud end users can find out how to resize a server by reading the -`OpenStack End User Guide `_. XenServer diff --git a/doc/config-reference/source/compute/schedulers.rst b/doc/config-reference/source/compute/schedulers.rst index a7ba242674..dbcd878057 100644 --- a/doc/config-reference/source/compute/schedulers.rst +++ b/doc/config-reference/source/compute/schedulers.rst @@ -49,7 +49,7 @@ how often the list is updated. be dead while the host list is being cached. For information about the volume scheduler, see the `Block Storage section -`_ +`_ of OpenStack Administrator Guide. The scheduler chooses a new host when an instance is migrated. @@ -59,7 +59,7 @@ the target host defined by the administrator on the :command:`nova evacuate` command. If a target is not defined by the administrator, the scheduler determines the target host. For information about instance evacuation, -see `Evacuate instances `_ section of the OpenStack Administrator Guide. diff --git a/doc/config-reference/source/identity.rst b/doc/config-reference/source/identity.rst index 902ee80c0e..0c44530499 100644 --- a/doc/config-reference/source/identity.rst +++ b/doc/config-reference/source/identity.rst @@ -16,8 +16,8 @@ Identity service This chapter details the Identity service configuration options. For installation prerequisites and step-by-step walkthroughs, see the `Newton Installation Tutorials and Guides -`_ for your distribution and -`OpenStack Administrator Guide `_. +`_ for your distribution and +`OpenStack Administrator Guide `_. .. note:: diff --git a/doc/config-reference/source/identity/config-options.rst b/doc/config-reference/source/identity/config-options.rst index 6493c134ef..49888cd08a 100644 --- a/doc/config-reference/source/identity/config-options.rst +++ b/doc/config-reference/source/identity/config-options.rst @@ -42,5 +42,5 @@ installed on an SQL or LDAP back end, and supports domain-specific Identity configuration options, which are stored in domain-specific configuration files. See the `Admin guide Identity Management Chapter -`_ +`_ for more information. diff --git a/doc/config-reference/source/identity/federated-identity.rst b/doc/config-reference/source/identity/federated-identity.rst index 649b1a0039..91b3a2bc4b 100644 --- a/doc/config-reference/source/identity/federated-identity.rst +++ b/doc/config-reference/source/identity/federated-identity.rst @@ -27,7 +27,7 @@ There is currently support for two major federation protocols: To enable federation: -#. Run keystone under Apache. See `Configure the Apache HTTP server `_ +#. Run keystone under Apache. See `Configure the Apache HTTP server `_ for more information. .. note:: @@ -37,7 +37,7 @@ To enable federation: by the community. #. Configure Apache to use a federation capable module. - We recommend Shibboleth, see `the Shibboleth documentation `_ + We recommend Shibboleth, see `the Shibboleth documentation `_ for more information. .. note:: @@ -317,7 +317,7 @@ A rule hierarchy is as follows: * ``condition``: contains information on conditions that allow a rule, can only be set in a remote rule. -For more information on mapping rules, see ``_. +For more information on mapping rules, see ``_. Mapping creation ---------------- diff --git a/doc/config-reference/source/image/api.rst b/doc/config-reference/source/image/api.rst index 7e5ab7ce06..6040a7c977 100644 --- a/doc/config-reference/source/image/api.rst +++ b/doc/config-reference/source/image/api.rst @@ -15,7 +15,7 @@ as v2 of ``glance-api`` can connect directly to the database. To assist you in formulating your deployment strategy for the Image APIs, the Glance team has published a statement concerning the status and development plans of the APIs: `Using public Image API -`_. +`_. Configuration options ~~~~~~~~~~~~~~~~~~~~~ diff --git a/doc/config-reference/source/image/glance-manage.conf.rst b/doc/config-reference/source/image/glance-manage.conf.rst index 1b51d033b6..0da1c69ad8 100644 --- a/doc/config-reference/source/image/glance-manage.conf.rst +++ b/doc/config-reference/source/image/glance-manage.conf.rst @@ -3,7 +3,7 @@ glance-manage.conf ================== Configuration options for the `glance database management tool -`_ +`_ are found in the ``glance-manage.conf`` file. .. note:: diff --git a/doc/config-reference/source/image/glance-scrubber.conf.rst b/doc/config-reference/source/image/glance-scrubber.conf.rst index 2edb9aae62..4e85521195 100644 --- a/doc/config-reference/source/image/glance-scrubber.conf.rst +++ b/doc/config-reference/source/image/glance-scrubber.conf.rst @@ -2,7 +2,7 @@ glance-scrubber.conf ==================== -`glance-scrubber `_ +`glance-scrubber `_ is a utility for the Image service that cleans up images that have been deleted. Its configuration is stored in the ``glance-scrubber.conf`` file. diff --git a/doc/config-reference/source/message/zaqar-storage-drivers.rst b/doc/config-reference/source/message/zaqar-storage-drivers.rst index 653f7a06bf..ed47be517b 100644 --- a/doc/config-reference/source/message/zaqar-storage-drivers.rst +++ b/doc/config-reference/source/message/zaqar-storage-drivers.rst @@ -44,7 +44,7 @@ stages, the sequence in which the option values are listed does matter or not. You can add external stages to the storage layer pipelines. For information how to write and add your own external stages, see `Writing stages for the storage pipelines -`_ +`_ tutorial. Options diff --git a/doc/config-reference/source/networking.rst b/doc/config-reference/source/networking.rst index a37a0ff039..cd11fe4e89 100644 --- a/doc/config-reference/source/networking.rst +++ b/doc/config-reference/source/networking.rst @@ -17,8 +17,8 @@ Networking service This chapter explains the Networking service configuration options. For installation prerequisites, steps, and use cases, see the Installation Tutorials and Guides for your distribution -(`docs.openstack.org `__) and the -`OpenStack Administrator Guide `__. +(`docs.openstack.org `__) and the +`OpenStack Administrator Guide `__. .. note:: diff --git a/doc/config-reference/source/object-storage/about.rst b/doc/config-reference/source/object-storage/about.rst index 61f1c0b3ee..054fff4083 100644 --- a/doc/config-reference/source/object-storage/about.rst +++ b/doc/config-reference/source/object-storage/about.rst @@ -30,4 +30,4 @@ hardware and inexpensive storage. For more information, review the key concepts in the developer documentation at `docs.openstack.org/developer/swift/ -`__. +`__. diff --git a/doc/config-reference/source/object-storage/features.rst b/doc/config-reference/source/object-storage/features.rst index aceaa27f4a..885fc1cdc4 100644 --- a/doc/config-reference/source/object-storage/features.rst +++ b/doc/config-reference/source/object-storage/features.rst @@ -418,7 +418,7 @@ consistent container listings to do so. Instead, a user-defined manifest of the object segments is used. For more information regarding SLO usage and support, please see: `Static Large -Objects `__. +Objects `__. .. include:: ../tables/swift-proxy-server-filter-slo.rst diff --git a/doc/config-reference/source/orchestration.rst b/doc/config-reference/source/orchestration.rst index 12640890e4..ee10ad561f 100644 --- a/doc/config-reference/source/orchestration.rst +++ b/doc/config-reference/source/orchestration.rst @@ -17,7 +17,7 @@ and applications within OpenStack clouds. Its various agents and services are configured in the ``/etc/heat/heat.conf`` file. To install Orchestration, see the `Newton Installation Tutorials and Guides -`_ for your distribution. +`_ for your distribution. .. note:: diff --git a/doc/config-reference/source/shared-file-systems/drivers/hitachi-hnas-driver.rst b/doc/config-reference/source/shared-file-systems/drivers/hitachi-hnas-driver.rst index ad003ea53e..af032a7f94 100644 --- a/doc/config-reference/source/shared-file-systems/drivers/hitachi-hnas-driver.rst +++ b/doc/config-reference/source/shared-file-systems/drivers/hitachi-hnas-driver.rst @@ -58,7 +58,7 @@ Pre-configuration on OpenStack deployment ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ #. Install the OpenStack environment with manila. See the - `OpenStack installation guide `_. + `OpenStack installation guide `_. #. Configure the OpenStack networking so it can reach HNAS Management interface and HNAS EVS Data interface. diff --git a/doc/config-reference/source/telemetry.rst b/doc/config-reference/source/telemetry.rst index b850d77511..275f52c92b 100644 --- a/doc/config-reference/source/telemetry.rst +++ b/doc/config-reference/source/telemetry.rst @@ -17,7 +17,7 @@ various agents and services are configured in the ``/etc/ceilometer/ceilometer.conf`` file. To install Telemetry, see the `Newton Installation Tutorials and Guides -`_ for your distribution. +`_ for your distribution. .. note::