[ops-guide] move operations content into top level
To improve readability with table of content. Change-Id: I7e06ac3b55f7fec2dac07f1d54ee8d5c1272b0f4
This commit is contained in:
parent
46c669ecdc
commit
6879a52890
@ -5,7 +5,30 @@ OpenStack Operations Guide
|
|||||||
Abstract
|
Abstract
|
||||||
~~~~~~~~
|
~~~~~~~~
|
||||||
|
|
||||||
This book provides information about designing and operating OpenStack clouds.
|
This guide provides information about operating OpenStack clouds.
|
||||||
|
|
||||||
|
We recommend that you turn to the `Installation Tutorials and Guides
|
||||||
|
<https://docs.openstack.org/project-install-guide/ocata/>`_,
|
||||||
|
which contains a step-by-step guide on how to manually install the
|
||||||
|
OpenStack packages and dependencies on your cloud.
|
||||||
|
|
||||||
|
While it is important for an operator to be familiar with the steps
|
||||||
|
involved in deploying OpenStack, we also strongly encourage you to
|
||||||
|
evaluate `OpenStack deployment tools
|
||||||
|
<https://docs.openstack.org/developer/openstack-projects.html>`_
|
||||||
|
and configuration-management tools, such as :term:`Puppet` or
|
||||||
|
:term:`Chef`, which can help automate this deployment process.
|
||||||
|
|
||||||
|
In this guide, we assume that you have successfully deployed an
|
||||||
|
OpenStack cloud and are able to perform basic operations
|
||||||
|
such as adding images, booting instances, and attaching volumes.
|
||||||
|
|
||||||
|
As your focus turns to stable operations, we recommend that you do skim
|
||||||
|
this guide to get a sense of the content. Some of this content is useful
|
||||||
|
to read in advance so that you can put best practices into effect to
|
||||||
|
simplify your life in the long run. Other content is more useful as a
|
||||||
|
reference that you might turn to when an unexpected event occurs (such
|
||||||
|
as a power failure), or to troubleshoot a particular problem.
|
||||||
|
|
||||||
Contents
|
Contents
|
||||||
~~~~~~~~
|
~~~~~~~~
|
||||||
@ -16,7 +39,16 @@ Contents
|
|||||||
acknowledgements.rst
|
acknowledgements.rst
|
||||||
preface.rst
|
preface.rst
|
||||||
common/conventions.rst
|
common/conventions.rst
|
||||||
operations.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
|
||||||
|
|
||||||
Appendix
|
Appendix
|
||||||
~~~~~~~~
|
~~~~~~~~
|
||||||
|
@ -1,40 +0,0 @@
|
|||||||
==========
|
|
||||||
Operations
|
|
||||||
==========
|
|
||||||
|
|
||||||
Congratulations! By now, you should have a solid design for your cloud.
|
|
||||||
We now recommend that you turn to the `Installation Tutorials and Guides
|
|
||||||
<https://docs.openstack.org/project-install-guide/ocata/>`_, which contains a
|
|
||||||
step-by-step guide on how to manually install the OpenStack packages and
|
|
||||||
dependencies on your cloud.
|
|
||||||
|
|
||||||
While it is important for an operator to be familiar with the steps
|
|
||||||
involved in deploying OpenStack, we also strongly encourage you to
|
|
||||||
evaluate configuration-management tools, such as :term:`Puppet` or
|
|
||||||
:term:`Chef`, which can help automate this deployment process.
|
|
||||||
|
|
||||||
In the remainder of this guide, we assume that you have successfully
|
|
||||||
deployed an OpenStack cloud and are able to perform basic operations
|
|
||||||
such as adding images, booting instances, and attaching volumes.
|
|
||||||
|
|
||||||
As your focus turns to stable operations, we recommend that you do skim
|
|
||||||
the remainder of this book to get a sense of the content. Some of this
|
|
||||||
content is useful to read in advance so that you can put best practices
|
|
||||||
into effect to simplify your life in the long run. Other content is more
|
|
||||||
useful as a reference that you might turn to when an unexpected event
|
|
||||||
occurs (such as a power failure), or to troubleshoot a particular
|
|
||||||
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
|
|
@ -90,6 +90,9 @@ redirectmatch 301 /ops/.*$ /ops-guide/index.html
|
|||||||
# Redirect Operations Guide architecture part to Architecture Guide
|
# Redirect Operations Guide architecture part to Architecture Guide
|
||||||
redirectmatch 301 /ops-guide/arch.*$ /arch-design/index.html
|
redirectmatch 301 /ops-guide/arch.*$ /arch-design/index.html
|
||||||
|
|
||||||
|
# Redirect Operations Guide operations to index
|
||||||
|
redirect 301 /ops-guide/operations.html /ops-guide/index.html
|
||||||
|
|
||||||
# Redirect Architecture Guide to /arch-design/
|
# Redirect Architecture Guide to /arch-design/
|
||||||
redirect 301 /arch/index.html /arch-design/index.html
|
redirect 301 /arch/index.html /arch-design/index.html
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user