[ha-guide] use https instead of http for docs.o.o

Change-Id: I2b05c905bea122e085ad9dac68f97e5dbbc3307c
This commit is contained in:
KATO Tomoyuki 2017-01-27 18:49:31 +09:00
parent 2c7324511a
commit 1dafbb621f
12 changed files with 19 additions and 19 deletions

View File

@ -3,7 +3,7 @@ name = openstackhaguide
summary = OpenStack High Availability Guide
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

View File

@ -3,7 +3,7 @@ Configuring the compute node
============================
The `Newton Installation Tutorials and Guides
<http://docs.openstack.org/project-install-guide/newton/>`_
<https://docs.openstack.org/project-install-guide/newton/>`_
provide instructions for installing multiple compute nodes.
To make the compute nodes highly available, you must configure the
environment to include multiple instances of the API and other services.

View File

@ -16,7 +16,7 @@ Prerequisites
Before beginning, ensure you have read the
`OpenStack Identity service getting started documentation
<http://docs.openstack.org/admin-guide/common/get-started-identity.html>`_.
<https://docs.openstack.org/admin-guide/common/get-started-identity.html>`_.
Add OpenStack Identity resource to Pacemaker
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

View File

@ -3,7 +3,7 @@ Highly available Telemetry API
==============================
The `Telemetry service
<http://docs.openstack.org/admin-guide/common/get-started-telemetry.html>`_
<https://docs.openstack.org/admin-guide/common/get-started-telemetry.html>`_
provides a data collection service and an alarming service.
Telemetry central agent
@ -22,7 +22,7 @@ It provides an API above several back ends that can be used for building
distributed applications.
Tooz supports
`various drivers <http://docs.openstack.org/developer/tooz/drivers.html>`_
`various drivers <https://docs.openstack.org/developer/tooz/drivers.html>`_
including the following back end solutions:
* `Zookeeper <http://zookeeper.apache.org/>`_:
@ -39,7 +39,7 @@ the Telemetry services.
For information about the required configuration options
to set in the :file:`ceilometer.conf`, see the `coordination section
<http://docs.openstack.org/newton/config-reference/telemetry.html>`_
<https://docs.openstack.org/newton/config-reference/telemetry.html>`_
in the OpenStack Configuration Reference.
.. note::
@ -61,7 +61,7 @@ agent configuration supports using different configuration files. This is for
groups of service instances that are running in parallel.
For enabling this configuration, set a value for the
``partitioning_group_prefix`` option in the
`polling section <http://docs.openstack.org/newton/config-reference/telemetry/telemetry-config-options.html>`_
`polling section <https://docs.openstack.org/newton/config-reference/telemetry/telemetry-config-options.html>`_
in the OpenStack Configuration Reference.
.. warning::
@ -72,10 +72,10 @@ in the OpenStack Configuration Reference.
can be set in the :file:`/etc/ceilometer/pipeline.yaml` configuration file.
For more information about pipelines see the `Data collection and
processing
<http://docs.openstack.org/admin-guide/telemetry-data-collection.html#data-collection-and-processing>`_
<https://docs.openstack.org/admin-guide/telemetry-data-collection.html#data-collection-and-processing>`_
section.
To enable the compute agent to run multiple instances simultaneously with
workload partitioning, the ``workload_partitioning`` option must be set to
``True`` under the `compute section <http://docs.openstack.org/newton/config-reference/telemetry.html>`_
``True`` under the `compute section <https://docs.openstack.org/newton/config-reference/telemetry.html>`_
in the :file:`ceilometer.conf` configuration file.

View File

@ -12,11 +12,11 @@ The following are the standard hardware requirements:
- Provider networks: See the *Overview -> Networking Option 1: Provider
networks* section of the
`Install Tutorials and Guides <http://docs.openstack.org/project-install-guide/newton>`_
`Install Tutorials and Guides <https://docs.openstack.org/project-install-guide/newton>`_
depending on your distribution.
- Self-service networks: See the *Overview -> Networking Option 2:
Self-service networks* section of the
`Install Tutorials and Guides <http://docs.openstack.org/project-install-guide/newton>`_
`Install Tutorials and Guides <https://docs.openstack.org/project-install-guide/newton>`_
depending on your distribution.
OpenStack does not require a significant amount of resources and the following

View File

@ -28,5 +28,5 @@ By default, ``controller1`` handles the caching service. If the host goes down,
For more information about Memcached installation, see the
*Environment -> Memcached* section in the
`Installation Tutorials and Guides <http://docs.openstack.org/project-install-guide/newton>`_
`Installation Tutorials and Guides <https://docs.openstack.org/project-install-guide/newton>`_
depending on your distribution.

View File

@ -7,4 +7,4 @@ We recommend that you configure the controller node to reference
more accurate (lower stratum) servers and other nodes to reference
the controller node. For more information, see the
`Newton Installation Tutorials and Guides
<http://docs.openstack.org/project-install-guide/newton/>`_.
<https://docs.openstack.org/project-install-guide/newton/>`_.

View File

@ -5,7 +5,7 @@ Installing the operating system
The first step in setting up your highly available OpenStack cluster
is to install the operating system on each node.
Follow the instructions in the *Environment* section of the
`Installation Tutorials and Guides <http://docs.openstack.org/project-install-guide/newton>`_
`Installation Tutorials and Guides <https://docs.openstack.org/project-install-guide/newton>`_
depending on your distribution.
The OpenStack Installation Tutorials and Guides also include a list of

View File

@ -11,7 +11,7 @@ Configuring the networking services
Configure networking on each node. See the basic information
about configuring networking in the *Networking service*
section of the
`Install Tutorials and Guides <http://docs.openstack.org/project-install-guide/newton>`_,
`Install Tutorials and Guides <https://docs.openstack.org/project-install-guide/newton>`_,
depending on your distribution.
OpenStack network nodes contain:

View File

@ -29,7 +29,7 @@ Galera Cluster requires that you open the following ports to network traffic:
.. seealso::
For more information on firewalls, see `Firewalls and default ports
<http://docs.openstack.org/newton/config-reference/firewalls-default-ports.html>`_
<https://docs.openstack.org/newton/config-reference/firewalls-default-ports.html>`_
in the Configuration Reference.
This can be achieved using the :command:`iptables` command:

View File

@ -23,7 +23,7 @@ An OpenStack environment includes multiple data pools for the VMs:
For more information about configuring storage back ends for
the different storage options, see `Manage volumes
<http://docs.openstack.org/admin-guide/blockstorage-manage-volumes.html>`_
<https://docs.openstack.org/admin-guide/blockstorage-manage-volumes.html>`_
in the OpenStack Administrator Guide.
This section discusses ways to protect against data loss in your OpenStack
@ -54,6 +54,6 @@ itself.
When Ceph RBD is used for ephemeral volumes as well as block and image storage,
it supports `live migration
<http://docs.openstack.org/admin-guide/compute-live-migration-usage.html>`_
<https://docs.openstack.org/admin-guide/compute-live-migration-usage.html>`_
of VMs with ephemeral drives. LVM only supports live migration of
volume-backed VMs.

View File

@ -16,7 +16,7 @@ Prerequisites
Before beginning, ensure that you are familiar with the
documentation for installing the OpenStack Image API service.
See the *Image service* section in the
`Installation Tutorials and Guides <http://docs.openstack.org/project-install-guide/newton>`_,
`Installation Tutorials and Guides <https://docs.openstack.org/project-install-guide/newton>`_,
depending on your distribution.
.. _glance-api-pacemaker: