openstack/openstack-manuals
Code Issues Proposed changes

Update "http" to "https" for safer

Browse Source 
Change-Id: Ibe36dc8c21d1779e735225286a7c8852019ad2c9
This commit is contained in:
caoyuan 2017-06-10 03:53:58 +08:00
parent ea55880fc0
commit 08267552f3
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/ha-guide/source/compute-node-ha.rst
View File

@ -19,7 +19,7 @@ the compute node, or other failures that could prevent instances from
functioning correctly, such as, issues with a cinder volume I/O path.
More details are available in the `user story
<http://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/ha_vm.html>`_
<https://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/ha_vm.html>`_
co-authored by OpenStack's HA community and `Product Working Group
<https://wiki.openstack.org/wiki/ProductTeam>`_ (PWG), where this feature is
identified as missing functionality in OpenStack, which
@ -40,7 +40,7 @@ links:
<https://github.com/gryf/mistral-evacuate>`_, by Intel
* `masakari <https://launchpad.net/masakari>`_, by NTT
* `OCF RAs
<http://aspiers.github.io/openstack-summit-2016-austin-compute-ha/#/ocf-pros-cons>`_,
<https://aspiers.github.io/openstack-summit-2016-austin-compute-ha/#/ocf-pros-cons>`_,
as used by Red Hat and SUSE
Current upstream work

2
doc/ha-guide/source/controller-ha-pacemaker.rst
View File

@ -11,7 +11,7 @@ Pacemaker is used to make OpenStack infrastructure highly available.
It is storage and application-agnostic, and in no way specific to OpenStack.
Pacemaker relies on the
`Corosync <http://corosync.github.io/corosync/>`_ messaging layer
`Corosync <https://corosync.github.io/corosync/>`_ messaging layer
for reliable cluster communications. Corosync implements the Totem single-ring
ordering and membership protocol. It also provides UDP and InfiniBand based
messaging, quorum, and cluster membership to Pacemaker.

6
doc/ha-guide/source/controller-ha-telemetry.rst
View File

@ -25,13 +25,13 @@ Tooz supports
`various drivers <https://docs.openstack.org/developer/tooz/drivers.html>`_
including the following back end solutions:
* `Zookeeper <http://zookeeper.apache.org/>`_:
* `Zookeeper <https://zookeeper.apache.org/>`_:
Recommended solution by the Tooz project.
* `Redis <http://redis.io/>`_:
* `Redis <https://redis.io/>`_:
Recommended solution by the Tooz project.
* `Memcached <http://memcached.org/>`_:
* `Memcached <https://memcached.org/>`_:
Recommended for testing.
You must configure a supported Tooz driver for the HA deployment of