[ops-guide] Changed underscore to hyphen in RST files
This patch: - renames all the RST files in the ops-guide folder to use a hyphen instead of underscore; - adds redirects to the renamed files to .htacces; - removes /([a-z-]+) from Admin Guide redirects in .htacces. Change-Id: I4c35a4c89ae9900a2e9bfe1a7a3bcb94ab72454b Implements: blueprint consistency-file-rename
This commit is contained in:
Olena Logvinova
parent
8755545ce3
commit
788b49f554
@ -28,5 +28,5 @@ Amazon EC2 Elastic Block Storage (EBS) offering.
|
||||
blockstorage-manage-volumes.rst
|
||||
blockstorage-troubleshoot.rst
|
||||
|
||||
.. _`Storage Decisions`: http://docs.openstack.org/ops-guide/arch_storage.html
|
||||
.. _`Storage Decisions`: http://docs.openstack.org/ops-guide/arch-storage.html
|
||||
.. _`OpenStack Operations Guide`: http://docs.openstack.org/ops-guide/
|
||||
|
||||
@ -122,7 +122,7 @@ Create a flavor
|
||||
flavor that you do not want other tenants to have access to,
|
||||
you can change the flavor's access to make it a private flavor.
|
||||
See
|
||||
`Private Flavors in the OpenStack Operations Guide <http://docs.openstack.org/ops-guide/ops_user_facing_operations.html#private-flavors>`_.
|
||||
`Private Flavors in the OpenStack Operations Guide <http://docs.openstack.org/ops-guide/ops-user-facing-operations.html#private-flavors>`_.
|
||||
|
||||
For a list of optional parameters, run this command:
|
||||
|
||||
|
||||
@ -135,7 +135,7 @@ compute node runs its own ``nova-network`` service. In both cases, all
|
||||
traffic between VMs and the internet flows through ``nova-network``. Each
|
||||
mode has benefits and drawbacks. For more on this, see the Network
|
||||
Topology section in the `OpenStack Operations Guide
|
||||
<http://docs.openstack.org/ops-guide/arch_network_design.html#network-topology>`__.
|
||||
<http://docs.openstack.org/ops-guide/arch-network-design.html#network-topology>`__.
|
||||
|
||||
All networking options require network connectivity to be already set up
|
||||
between OpenStack physical nodes. OpenStack does not configure any
|
||||
|
||||
@ -79,7 +79,7 @@ extensible OpenStack Networking (neutron). OpenStack Networking and legacy
|
||||
networking both have their advantages and disadvantages. They are both valid
|
||||
and supported options that fit different network deployment models described in
|
||||
the `OpenStack Operations Guide
|
||||
<http://docs.openstack.org/ops-guide/arch_network_design.html#network-topology>`_.
|
||||
<http://docs.openstack.org/ops-guide/arch-network-design.html#network-topology>`_.
|
||||
|
||||
When using the Networking service, the OpenStack controller servers or separate
|
||||
Networking hosts handle routing unless the dynamic virtual routers pattern for
|
||||
|
||||
@ -20,5 +20,5 @@ launch more than 25 instances in any single region.
|
||||
|
||||
For more information on managing quotas refer to the `Managing projects
|
||||
and users
|
||||
chapter <http://docs.openstack.org/ops-guide/ops_projects_users.html>`__
|
||||
chapter <http://docs.openstack.org/ops-guide/ops-projects-users.html>`__
|
||||
of the OpenStack Operators Guide.
|
||||
|
||||
@ -15,7 +15,7 @@ independent OpenStack installations which are linked together using
|
||||
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/ops-guide/ops_upgrades.html>`_
|
||||
chapter <http://docs.openstack.org/ops-guide/ops-upgrades.html>`_
|
||||
of the OpenStack Operations Guide for details):
|
||||
|
||||
#. Upgrade the OpenStack Identity service (keystone).
|
||||
|
||||
@ -18,7 +18,7 @@ Specific meters that are critically important to capture include:
|
||||
|
||||
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/ops-guide/ops_logging_monitoring.html>`__ of
|
||||
<http://docs.openstack.org/ops-guide/ops-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.
|
||||
|
||||
|
||||
@ -68,9 +68,9 @@ The starting point is the core count of your cloud. By applying
|
||||
some ratios, you can gather information about:
|
||||
|
||||
- The number of virtual machines (VMs) you expect to run,
|
||||
``((overcommit fraction × cores) / virtual cores per instance)``
|
||||
``((overcommit fraction × cores) / virtual cores per instance)``
|
||||
|
||||
- How much storage is required ``(flavor disk size × number of instances)``
|
||||
- How much storage is required ``(flavor disk size × number of instances)``
|
||||
|
||||
You can use these ratios to determine how much additional infrastructure
|
||||
you need to support your cloud.
|
||||
@ -118,7 +118,7 @@ refreshes the list of VMs every 30 seconds.
|
||||
|
||||
After you consider these factors, you can determine how many cloud
|
||||
controller cores you require. A typical eight core, 8 GB of RAM server
|
||||
is sufficient for up to a rack of compute nodes — given the above
|
||||
is sufficient for up to a rack of compute nodes — given the above
|
||||
caveats.
|
||||
|
||||
You must also consider key hardware specifications for the performance
|
||||
@ -131,7 +131,7 @@ CPU performance (CPU/core).
|
||||
|
||||
For a discussion of metric tracking, including how to extract
|
||||
metrics from your cloud, see the .`OpenStack Operations Guide
|
||||
<http://docs.openstack.org/ops-guide/ops_logging_monitoring.html>`_.
|
||||
<http://docs.openstack.org/ops-guide/ops-logging-monitoring.html>`_.
|
||||
|
||||
Adding Cloud Controller Nodes
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
@ -417,7 +417,7 @@ nodes, a :term:`weight` should be specified that reflects the
|
||||
|
||||
Monitoring the resource usage and user growth will enable you to know
|
||||
when to procure. The `Logging and Monitoring
|
||||
<http://docs.openstack.org/ops-guide/ops_logging_monitoring.html>`_
|
||||
<http://docs.openstack.org/ops-guide/ops-logging-monitoring.html>`_
|
||||
chapte in the Operations Guide details some useful metrics.
|
||||
|
||||
Burn-in Testing
|
||||
|
||||
@ -75,7 +75,7 @@ community experience.
|
||||
|
||||
For example, KVM is the most widely adopted hypervisor in the OpenStack
|
||||
community. Besides KVM, more deployments run Xen, LXC, VMware, and
|
||||
Hyper-V than the others listed. However, each of these are lacking some
|
||||
Hyper-V than the others listed. However, each of these are lacking some
|
||||
feature support or the documentation on how to use them with OpenStack
|
||||
is out of date.
|
||||
|
||||
@ -285,7 +285,7 @@ Logging
|
||||
~~~~~~~
|
||||
|
||||
Logging is described in more detail in `Logging and Monitoring
|
||||
<http://docs.openstack.org/ops-guide/ops_logging_monitoring.html>`_. However,
|
||||
<http://docs.openstack.org/ops-guide/ops-logging-monitoring.html>`_. However,
|
||||
it is an important design consideration to take into account before
|
||||
commencing operations of your cloud.
|
||||
|
||||
|
||||
@ -372,7 +372,7 @@ OpenStack Identity provides authentication decisions and user attribute
|
||||
information, which is then used by the other OpenStack services to
|
||||
perform authorization. The policy is set in the ``policy.json`` file.
|
||||
For information on how to configure these, see `Managing Projects and Users
|
||||
<http://docs.openstack.org/ops-guide/ops_projects_users.html>`_ in the
|
||||
<http://docs.openstack.org/ops-guide/ops-projects-users.html>`_ in the
|
||||
OpenStack Operations Guide.
|
||||
|
||||
OpenStack Identity supports different plug-ins for authentication
|
||||
|
||||
@ -38,10 +38,10 @@ equation of:
|
||||
|
||||
* 1600 = (16 × (number of physical cores)) / 2
|
||||
|
||||
* Storage required = 50 GB × 1600
|
||||
* Storage required = 50 GB × 1600
|
||||
|
||||
On the surface, the equations reveal the need for 200 physical cores and
|
||||
80 TB of storage for ``/var/lib/nova/instances/``. However, it is also
|
||||
80 TB of storage for ``/var/lib/nova/instances/``. However, it is also
|
||||
important to look at patterns of usage to estimate the load that the API
|
||||
services, database servers, and queue servers are likely to encounter.
|
||||
|
||||
@ -167,7 +167,7 @@ configuration, particularly where they present different ratios of CPU
|
||||
versus RAM versus HDD requirements.
|
||||
|
||||
For more information on Flavors see `OpenStack Operations Guide:
|
||||
Flavors <http://docs.openstack.org/ops-guide/ops_user_facing_operations.html#flavors>`_.
|
||||
Flavors <http://docs.openstack.org/ops-guide/ops-user-facing-operations.html#flavors>`_.
|
||||
|
||||
OpenStack components
|
||||
~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
@ -522,7 +522,7 @@ case, the switching infrastructure must support L3 routing.
|
||||
OpenStack Networking and legacy networking both have their advantages
|
||||
and disadvantages. They are both valid and supported options that fit
|
||||
different network deployment models described in the
|
||||
`Networking deployment options table <http://docs.openstack.org/ops-guide/arch_network_design.html#network-topology>`
|
||||
`Networking deployment options table <http://docs.openstack.org/ops-guide/arch-network-design.html#network-topology>`
|
||||
of OpenStack Operations Guide.
|
||||
|
||||
Ensure your deployment has adequate back-up capabilities.
|
||||
|
||||
@ -48,7 +48,7 @@ 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/ops-guide/ops_logging_monitoring.html>`__
|
||||
chapter <http://docs.openstack.org/ops-guide/ops-logging-monitoring.html>`__
|
||||
of the OpenStack Operations Guide remain applicable. Logging and monitoring
|
||||
can be provided on a per-site basis, and in a common centralized location.
|
||||
|
||||
@ -64,7 +64,7 @@ independent OpenStack installations which are linked together using
|
||||
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/ops-guide/ops_upgrades.html>`__
|
||||
chapter <http://docs.openstack.org/ops-guide/ops-upgrades.html>`__
|
||||
of the OpenStack Operations Guide for details):
|
||||
|
||||
#. Upgrade the OpenStack Identity service (keystone).
|
||||
@ -119,7 +119,7 @@ launch more than 25 instances in any single region.
|
||||
|
||||
For more information on managing quotas refer to the `Managing projects
|
||||
and users
|
||||
chapter <http://docs.openstack.org/ops-guide/ops_projects_users.html>`__
|
||||
chapter <http://docs.openstack.org/ops-guide/ops-projects-users.html>`__
|
||||
of the OpenStack Operators Guide.
|
||||
|
||||
Policy management
|
||||
|
||||
@ -28,7 +28,7 @@ characteristics to images.
|
||||
: Official LibGuestFS documentation.
|
||||
|
||||
`Logging and Monitoring
|
||||
<http://docs.openstack.org/ops-guide/ops_logging_monitoring.html>`_
|
||||
<http://docs.openstack.org/ops-guide/ops-logging-monitoring.html>`_
|
||||
: Official OpenStack Operations documentation.
|
||||
|
||||
`ManageIQ Cloud Management Platform <http://manageiq.org/>`_
|
||||
@ -47,7 +47,7 @@ and enable the delivery of the most efficient server,
|
||||
storage and data center hardware designs for scalable computing.
|
||||
|
||||
`OpenStack Flavors
|
||||
<http://docs.openstack.org/ops-guide/ops_user_facing_operations.html#flavors>`_
|
||||
<http://docs.openstack.org/ops-guide/ops-user-facing-operations.html#flavors>`_
|
||||
: Official OpenStack documentation.
|
||||
|
||||
`OpenStack High Availability Guide <http://docs.openstack.org/ha-guide/>`_
|
||||
|
||||
@ -93,7 +93,7 @@ service. The authentication service uses a combination of :term:`domains
|
||||
OpenStack service. The default policy for most services grants
|
||||
administrative access to the ``admin`` role. For more information,
|
||||
see the `OpenStack Operations Guide - Managing Projects and
|
||||
Users <http://docs.openstack.org/ops-guide/ops_projects_users.html>`__.
|
||||
Users <http://docs.openstack.org/ops-guide/ops-projects-users.html>`__.
|
||||
|
||||
#. This guide uses a service project that contains a unique user for each
|
||||
service that you add to your environment. Create the ``service``
|
||||
|
||||
@ -242,7 +242,7 @@ Access the instance remotely
|
||||
|
||||
If your instance does not launch or seem to work as you expect, see the
|
||||
`Instance Boot Failures
|
||||
<http://docs.openstack.org/ops-guide/ops_maintenance_compute.html#instances>`__
|
||||
<http://docs.openstack.org/ops-guide/ops-maintenance-compute.html#instances>`__
|
||||
section in OpenStack Operations Guide for more information or use one of
|
||||
the :doc:`many other options <common/app-support>`
|
||||
to seek assistance. We want your first installation to work!
|
||||
|
||||
@ -266,7 +266,7 @@ Access the instance remotely
|
||||
|
||||
If your instance does not launch or seem to work as you expect, see the
|
||||
`Instance Boot Failures
|
||||
<http://docs.openstack.org/ops-guide/ops_maintenance_compute.html#instances>`__
|
||||
<http://docs.openstack.org/ops-guide/ops-maintenance-compute.html#instances>`__
|
||||
section in OpenStack Operations Guide for more information or use one of
|
||||
the :doc:`many other options <common/app-support>`
|
||||
to seek assistance. We want your first installation to work!
|
||||
|
||||
@ -374,14 +374,14 @@ msgid ""
|
||||
"default policy for most services grants administrative access to the "
|
||||
"``admin`` role. For more information, see the `OpenStack Operations Guide - "
|
||||
"Managing Projects and Users <http://docs.openstack.org/ops-guide/"
|
||||
"ops_projects_users.html>`__."
|
||||
"ops-projects-users.html>`__."
|
||||
msgstr ""
|
||||
"Tous les rôles que vous créez doivent correspondre aux rôles spécifiés dans "
|
||||
"le fichier ``policy.json`` dans le répertoire des fichiers de configuration "
|
||||
"de chaque service OpenStack. La politique par défaut pour la plupart des "
|
||||
"services accorde des accès administratifs au rôle ``admin``. Pour plus "
|
||||
"d'informations, voir le `Guide des Opérations OpenStack - Gérer les Projets "
|
||||
"et les Utilisateurs <http://docs.openstack.org/ops-guide/ops_projects_users."
|
||||
"et les Utilisateurs <http://docs.openstack.org/ops-guide/ops-projects-users."
|
||||
"html>`__."
|
||||
|
||||
msgid "Appendix"
|
||||
|
||||
@ -417,14 +417,14 @@ msgid ""
|
||||
"default policy for most services grants administrative access to the "
|
||||
"``admin`` role. For more information, see the `OpenStack Operations Guide - "
|
||||
"Managing Projects and Users <http://docs.openstack.org/ops-guide/"
|
||||
"ops_projects_users.html>`__."
|
||||
"ops-projects-users.html>`__."
|
||||
msgstr ""
|
||||
"Apa peran yang Anda buat harus memetakan peran yang ditentukan dalam `` "
|
||||
"berkas policy.json`` di direktori file konfigurasi setiap layanan OpenStack. "
|
||||
"Kebijakan default untuk sebagian besar layanan memberikan akses "
|
||||
"administratif untuk `` peran admin``. Untuk informasi lebih lanjut, lihat "
|
||||
"`Panduan OpenStack Operasi - Managing Proyek dan Pengguna <http://docs."
|
||||
"openstack.org/ops-guide/ops_projects_users.html>` __."
|
||||
"openstack.org/ops-guide/ops-projects-users.html>` __."
|
||||
|
||||
msgid "Appendix"
|
||||
msgstr "Appendix"
|
||||
@ -2003,14 +2003,14 @@ msgstr ""
|
||||
msgid ""
|
||||
"If your instance does not launch or seem to work as you expect, see the "
|
||||
"`Instance Boot Failures <http://docs.openstack.org/ops-guide/"
|
||||
"ops_maintenance_compute.html#instances>`__ section in OpenStack Operations "
|
||||
"ops-maintenance-compute.html#instances>`__ section in OpenStack Operations "
|
||||
"Guide for more information or use one of the :doc:`many other options "
|
||||
"<common/app-support>` to seek assistance. We want your first installation to "
|
||||
"work!"
|
||||
msgstr ""
|
||||
"Jika misalnya Anda tidak memulai atau tampaknya bekerja seperti yang Anda "
|
||||
"harapkan, melihat `Kegagalan Instance Boot <http://docs.openstack.org/ops-"
|
||||
"guide/ops_maintenance_compute.html#instances>` __ bagian di Panduan "
|
||||
"guide/ops-maintenance-compute.html#instances>` __ bagian di Panduan "
|
||||
"OpenStack Operasi untuk lebih informasi atau menggunakan salah satu: doc: "
|
||||
"`banyak pilihan lain <umum / app-support>` untuk mencari bantuan. Kami ingin "
|
||||
"instalasi pertama Anda untuk bekerja!"
|
||||
|
||||
@ -433,13 +433,13 @@ msgid ""
|
||||
"default policy for most services grants administrative access to the "
|
||||
"``admin`` role. For more information, see the `OpenStack Operations Guide - "
|
||||
"Managing Projects and Users <http://docs.openstack.org/ops-guide/"
|
||||
"ops_projects_users.html>`__."
|
||||
"ops-projects-users.html>`__."
|
||||
msgstr ""
|
||||
"作成したロールは、各 OpenStack サービスの設定ファイルディレクトリーにある "
|
||||
"``policy.json`` ファイルに指定されたロールに対応している必要があります。ほと"
|
||||
"んどのサービスに対するデフォルトのポリシーでは、管理アクセス権が ``admin`` "
|
||||
"ロールに付与されています。詳細は、`OpenStack Operations Guide - Managing "
|
||||
"Projects and Users <http://docs.openstack.org/ops-guide/ops_projects_users."
|
||||
"Projects and Users <http://docs.openstack.org/ops-guide/ops-projects-users."
|
||||
"html>`__ を参照してください。"
|
||||
|
||||
msgid "Appendix"
|
||||
@ -2075,14 +2075,14 @@ msgstr ""
|
||||
msgid ""
|
||||
"If your instance does not launch or seem to work as you expect, see the "
|
||||
"`Instance Boot Failures <http://docs.openstack.org/ops-guide/"
|
||||
"ops_maintenance_compute.html#instances>`__ section in OpenStack Operations "
|
||||
"ops-maintenance-compute.html#instances>`__ section in OpenStack Operations "
|
||||
"Guide for more information or use one of the :doc:`many other options "
|
||||
"<common/app-support>` to seek assistance. We want your first installation to "
|
||||
"work!"
|
||||
msgstr ""
|
||||
"インスタンスが起動しない場合や期待通り動作しない場合、詳細は OpenStack "
|
||||
"Operations Guide の `Instance Boot Failures <http://docs.openstack.org/ops-"
|
||||
"guide/ops_maintenance_compute.html#instances>`__ セクションを参照してくださ"
|
||||
"guide/ops-maintenance-compute.html#instances>`__ セクションを参照してくださ"
|
||||
"い。または、支援を得るために :doc:`他の多くの方法 <common/app-support>` を利"
|
||||
"用してください。はじめてのインストール環境が正しく動作することを期待していま"
|
||||
"す。"
|
||||
|
||||
@ -437,13 +437,13 @@ msgid ""
|
||||
"default policy for most services grants administrative access to the "
|
||||
"``admin`` role. For more information, see the `OpenStack Operations Guide - "
|
||||
"Managing Projects and Users <http://docs.openstack.org/ops-guide/"
|
||||
"ops_projects_users.html>`__."
|
||||
"ops-projects-users.html>`__."
|
||||
msgstr ""
|
||||
"생성하는 모든 역할은 각 OpenStack 서비스에 대한 구성 파일 디렉토리 내에 있는 "
|
||||
"``policy.json`` 에 명시된 역할과 연결되어야 합니다. 대부분의 서비스에 대한 디"
|
||||
"폴트 정책은 ``admin`` 역할에 대해 관리 액세스를 부여하는 것입니다. 보다 자세"
|
||||
"한 정보는 `OpenStack Operations Guide - Managing Projects and Users <http://"
|
||||
"docs.openstack.org/ops-guide/ops_projects_users.html>`__ 를 살펴봅니다."
|
||||
"docs.openstack.org/ops-guide/ops-projects-users.html>`__ 를 살펴봅니다."
|
||||
|
||||
# auto translated by TM merge from project: openstack-manuals, version: stable-mitaka, DocId: doc/install-guide/source/locale/install-guide
|
||||
msgid "Appendix"
|
||||
|
||||
@ -219,7 +219,7 @@ The roadmap for the next release as it is developed can be seen at
|
||||
|
||||
To determine the potential features going in to future releases, or to
|
||||
look at features implemented previously, take a look at the existing
|
||||
blueprints such as `OpenStack Compute (nova)
|
||||
blueprints such as `OpenStack Compute (nova)
|
||||
Blueprints <https://blueprints.launchpad.net/nova>`_, `OpenStack
|
||||
Identity (keystone)
|
||||
Blueprints <https://blueprints.launchpad.net/keystone>`_, and release
|
||||
@ -266,7 +266,7 @@ tool. This tool tests database migration performance on copies of
|
||||
real-world user databases.
|
||||
|
||||
These changes have facilitated the first proper OpenStack upgrade guide,
|
||||
found in :doc:`ops_upgrades`, and will continue to improve in the next
|
||||
found in :doc:`ops-upgrades`, and will continue to improve in the next
|
||||
release.
|
||||
|
||||
Deprecation of Nova Network
|
||||
@ -368,7 +368,7 @@ space, and so on, are associated with a project.
|
||||
OpenStack Identity provides authentication decisions and user attribute
|
||||
information, which is then used by the other OpenStack services to
|
||||
perform authorization. The policy is set in the ``policy.json`` file.
|
||||
For information on how to configure these, see :doc:`ops_projects_users`
|
||||
For information on how to configure these, see :doc:`ops-projects-users`
|
||||
|
||||
OpenStack Identity supports different plug-ins for authentication
|
||||
decisions and identity storage. Examples of these plug-ins include:
|
||||
@ -69,7 +69,7 @@ community experience.
|
||||
|
||||
For example, KVM is the most widely adopted hypervisor in the OpenStack
|
||||
community. Besides KVM, more deployments run Xen, LXC, VMware, and
|
||||
Hyper-V than the others listed. However, each of these are lacking some
|
||||
Hyper-V than the others listed. However, each of these are lacking some
|
||||
feature support or the documentation on how to use them with OpenStack
|
||||
is out of date.
|
||||
|
||||
@ -281,7 +281,7 @@ particular use case.
|
||||
Logging
|
||||
~~~~~~~
|
||||
|
||||
Logging is detailed more fully in :doc:`ops_logging_monitoring`. However,
|
||||
Logging is detailed more fully in :doc:`ops-logging-monitoring`. However,
|
||||
it is an important design consideration to take into account before
|
||||
commencing operations of your cloud.
|
||||
|
||||
@ -294,7 +294,7 @@ Networking
|
||||
~~~~~~~~~~
|
||||
|
||||
Networking in OpenStack is a complex, multifaceted challenge. See
|
||||
:doc:`arch_network_design`.
|
||||
:doc:`arch-network-design`.
|
||||
|
||||
Conclusion
|
||||
~~~~~~~~~~
|
||||
@ -249,11 +249,11 @@ Optional Extensions
|
||||
|
||||
You can extend this reference architecture as follows:
|
||||
|
||||
- Add additional cloud controllers (see :doc:`ops_maintenance`).
|
||||
- Add additional cloud controllers (see :doc:`ops-maintenance`).
|
||||
|
||||
- Add an OpenStack Storage service (see the Object Storage chapter in
|
||||
the `OpenStack Installation Guide
|
||||
<http://docs.openstack.org/#install-guides>`_ for your distribution).
|
||||
|
||||
- Add additional OpenStack Block Storage hosts (see
|
||||
:doc:`ops_maintenance`).
|
||||
:doc:`ops-maintenance`).
|
||||
@ -5,7 +5,7 @@ Parting Thoughts on Architecture Examples
|
||||
With so many considerations and options available, our hope is to
|
||||
provide a few clearly-marked and tested paths for your OpenStack
|
||||
exploration. If you're looking for additional ideas, check out
|
||||
:doc:`app_usecases`, the
|
||||
:doc:`app-usecases`, the
|
||||
`OpenStack Installation Guides <http://docs.openstack.org/#install-guides>`_, or the
|
||||
`OpenStack User Stories
|
||||
page <http://www.openstack.org/user-stories/>`_.
|
||||
@ -25,6 +25,6 @@ serving users.
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
||||
arch_example_nova_network.rst
|
||||
arch_example_neutron.rst
|
||||
arch_example_thoughts.rst
|
||||
arch-example-nova-network.rst
|
||||
arch-example-neutron.rst
|
||||
arch-example-thoughts.rst
|
||||
@ -69,9 +69,9 @@ The starting point for most is the core count of your cloud. By applying
|
||||
some ratios, you can gather information about:
|
||||
|
||||
- The number of virtual machines (VMs) you expect to run,
|
||||
``((overcommit fraction × cores) / virtual cores per instance)``
|
||||
``((overcommit fraction × cores) / virtual cores per instance)``
|
||||
|
||||
- How much storage is required ``(flavor disk size × number of instances)``
|
||||
- How much storage is required ``(flavor disk size × number of instances)``
|
||||
|
||||
You can use these ratios to determine how much additional infrastructure
|
||||
you need to support your cloud.
|
||||
@ -117,7 +117,7 @@ of VMs every 30 seconds.
|
||||
|
||||
After you consider these factors, you can determine how many cloud
|
||||
controller cores you require. A typical eight core, 8 GB of RAM server
|
||||
is sufficient for up to a rack of compute nodes — given the above
|
||||
is sufficient for up to a rack of compute nodes — given the above
|
||||
caveats.
|
||||
|
||||
You must also consider key hardware specifications for the performance
|
||||
@ -128,7 +128,7 @@ bandwidth (Gbps/core), and overall CPU performance (CPU/core).
|
||||
.. tip::
|
||||
|
||||
For a discussion of metric tracking, including how to extract
|
||||
metrics from your cloud, see :doc:`ops_logging_monitoring`.
|
||||
metrics from your cloud, see :doc:`ops-logging-monitoring`.
|
||||
|
||||
Adding Cloud Controller Nodes
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
@ -416,7 +416,7 @@ When adding object storage nodes, a :term:`weight` should be specified
|
||||
that reflects the :term:`capability` of the node.
|
||||
|
||||
Monitoring the resource usage and user growth will enable you to know
|
||||
when to procure. :doc:`ops_logging_monitoring` details some useful metrics.
|
||||
when to procure. :doc:`ops-logging-monitoring` details some useful metrics.
|
||||
|
||||
Burn-in Testing
|
||||
---------------
|
||||
@ -43,10 +43,10 @@ architecture for an OpenStack cloud.
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
||||
arch_examples.rst
|
||||
arch_provision.rst
|
||||
arch_cloud_controller.rst
|
||||
arch_compute_nodes.rst
|
||||
arch_scaling.rst
|
||||
arch_storage.rst
|
||||
arch_network_design.rst
|
||||
arch-examples.rst
|
||||
arch-provision.rst
|
||||
arch-cloud-controller.rst
|
||||
arch-compute-nodes.rst
|
||||
arch-scaling.rst
|
||||
arch-storage.rst
|
||||
arch-network-design.rst
|
||||
|
||||
@ -25,10 +25,10 @@ Appendix
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
app_usecases.rst
|
||||
app_crypt.rst
|
||||
app_roadmaps.rst
|
||||
app_resources.rst
|
||||
app-usecases.rst
|
||||
app-crypt.rst
|
||||
app-roadmaps.rst
|
||||
app-resources.rst
|
||||
common/app-support.rst
|
||||
|
||||
Glossary
|
||||
|
||||
@ -28,13 +28,13 @@ problem.
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
||||
ops_lay_of_the_land.rst
|
||||
ops_projects_users.rst
|
||||
ops_user_facing_operations.rst
|
||||
ops_maintenance.rst
|
||||
ops_network_troubleshooting.rst
|
||||
ops_logging_monitoring.rst
|
||||
ops_backup_recovery.rst
|
||||
ops_customize.rst
|
||||
ops_advanced_configuration.rst
|
||||
ops_upgrades.rst
|
||||
ops-lay-of-the-land.rst
|
||||
ops-projects-users.rst
|
||||
ops-user-facing-operations.rst
|
||||
ops-maintenance.rst
|
||||
ops-network-troubleshooting.rst
|
||||
ops-logging-monitoring.rst
|
||||
ops-backup-recovery.rst
|
||||
ops-customize.rst
|
||||
ops-advanced-configuration.rst
|
||||
ops-upgrades.rst
|
||||
|
||||
@ -5,11 +5,11 @@ Customization
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
ops_customize_development.rst
|
||||
ops_customize_objectstorage.rst
|
||||
ops_customize_compute.rst
|
||||
ops_customize_dashboard.rst
|
||||
ops_customize_conclusion.rst
|
||||
ops-customize-development.rst
|
||||
ops-customize-objectstorage.rst
|
||||
ops-customize-compute.rst
|
||||
ops-customize-dashboard.rst
|
||||
ops-customize-conclusion.rst
|
||||
|
||||
OpenStack might not do everything you need it to do out of the box. To
|
||||
add a new feature, you can follow different paths.
|
||||
@ -5,9 +5,9 @@ Logging and Monitoring
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
ops_logging.rst
|
||||
ops_monitoring.rst
|
||||
ops_logging_monitoring_summary.rst
|
||||
ops-logging.rst
|
||||
ops-monitoring.rst
|
||||
ops-logging-monitoring-summary.rst
|
||||
|
||||
As an OpenStack cloud is composed of so many different services, there
|
||||
are a large number of log files. This chapter aims to assist you in
|
||||
@ -262,4 +262,4 @@ capabilities and configuration requirements.
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
|
||||
ops_logging_rsyslog.rst
|
||||
ops-logging-rsyslog.rst
|
||||
@ -88,7 +88,7 @@ The next best approach is to use a configuration-management tool, such
|
||||
as Puppet, to automatically build a cloud controller. This should not
|
||||
take more than 15 minutes if you have a spare server available. After
|
||||
the controller rebuilds, restore any backups taken
|
||||
(see :doc:`ops_backup_recovery`).
|
||||
(see :doc:`ops-backup-recovery`).
|
||||
|
||||
Also, in practice, the ``nova-compute`` services on the compute nodes do
|
||||
not always reconnect cleanly to rabbitmq hosted on the controller when
|
||||
@ -29,7 +29,7 @@ Terminal 2:
|
||||
# nova list
|
||||
|
||||
Look for any errors or traces in the log file. For more information, see
|
||||
:doc:`ops_logging_monitoring`.
|
||||
:doc:`ops-logging-monitoring`.
|
||||
|
||||
If the error indicates that the problem is with another component,
|
||||
switch to tailing that component's log file. For example, if nova cannot
|
||||
23
doc/ops-guide/source/ops-maintenance.rst
Normal file
23
doc/ops-guide/source/ops-maintenance.rst
Normal file
@ -0,0 +1,23 @@
|
||||
====================================
|
||||
Maintenance, Failures, and Debugging
|
||||
====================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
||||
ops-maintenance-controller.rst
|
||||
ops-maintenance-compute.rst
|
||||
ops-maintenance-storage.rst
|
||||
ops-maintenance-complete.rst
|
||||
ops-maintenance-configuration.rst
|
||||
ops-maintenance-hardware.rst
|
||||
ops-maintenance-database.rst
|
||||
ops-maintenance-rabbitmq.rst
|
||||
ops-maintenance-hdmwy.rst
|
||||
ops-maintenance-determine.rst
|
||||
ops-maintenance-slow.rst
|
||||
ops-uninstall.rst
|
||||
|
||||
Downtime, whether planned or unscheduled, is a certainty when running a
|
||||
cloud. This chapter aims to provide useful information for dealing
|
||||
proactively, or reactively, with these occurrences.
|
||||
@ -4,10 +4,10 @@ Managing Projects and Users
|
||||
|
||||
.. toctree::
|
||||
|
||||
ops_projects.rst
|
||||
ops_quotas.rst
|
||||
ops_users.rst
|
||||
ops_projects_users_summary.rst
|
||||
ops-projects.rst
|
||||
ops-quotas.rst
|
||||
ops-users.rst
|
||||
ops-projects-users-summary.rst
|
||||
|
||||
An OpenStack cloud does not have much value without users. This chapter
|
||||
covers topics that relate to managing users, projects, and quotas. This
|
||||
@ -1,23 +0,0 @@
|
||||
====================================
|
||||
Maintenance, Failures, and Debugging
|
||||
====================================
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
||||
ops_maintenance_controller.rst
|
||||
ops_maintenance_compute.rst
|
||||
ops_maintenance_storage.rst
|
||||
ops_maintenance_complete.rst
|
||||
ops_maintenance_configuration.rst
|
||||
ops_maintenance_hardware.rst
|
||||
ops_maintenance_database.rst
|
||||
ops_maintenance_rabbitmq.rst
|
||||
ops_maintenance_hdmwy.rst
|
||||
ops_maintenance_determine.rst
|
||||
ops_maintenance_slow.rst
|
||||
ops_uninstall.rst
|
||||
|
||||
Downtime, whether planned or unscheduled, is a certainty when running a
|
||||
cloud. This chapter aims to provide useful information for dealing
|
||||
proactively, or reactively, with these occurrences.
|
||||
@ -125,7 +125,7 @@ your OpenStack cloud.
|
||||
lot of background knowledge. However, if you are fairly new to cloud
|
||||
computing, we recommend that you make use of the :doc:`common/glossary`
|
||||
at the back of the book, as well as the online documentation for OpenStack
|
||||
and additional resources mentioned in this book in :doc:`app_resources`.
|
||||
and additional resources mentioned in this book in :doc:`app-resources`.
|
||||
|
||||
Further Reading
|
||||
---------------
|
||||
@ -190,38 +190,38 @@ OpenStack clouds.
|
||||
|
||||
**Part I:**
|
||||
|
||||
:doc:`arch_examples`
|
||||
:doc:`arch-examples`
|
||||
Because of all the decisions the other chapters discuss, this
|
||||
chapter describes the decisions made for this particular book and
|
||||
much of the justification for the example architecture.
|
||||
|
||||
:doc:`arch_provision`
|
||||
:doc:`arch-provision`
|
||||
While this book doesn't describe installation, we do recommend
|
||||
automation for deployment and configuration, discussed in this
|
||||
chapter.
|
||||
|
||||
:doc:`arch_cloud_controller`
|
||||
:doc:`arch-cloud-controller`
|
||||
The cloud controller is an invention for the sake of consolidating
|
||||
and describing which services run on which nodes. This chapter
|
||||
discusses hardware and network considerations as well as how to
|
||||
design the cloud controller for performance and separation of
|
||||
services.
|
||||
|
||||
:doc:`arch_compute_nodes`
|
||||
:doc:`arch-compute-nodes`
|
||||
This chapter describes the compute nodes, which are dedicated to
|
||||
running virtual machines. Some hardware choices come into play here,
|
||||
as well as logging and networking descriptions.
|
||||
|
||||
:doc:`arch_scaling`
|
||||
:doc:`arch-scaling`
|
||||
This chapter discusses the growth of your cloud resources through
|
||||
scaling and segregation considerations.
|
||||
|
||||
:doc:`arch_storage`
|
||||
:doc:`arch-storage`
|
||||
As with other architecture decisions, storage concepts within
|
||||
OpenStack offer many options. This chapter lays out the choices for
|
||||
you.
|
||||
|
||||
:doc:`arch_network_design`
|
||||
:doc:`arch-network-design`
|
||||
Your OpenStack cloud networking needs to fit into your existing
|
||||
networks while also enabling the best design for your users and
|
||||
administrators, and this chapter gives you in-depth information
|
||||
@ -229,68 +229,68 @@ OpenStack clouds.
|
||||
|
||||
**Part II:**
|
||||
|
||||
:doc:`ops_lay_of_the_land`
|
||||
:doc:`ops-lay-of-the-land`
|
||||
This chapter is written to let you get your hands wrapped around
|
||||
your OpenStack cloud through command-line tools and understanding
|
||||
what is already set up in your cloud.
|
||||
|
||||
:doc:`ops_projects_users`
|
||||
:doc:`ops-projects-users`
|
||||
This chapter walks through user-enabling processes that all admins
|
||||
must face to manage users, give them quotas to parcel out resources,
|
||||
and so on.
|
||||
|
||||
:doc:`ops_user_facing_operations`
|
||||
:doc:`ops-user-facing-operations`
|
||||
This chapter shows you how to use OpenStack cloud resources and how
|
||||
to train your users.
|
||||
|
||||
:doc:`ops_maintenance`
|
||||
:doc:`ops-maintenance`
|
||||
This chapter goes into the common failures that the authors have
|
||||
seen while running clouds in production, including troubleshooting.
|
||||
|
||||
:doc:`ops_network_troubleshooting`
|
||||
:doc:`ops-network-troubleshooting`
|
||||
Because network troubleshooting is especially difficult with virtual
|
||||
resources, this chapter is chock-full of helpful tips and tricks for
|
||||
tracing network traffic, finding the root cause of networking
|
||||
failures, and debugging related services, such as DHCP and DNS.
|
||||
|
||||
:doc:`ops_logging_monitoring`
|
||||
:doc:`ops-logging-monitoring`
|
||||
This chapter shows you where OpenStack places logs and how to best
|
||||
read and manage logs for monitoring purposes.
|
||||
|
||||
:doc:`ops_backup_recovery`
|
||||
:doc:`ops-backup-recovery`
|
||||
This chapter describes what you need to back up within OpenStack as
|
||||
well as best practices for recovering backups.
|
||||
|
||||
:doc:`ops_customize`
|
||||
:doc:`ops-customize`
|
||||
For readers who need to get a specialized feature into OpenStack,
|
||||
this chapter describes how to use DevStack to write custom
|
||||
middleware or a custom scheduler to rebalance your resources.
|
||||
|
||||
:doc:`ops_advanced_configuration`
|
||||
:doc:`ops-advanced-configuration`
|
||||
Much of OpenStack is driver-oriented, so you can plug in different
|
||||
solutions to the base set of services. This chapter describes some
|
||||
advanced configuration topics.
|
||||
|
||||
:doc:`ops_upgrades`
|
||||
:doc:`ops-upgrades`
|
||||
This chapter provides upgrade information based on the architectures
|
||||
used in this book.
|
||||
|
||||
**Back matter:**
|
||||
|
||||
:doc:`app_usecases`
|
||||
:doc:`app-usecases`
|
||||
You can read a small selection of use cases from the OpenStack
|
||||
community with some technical details and further resources.
|
||||
|
||||
:doc:`app_crypt`
|
||||
:doc:`app-crypt`
|
||||
These are shared legendary tales of image disappearances, VM
|
||||
massacres, and crazy troubleshooting techniques that result in
|
||||
hard-learned lessons and wisdom.
|
||||
|
||||
:doc:`app_roadmaps`
|
||||
:doc:`app-roadmaps`
|
||||
Read about how to track the OpenStack roadmap through the open and
|
||||
transparent development processes.
|
||||
|
||||
:doc:`app_resources`
|
||||
:doc:`app-resources`
|
||||
So many OpenStack resources are available online because of the
|
||||
fast-moving nature of the project, but there are also resources
|
||||
listed here that the authors found helpful while learning
|
||||
|
||||
@ -293,6 +293,58 @@ redirectmatch 301 ^/([a-z-]+)/ts_non_existent_host.html /$1/ts-non-existent-host
|
||||
redirectmatch 301 ^/([a-z-]+)/ts_non_existent_vlun.html /$1/ts-non-existent-vlun.html
|
||||
redirectmatch 301 ^/([a-z-]+)/ts_vol_attach_miss_sg_scan.html /$1/ts-vol-attach-miss-sg-scan.html
|
||||
|
||||
# Redirect renamed Ops Guide pages
|
||||
|
||||
redirect 301 /ops-guide/app_crypt.html /ops-guide/app-crypt.html
|
||||
redirect 301 /ops-guide/ops_advanced_configuration.html /ops-guide/ops-advanced-configuration.html
|
||||
redirect 301 /ops-guide/arch_provision.html /ops-guide/arch-provision.html
|
||||
redirect 301 /ops-guide/ops_customize.html /ops-guide/ops-customize.html
|
||||
redirect 301 /ops-guide/arch_example_neutron.html /ops-guide/arch-example-neutron.html
|
||||
redirect 301 /ops-guide/arch_example_nova_network.html /ops-guide/arch-example-nova-network.html
|
||||
redirect 301 /ops-guide/ops_lay_of_the_land.html /ops-guide/ops-lay-of-the-land.html
|
||||
redirect 301 /ops-guide/ops_maintenance_rabbitmq.html /ops-guide/ops-maintenance-rabbitmq.html
|
||||
redirect 301 /ops-guide/ops_customize_conclusion.html /ops-guide/ops-customize-conclusion.html
|
||||
redirect 301 /ops-guide/ops_maintenance_storage.html /ops-guide/ops-maintenance-storage.html
|
||||
redirect 301 /ops-guide/ops_maintenance_complete.html /ops-guide/ops-maintenance-complete.html
|
||||
redirect 301 /ops-guide/ops_logging_monitoring.html /ops-guide/ops-logging-monitoring.html
|
||||
redirect 301 /ops-guide/ops_logging.html /ops-guide/ops-logging.html
|
||||
redirect 301 /ops-guide/ops_maintenance_slow.html /ops-guide/ops-maintenance-slow.html
|
||||
redirect 301 /ops-guide/arch_examples.html /ops-guide/arch-examples.html
|
||||
redirect 301 /ops-guide/ops_backup_recovery.html /ops-guide/ops-backup-recovery.html
|
||||
redirect 301 /ops-guide/ops_maintenance_configuration.html /ops-guide/ops-maintenance-configuration.html
|
||||
redirect 301 /ops-guide/ops_maintenance_hardware.html /ops-guide/ops-maintenance-hardware.html
|
||||
redirect 301 /ops-guide/ops_customize_dashboard.html /ops-guide/ops-customize-dashboard.html
|
||||
redirect 301 /ops-guide/ops_uninstall.html /ops-guide/ops-uninstall.html
|
||||
redirect 301 /ops-guide/arch_storage.html /ops-guide/arch-storage.html
|
||||
redirect 301 /ops-guide/app_roadmaps.html /ops-guide/app-roadmaps.html
|
||||
redirect 301 /ops-guide/ops_maintenance_database.html /ops-guide/ops-maintenance-database.html
|
||||
redirect 301 /ops-guide/ops_maintenance_hdmwy.html /ops-guide/ops-maintenance-hdmwy.html
|
||||
redirect 301 /ops-guide/ops_customize_compute.html /ops-guide/ops-customize-compute.html
|
||||
redirect 301 /ops-guide/arch_cloud_controller.html /ops-guide/arch-cloud-controller.html
|
||||
redirect 301 /ops-guide/ops_maintenance_controller.html /ops-guide/ops-maintenance-controller.html
|
||||
redirect 301 /ops-guide/ops_customize_development.html /ops-guide/ops-customize-development.html
|
||||
redirect 301 /ops-guide/ops_maintenance_compute.html /ops-guide/ops-maintenance-compute.html
|
||||
redirect 301 /ops-guide/app_resources.html /ops-guide/app-resources.html
|
||||
redirect 301 /ops-guide/ops_projects.html /ops-guide/ops-projects.html
|
||||
redirect 301 /ops-guide/arch_compute_nodes.html /ops-guide/arch-compute-nodes.html
|
||||
redirect 301 /ops-guide/ops_projects_users.html /ops-guide/ops-projects-users.html
|
||||
redirect 301 /ops-guide/ops_quotas.html /ops-guide/ops-quotas.html
|
||||
redirect 301 /ops-guide/arch_network_design.html /ops-guide/arch-network-design.html
|
||||
redirect 301 /ops-guide/ops_customize_objectstorage.html /ops-guide/ops-customize-objectstorage.html
|
||||
redirect 301 /ops-guide/arch_scaling.html /ops-guide/arch-scaling.html
|
||||
redirect 301 /ops-guide/ops_user_facing_operations.html /ops-guide/ops-user-facing-operations.html
|
||||
redirect 301 /ops-guide/ops_maintenance_determine.html /ops-guide/ops-maintenance-determine.html
|
||||
redirect 301 /ops-guide/ops_monitoring.html /ops-guide/ops-monitoring.html
|
||||
redirect 301 /ops-guide/ops_upgrades.html /ops-guide/ops-upgrades.html
|
||||
redirect 301 /ops-guide/ops_projects_users_summary.html /ops-guide/ops-projects-users-summary.html
|
||||
redirect 301 /ops-guide/arch_example_thoughts.html /ops-guide/arch-example-thoughts.html
|
||||
redirect 301 /ops-guide/ops_users.html /ops-guide/ops-users.html
|
||||
redirect 301 /ops-guide/app_usecases.html /ops-guide/app-usecases.html
|
||||
redirect 301 /ops-guide/ops_network_troubleshooting.html /ops-guide/ops-network-troubleshooting.html
|
||||
redirect 301 /ops-guide/ops_logging_monitoring_summary.html /ops-guide/ops-logging-monitoring-summary.html
|
||||
redirect 301 /ops-guide/ops_logging_rsyslog.html /ops-guide/ops-logging-rsyslog.html
|
||||
redirect 301 /ops-guide/ops_maintenance.html /ops-guide/ops-maintenance.html
|
||||
|
||||
# Since we don't have a direct match for all file, redirect to the index page.
|
||||
|
||||
redirectmatch 301 "^/user-guide/content/.*$" /user-guide/index.html
|
||||
|
||||
Loading…
Reference in New Issue
Block a user