openstack/openstack-manuals
Code Issues Proposed changes

Merge "[operation-guide]Correct the wrong title name"

Browse Source
This commit is contained in:
Jenkins 2016-05-24 06:15:42 +00:00 committed by Gerrit Code Review
commit b115401895
6 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/arch-design-draft/source/arch-guide-draft-mitaka/operator-requirements-upgrades.rst
View File

@ -16,7 +16,7 @@ shared centralized services such as OpenStack Identity. At a high level
the recommended order of operations to upgrade an individual OpenStack
environment is (see the `Upgrades
chapter <http://docs.openstack.org/openstack-ops/content/ops_upgrades-general-steps.html>`_
of the Operations Guide for details):
of the OpenStack Operations Guide for details):
#. Upgrade the OpenStack Identity service (keystone).

6
doc/arch-design/source/multi-site-operational-considerations.rst
View File

@ -49,8 +49,8 @@ Logging and monitoring
Logging and monitoring does not significantly differ for a multi-site
OpenStack cloud. The tools described in the `Logging and monitoring
chapter <http://docs.openstack.org/openstack-ops/content/logging_monitoring.html>`__
of the Operations Guide remain applicable. Logging and monitoring can be
provided on a per-site basis, and in a common centralized location.
of the OpenStack Operations Guide remain applicable. Logging and monitoring
can be provided on a per-site basis, and in a common centralized location.
When attempting to deploy logging and monitoring facilities to a
centralized location, care must be taken with the load placed on the
@ -65,7 +65,7 @@ shared centralized services such as OpenStack Identity. At a high level
the recommended order of operations to upgrade an individual OpenStack
environment is (see the `Upgrades
chapter <http://docs.openstack.org/openstack-ops/content/ops_upgrades-general-steps.html>`__
of the Operations Guide for details):
of the OpenStack Operations Guide for details):
#. Upgrade the OpenStack Identity service (keystone).

2
doc/contributor-guide/source/docs-builds.rst
View File

@ -84,7 +84,7 @@ Guides for deployers and administrators
- http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/networking-guide
- http://docs.openstack.org/mitaka/networking-guide
* - Operations Guide
* - OpenStack Operations Guide
- http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/ops-guide
- http://docs.openstack.org/ops-guide

2
doc/contributor-guide/source/topic-tags.rst
View File

@ -45,7 +45,7 @@ Based on the topic your request refers to, use the following tags:
Networking Guide
[ops-guide]
Operations Guide
OpenStack Operations Guide
[sec-guide]
Security Guide

2
doc/install-guide/source/keystone-users.rst
View File

@ -92,7 +92,7 @@ service. The authentication service uses a combination of :term:`domains
``policy.json`` file in the configuration file directory of each
OpenStack service. The default policy for most services grants
administrative access to the ``admin`` role. For more information,
see the `Operations Guide - Managing Projects and
see the `OpenStack Operations Guide - Managing Projects and
Users <http://docs.openstack.org/openstack-ops/content/projects_users.html>`__.
#. This guide uses a service project that contains a unique user for each

2
doc/install-guide/source/overview.rst
View File

@ -123,7 +123,7 @@ follows:
For more information on production architectures, see the
`Architecture Design Guide <http://docs.openstack.org/arch-design/>`__,
`Operations Guide <http://docs.openstack.org/ops/>`__, and
`OpenStack Operations Guide <http://docs.openstack.org/ops/>`__, and
`Networking Guide <http://docs.openstack.org/mitaka/networking-guide/>`__.
.. _figure-hwreqs: