[config-ref] use https://docs.o.o/ instead of http
Change-Id: Ic12e83aff2edd494760e75c47d404f67f5996032
This commit is contained in:
parent
2c7324511a
commit
d1fccca921
doc/config-reference
setup.cfg
source
block-storage
drivers
coho-data-driver.rstdell-equallogic-driver.rstemc-vmax-driver.rstemc-vnx-driver.rstkaminario-driver.rstsolidfire-volume-driver.rst
schedulers.rstvolume-encryption.rstcommon-configurations
compute
identity.rstidentity
image
message
networking.rstobject-storage
orchestration.rstshared-file-systems/drivers
telemetry.rst@ -3,7 +3,7 @@ name = configurationreference
|
|||||||
summary = OpenStack Configuration Reference
|
summary = OpenStack Configuration Reference
|
||||||
author = OpenStack
|
author = OpenStack
|
||||||
author-email = openstack-docs@lists.openstack.org
|
author-email = openstack-docs@lists.openstack.org
|
||||||
home-page = http://docs.openstack.org/
|
home-page = https://docs.openstack.org/
|
||||||
classifier =
|
classifier =
|
||||||
Environment :: OpenStack
|
Environment :: OpenStack
|
||||||
Intended Audience :: Information Technology
|
Intended Audience :: Information Technology
|
||||||
|
@ -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.
|
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
|
For information about how to set the key-value pairs and associate
|
||||||
them with a volume type, see the `volume qos
|
them with a volume type, see the `volume qos
|
||||||
<http://docs.openstack.org/developer/python-openstackclient/command-objects/volume-qos.html>`_
|
<https://docs.openstack.org/developer/python-openstackclient/command-objects/volume-qos.html>`_
|
||||||
section in the OpenStackClient command list.
|
section in the OpenStackClient command list.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
@ -157,4 +157,4 @@ In this example:
|
|||||||
|
|
||||||
For information on configuring multiple back ends, see `Configure a
|
For information on configuring multiple back ends, see `Configure a
|
||||||
multiple-storage back
|
multiple-storage back
|
||||||
end <http://docs.openstack.org/admin-guide/blockstorage-multi-backend.html>`__.
|
end <https://docs.openstack.org/admin-guide/blockstorage-multi-backend.html>`__.
|
||||||
|
@ -1135,7 +1135,7 @@ these snapshots. The functionality to backup snapshots provides another layer
|
|||||||
of data protection.
|
of data protection.
|
||||||
|
|
||||||
Please refer to `backup and restore volumes and
|
Please refer to `backup and restore volumes and
|
||||||
snapshots <http://docs.openstack.org/admin-guide/blockstorage-volume-backups.html>`
|
snapshots <https://docs.openstack.org/admin-guide/blockstorage-volume-backups.html>`
|
||||||
for more more information.
|
for more more information.
|
||||||
|
|
||||||
Enable attach and detach snapshot functionality
|
Enable attach and detach snapshot functionality
|
||||||
|
@ -179,7 +179,7 @@ The value of the option ``storage_protocol`` can be either ``fc`` or ``iscsi``,
|
|||||||
which is case insensitive.
|
which is case insensitive.
|
||||||
|
|
||||||
For more details on multiple back ends, see `Configure multiple-storage
|
For more details on multiple back ends, see `Configure multiple-storage
|
||||||
back ends <http://docs.openstack.org/admin-guide/blockstorage-multi-backend.html>`_
|
back ends <https://docs.openstack.org/admin-guide/blockstorage-multi-backend.html>`_
|
||||||
|
|
||||||
Required configurations
|
Required configurations
|
||||||
-----------------------
|
-----------------------
|
||||||
|
@ -100,8 +100,8 @@ Cinder Driver for single FC or iSCSI backend.
|
|||||||
scheduler_default_filters = DriverFilter,CapabilitiesFilter
|
scheduler_default_filters = DriverFilter,CapabilitiesFilter
|
||||||
|
|
||||||
See following links for more information:
|
See following links for more information:
|
||||||
`<http://docs.openstack.org/developer/cinder/scheduler-filters.html>`_
|
`<https://docs.openstack.org/developer/cinder/scheduler-filters.html>`_
|
||||||
`<http://docs.openstack.org/admin-guide/blockstorage-driver-filter-weighing.html>`_
|
`<https://docs.openstack.org/admin-guide/blockstorage-driver-filter-weighing.html>`_
|
||||||
|
|
||||||
#. Under the ``[DEFAULT]`` section, set the enabled_backends parameter
|
#. Under the ``[DEFAULT]`` section, set the enabled_backends parameter
|
||||||
with the iSCSI or FC back-end group
|
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``
|
``Configure single Kaminario iSCSI/FC back end``
|
||||||
|
|
||||||
See `Configure multiple-storage back ends
|
See `Configure multiple-storage back ends
|
||||||
<http://docs.openstack.org/admin-guide/blockstorage-multi-backend.html>`__
|
<https://docs.openstack.org/admin-guide/blockstorage-multi-backend.html>`__
|
||||||
for additional information.
|
for additional information.
|
||||||
|
|
||||||
#. Restart the cinder volume service for the changes to take effect.
|
#. Restart the cinder volume service for the changes to take effect.
|
||||||
|
@ -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
|
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
|
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
|
pairs and associate them with a volume type, see the `volume qos
|
||||||
<http://docs.openstack.org/developer/python-openstackclient/command-objects/volume-qos.html>`_
|
<https://docs.openstack.org/developer/python-openstackclient/command-objects/volume-qos.html>`_
|
||||||
section in the OpenStackClient command list.
|
section in the OpenStackClient command list.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
@ -6,6 +6,6 @@ Block Storage service uses the ``cinder-scheduler`` service
|
|||||||
to determine how to dispatch block storage requests.
|
to determine how to dispatch block storage requests.
|
||||||
|
|
||||||
For more information, see `Cinder Scheduler Filters
|
For more information, see `Cinder Scheduler Filters
|
||||||
<http://docs.openstack.org/developer/cinder/scheduler-filters.html>`_
|
<https://docs.openstack.org/developer/cinder/scheduler-filters.html>`_
|
||||||
and `Cinder Scheduler Weights
|
and `Cinder Scheduler Weights
|
||||||
<http://docs.openstack.org/developer/cinder/scheduler-weights.html>`_.
|
<https://docs.openstack.org/developer/cinder/scheduler-weights.html>`_.
|
||||||
|
@ -88,7 +88,7 @@ the volume.
|
|||||||
The OpenStack dashboard (horizon) supports creating the encrypted
|
The OpenStack dashboard (horizon) supports creating the encrypted
|
||||||
volume type as of the Kilo release. For instructions, see
|
volume type as of the Kilo release. For instructions, see
|
||||||
`Create an encrypted volume type
|
`Create an encrypted volume type
|
||||||
<http://docs.openstack.org/admin-guide/dashboard-manage-volumes.html>`_.
|
<https://docs.openstack.org/admin-guide/dashboard-manage-volumes.html>`_.
|
||||||
|
|
||||||
Create an encrypted volume
|
Create an encrypted volume
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
@ -15,4 +15,4 @@ These options are supported by:
|
|||||||
|
|
||||||
For a complete list of all available cache configuration options,
|
For a complete list of all available cache configuration options,
|
||||||
see `olso.cache configuration options
|
see `olso.cache configuration options
|
||||||
<http://docs.openstack.org/developer/oslo.cache/opts.html>`_.
|
<https://docs.openstack.org/developer/oslo.cache/opts.html>`_.
|
||||||
|
@ -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.
|
one it was originated from. OpenStack services support CORS requests.
|
||||||
|
|
||||||
For more information, see `cross-project features
|
For more information, see `cross-project features
|
||||||
<http://docs.openstack.org/admin-guide/cross-project.html>`_
|
<https://docs.openstack.org/admin-guide/cross-project.html>`_
|
||||||
in OpenStack Administrator Guide, `CORS in Dashboard
|
in OpenStack Administrator Guide, `CORS in Dashboard
|
||||||
<http://docs.openstack.org/security-guide/dashboard/cross-origin-resource-sharing-cors.html>`_,
|
<https://docs.openstack.org/security-guide/dashboard/cross-origin-resource-sharing-cors.html>`_,
|
||||||
and `CORS in Object Storage service
|
and `CORS in Object Storage service
|
||||||
<http://docs.openstack.org/developer/swift/cors.html>`_.
|
<https://docs.openstack.org/developer/swift/cors.html>`_.
|
||||||
|
|
||||||
For a complete list of all available CORS configuration options,
|
For a complete list of all available CORS configuration options,
|
||||||
see `CORS configuration options
|
see `CORS configuration options
|
||||||
<http://docs.openstack.org/developer/oslo.middleware/cors.html#configuration-options>`_.
|
<https://docs.openstack.org/developer/oslo.middleware/cors.html#configuration-options>`_.
|
||||||
|
@ -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.
|
#. **Image formats**: Xen supports raw, qcow2 and vhd image formats.
|
||||||
For more information on image formats, refer to the `OpenStack Virtual
|
For more information on image formats, refer to the `OpenStack Virtual
|
||||||
Image Guide <http://docs.openstack.org/image-guide/introduction.html>`__
|
Image Guide <https://docs.openstack.org/image-guide/introduction.html>`__
|
||||||
and the `Storage Options Guide on the Xen Project Wiki
|
and the `Storage Options Guide on the Xen Project Wiki
|
||||||
<http://wiki.xenproject.org/wiki/Storage_options>`_.
|
<http://wiki.xenproject.org/wiki/Storage_options>`_.
|
||||||
|
|
||||||
@ -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
|
For more more information on image metadata, refer to the
|
||||||
`OpenStack Virtual Image Guide
|
`OpenStack Virtual Image Guide
|
||||||
<http://docs.openstack.org/image-guide/image-metadata.html>`__.
|
<https://docs.openstack.org/image-guide/image-metadata.html>`__.
|
||||||
|
|
||||||
#. **Libguestfs file injection**: OpenStack compute nodes can use `libguestfs
|
#. **Libguestfs file injection**: OpenStack compute nodes can use `libguestfs
|
||||||
<http://libguestfs.org/>`_ to inject files into an instance's image prior
|
<http://libguestfs.org/>`_ to inject files into an instance's image prior
|
||||||
|
@ -20,7 +20,7 @@ for you to choose one. Most installations use only one hypervisor.
|
|||||||
However, you can use :ref:`ComputeFilter` and :ref:`ImagePropertiesFilter`
|
However, you can use :ref:`ComputeFilter` and :ref:`ImagePropertiesFilter`
|
||||||
to schedule different hypervisors within the same installation.
|
to schedule different hypervisors within the same installation.
|
||||||
The following links help you choose a hypervisor.
|
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.
|
for a detailed list of features and support across the hypervisors.
|
||||||
|
|
||||||
The following hypervisors are supported:
|
The following hypervisors are supported:
|
||||||
|
@ -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.
|
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
|
Cloud end users can find out how to resize a server by reading the
|
||||||
`OpenStack End User Guide <http://docs.openstack.org/user-guide/
|
`OpenStack End User Guide <https://docs.openstack.org/user-guide/
|
||||||
cli_change_the_size_of_your_server.html>`_.
|
cli_change_the_size_of_your_server.html>`_.
|
||||||
|
|
||||||
XenServer
|
XenServer
|
||||||
|
@ -49,7 +49,7 @@ how often the list is updated.
|
|||||||
be dead while the host list is being cached.
|
be dead while the host list is being cached.
|
||||||
|
|
||||||
For information about the volume scheduler, see the `Block Storage section
|
For information about the volume scheduler, see the `Block Storage section
|
||||||
<http://docs.openstack.org/admin-guide/blockstorage-manage-volumes.html>`_
|
<https://docs.openstack.org/admin-guide/blockstorage-manage-volumes.html>`_
|
||||||
of OpenStack Administrator Guide.
|
of OpenStack Administrator Guide.
|
||||||
|
|
||||||
The scheduler chooses a new host when an instance is migrated.
|
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.
|
:command:`nova evacuate` command.
|
||||||
If a target is not defined by the administrator, the scheduler
|
If a target is not defined by the administrator, the scheduler
|
||||||
determines the target host. For information about instance evacuation,
|
determines the target host. For information about instance evacuation,
|
||||||
see `Evacuate instances <http://docs.openstack.org/admin-guide/
|
see `Evacuate instances <https://docs.openstack.org/admin-guide/
|
||||||
compute-node-down.html#evacuate-instances>`_ section of the
|
compute-node-down.html#evacuate-instances>`_ section of the
|
||||||
OpenStack Administrator Guide.
|
OpenStack Administrator Guide.
|
||||||
|
|
||||||
|
@ -16,8 +16,8 @@ Identity service
|
|||||||
This chapter details the Identity service configuration options. For
|
This chapter details the Identity service configuration options. For
|
||||||
installation prerequisites and step-by-step walkthroughs, see the
|
installation prerequisites and step-by-step walkthroughs, see the
|
||||||
`Newton Installation Tutorials and Guides
|
`Newton Installation Tutorials and Guides
|
||||||
<http://docs.openstack.org/project-install-guide/newton/>`_ for your distribution and
|
<https://docs.openstack.org/project-install-guide/newton/>`_ for your distribution and
|
||||||
`OpenStack Administrator Guide <http://docs.openstack.org/admin-guide/>`_.
|
`OpenStack Administrator Guide <https://docs.openstack.org/admin-guide/>`_.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
|
@ -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
|
Identity configuration options, which are stored in domain-specific
|
||||||
configuration files. See the
|
configuration files. See the
|
||||||
`Admin guide Identity Management Chapter
|
`Admin guide Identity Management Chapter
|
||||||
<http://docs.openstack.org/admin-guide/identity-domain-specific-config.html>`_
|
<https://docs.openstack.org/admin-guide/identity-domain-specific-config.html>`_
|
||||||
for more information.
|
for more information.
|
||||||
|
@ -27,7 +27,7 @@ There is currently support for two major federation protocols:
|
|||||||
|
|
||||||
To enable federation:
|
To enable federation:
|
||||||
|
|
||||||
#. Run keystone under Apache. See `Configure the Apache HTTP server <http://docs.openstack.org/newton/install-guide-obs/keystone-install.html>`_
|
#. Run keystone under Apache. See `Configure the Apache HTTP server <https://docs.openstack.org/newton/install-guide-obs/keystone-install.html>`_
|
||||||
for more information.
|
for more information.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
@ -37,7 +37,7 @@ To enable federation:
|
|||||||
by the community.
|
by the community.
|
||||||
|
|
||||||
#. Configure Apache to use a federation capable module.
|
#. Configure Apache to use a federation capable module.
|
||||||
We recommend Shibboleth, see `the Shibboleth documentation <http://docs.openstack.org/developer/keystone/federation/shibboleth.html>`_
|
We recommend Shibboleth, see `the Shibboleth documentation <https://docs.openstack.org/developer/keystone/federation/shibboleth.html>`_
|
||||||
for more information.
|
for more information.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
@ -317,7 +317,7 @@ A rule hierarchy is as follows:
|
|||||||
* ``condition``: contains information on conditions that allow a rule, can
|
* ``condition``: contains information on conditions that allow a rule, can
|
||||||
only be set in a remote rule.
|
only be set in a remote rule.
|
||||||
|
|
||||||
For more information on mapping rules, see `<http://docs.openstack.org/developer/keystone/federation/federated_identity.html#mapping-rules>`_.
|
For more information on mapping rules, see `<https://docs.openstack.org/developer/keystone/federation/federated_identity.html#mapping-rules>`_.
|
||||||
|
|
||||||
Mapping creation
|
Mapping creation
|
||||||
----------------
|
----------------
|
||||||
|
@ -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,
|
To assist you in formulating your deployment strategy for the Image APIs,
|
||||||
the Glance team has published a statement concerning the status and
|
the Glance team has published a statement concerning the status and
|
||||||
development plans of the APIs: `Using public Image API
|
development plans of the APIs: `Using public Image API
|
||||||
<http://docs.openstack.org/developer/glance/glanceapi.html>`_.
|
<https://docs.openstack.org/developer/glance/glanceapi.html>`_.
|
||||||
|
|
||||||
Configuration options
|
Configuration options
|
||||||
~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
@ -3,7 +3,7 @@ glance-manage.conf
|
|||||||
==================
|
==================
|
||||||
|
|
||||||
Configuration options for the `glance database management tool
|
Configuration options for the `glance database management tool
|
||||||
<http://docs.openstack.org/developer/glance/man/glancemanage.html>`_
|
<https://docs.openstack.org/developer/glance/man/glancemanage.html>`_
|
||||||
are found in the ``glance-manage.conf`` file.
|
are found in the ``glance-manage.conf`` file.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
@ -2,7 +2,7 @@
|
|||||||
glance-scrubber.conf
|
glance-scrubber.conf
|
||||||
====================
|
====================
|
||||||
|
|
||||||
`glance-scrubber <http://docs.openstack.org/developer/glance/man/glancescrubber.html>`_
|
`glance-scrubber <https://docs.openstack.org/developer/glance/man/glancescrubber.html>`_
|
||||||
is a utility for the Image service that cleans up images that have been
|
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.
|
deleted. Its configuration is stored in the ``glance-scrubber.conf`` file.
|
||||||
|
|
||||||
|
@ -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
|
You can add external stages to the storage layer pipelines. For information how
|
||||||
to write and add your own external stages, see
|
to write and add your own external stages, see
|
||||||
`Writing stages for the storage pipelines
|
`Writing stages for the storage pipelines
|
||||||
<http://docs.openstack.org/developer/zaqar/writing_pipeline_stages.html>`_
|
<https://docs.openstack.org/developer/zaqar/writing_pipeline_stages.html>`_
|
||||||
tutorial.
|
tutorial.
|
||||||
|
|
||||||
Options
|
Options
|
||||||
|
@ -17,8 +17,8 @@ Networking service
|
|||||||
This chapter explains the Networking service configuration options.
|
This chapter explains the Networking service configuration options.
|
||||||
For installation prerequisites, steps, and use cases, see the
|
For installation prerequisites, steps, and use cases, see the
|
||||||
Installation Tutorials and Guides for your distribution
|
Installation Tutorials and Guides for your distribution
|
||||||
(`docs.openstack.org <http://docs.openstack.org>`__) and the
|
(`docs.openstack.org <https://docs.openstack.org>`__) and the
|
||||||
`OpenStack Administrator Guide <http://docs.openstack.org/admin-guide/>`__.
|
`OpenStack Administrator Guide <https://docs.openstack.org/admin-guide/>`__.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
|
@ -30,4 +30,4 @@ hardware and inexpensive storage.
|
|||||||
|
|
||||||
For more information, review the key concepts in the developer documentation
|
For more information, review the key concepts in the developer documentation
|
||||||
at `docs.openstack.org/developer/swift/
|
at `docs.openstack.org/developer/swift/
|
||||||
<http://docs.openstack.org/developer/swift/>`__.
|
<https://docs.openstack.org/developer/swift/>`__.
|
||||||
|
@ -418,7 +418,7 @@ consistent container listings to do so. Instead, a user-defined manifest of
|
|||||||
the object segments is used.
|
the object segments is used.
|
||||||
|
|
||||||
For more information regarding SLO usage and support, please see: `Static Large
|
For more information regarding SLO usage and support, please see: `Static Large
|
||||||
Objects <http://docs.openstack.org/developer/swift/middleware.html#slo-doc>`__.
|
Objects <https://docs.openstack.org/developer/swift/middleware.html#slo-doc>`__.
|
||||||
|
|
||||||
.. include:: ../tables/swift-proxy-server-filter-slo.rst
|
.. include:: ../tables/swift-proxy-server-filter-slo.rst
|
||||||
|
|
||||||
|
@ -17,7 +17,7 @@ and applications within OpenStack clouds. Its various agents and services are
|
|||||||
configured in the ``/etc/heat/heat.conf`` file.
|
configured in the ``/etc/heat/heat.conf`` file.
|
||||||
|
|
||||||
To install Orchestration, see the `Newton Installation Tutorials and Guides
|
To install Orchestration, see the `Newton Installation Tutorials and Guides
|
||||||
<http://docs.openstack.org/project-install-guide/newton/>`_ for your distribution.
|
<https://docs.openstack.org/project-install-guide/newton/>`_ for your distribution.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
|
@ -58,7 +58,7 @@ Pre-configuration on OpenStack deployment
|
|||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
#. Install the OpenStack environment with manila. See the
|
#. Install the OpenStack environment with manila. See the
|
||||||
`OpenStack installation guide <http://docs.openstack.org/>`_.
|
`OpenStack installation guide <https://docs.openstack.org/>`_.
|
||||||
|
|
||||||
#. Configure the OpenStack networking so it can reach HNAS Management
|
#. Configure the OpenStack networking so it can reach HNAS Management
|
||||||
interface and HNAS EVS Data interface.
|
interface and HNAS EVS Data interface.
|
||||||
|
@ -17,7 +17,7 @@ various agents and services are configured in the
|
|||||||
``/etc/ceilometer/ceilometer.conf`` file.
|
``/etc/ceilometer/ceilometer.conf`` file.
|
||||||
|
|
||||||
To install Telemetry, see the `Newton Installation Tutorials and Guides
|
To install Telemetry, see the `Newton Installation Tutorials and Guides
|
||||||
<http://docs.openstack.org/project-install-guide/newton/>`_ for your distribution.
|
<https://docs.openstack.org/project-install-guide/newton/>`_ for your distribution.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user