Update the ops-guide reference links with new ones
Change-Id: Iac6dc9e9a0b92dfc03456a099096bd59a9255fc1
This commit is contained in:
parent
c8de69deca
commit
7718456078
doc
admin-guide/source
arch-design-draft/source/arch-guide-draft-mitaka
high-availability.rstintroduction.rstoperator-requirements-quota-management.rstoperator-requirements-upgrades.rsttechnical-requirements-logging-monitoring.rst
arch-design/source
compute-focus-technical-considerations.rstgeneralpurpose-technical-considerations.rstintroduction-intended-audience.rstmulti-site-operational-considerations.rstreferences.rst
install-guide/source
@ -28,5 +28,5 @@ Amazon EC2 Elastic Block Storage (EBS) offering.
|
||||
blockstorage-manage-volumes.rst
|
||||
blockstorage-troubleshoot.rst
|
||||
|
||||
.. _`Storage Decisions`: http://docs.openstack.org/openstack-ops/content/storage_decision.html
|
||||
.. _`OpenStack Operations Guide`: http://docs.openstack.org/ops/
|
||||
.. _`Storage Decisions`: http://docs.openstack.org/ops-guide/arch_storage.html
|
||||
.. _`OpenStack Operations Guide`: http://docs.openstack.org/ops-guide/
|
||||
|
@ -121,7 +121,8 @@ Create a flavor
|
||||
#. If an individual user or group of users needs a custom
|
||||
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/openstack-ops/content/private-flavors.html>`_.
|
||||
See
|
||||
`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/openstack-ops/content/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/openstack-ops/content/network_design.html#network_deployment_options>`_.
|
||||
<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
|
||||
|
@ -15,7 +15,7 @@ Intended audience
|
||||
This book has been written for architects and designers of OpenStack
|
||||
clouds. For a guide on deploying and operating OpenStack, please refer
|
||||
to the
|
||||
`OpenStack Operations Guide <http://docs.openstack.org/openstack-ops/>`_.
|
||||
`OpenStack Operations Guide <http://docs.openstack.org/ops-guide/>`_.
|
||||
|
||||
Before reading this book, we recommend:
|
||||
|
||||
|
@ -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/openstack-ops/content/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/openstack-ops/content/ops_upgrades-general-steps.html>`_
|
||||
chapter <http://docs.openstack.org/ops-guide/ops_upgrades.html>`_
|
||||
of the OpenStack Operations Guide for details):
|
||||
|
||||
#. Upgrade the OpenStack Identity service (keystone).
|
||||
|
2
doc/arch-design-draft/source/arch-guide-draft-mitaka/technical-requirements-logging-monitoring.rst
2
doc/arch-design-draft/source/arch-guide-draft-mitaka/technical-requirements-logging-monitoring.rst
@ -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/openstack-ops/content/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.
|
||||
|
||||
|
@ -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/openstack-ops/content/flavors.html>`_.
|
||||
Flavors <http://docs.openstack.org/ops-guide/ops_user_facing_operations.html#flavors>`_.
|
||||
|
||||
OpenStack components
|
||||
~~~~~~~~~~~~~~~~~~~~
|
||||
|
@ -521,9 +521,9 @@ 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 `OpenStack
|
||||
Operations
|
||||
Guide <http://docs.openstack.org/openstack-ops/content/network_design.html#network_deployment_options>`_.
|
||||
different network deployment models described in the
|
||||
`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.
|
||||
|
||||
|
@ -3,7 +3,7 @@ Intended audience
|
||||
|
||||
This book has been written for architects and designers of OpenStack
|
||||
clouds. For a guide on deploying and operating OpenStack, please refer
|
||||
to the `OpenStack Operations Guide <http://docs.openstack.org/openstack-ops/>`_.
|
||||
to the `OpenStack Operations Guide <http://docs.openstack.org/ops-guide/>`_.
|
||||
|
||||
Before reading this book, we recommend prior knowledge of cloud
|
||||
architecture and principles, experience in enterprise system design,
|
||||
|
@ -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/openstack-ops/content/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/openstack-ops/content/ops_upgrades-general-steps.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/openstack-ops/content/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/openstack-ops/content/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/openstack-ops/content/flavors.html>`_
|
||||
<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/>`_
|
||||
@ -61,7 +61,7 @@ storage and data center hardware designs for scalable computing.
|
||||
<http://docs.openstack.org/developer/swift/replication_network.html>`_
|
||||
: Developer documentation of Swift replication.
|
||||
|
||||
`OpenStack Operations Guide <http://docs.openstack.org/openstack-ops/>`_
|
||||
`OpenStack Operations Guide <http://docs.openstack.org/ops-guide/>`_
|
||||
: The OpenStack Operations Guide provides information on setting up
|
||||
and installing OpenStack.
|
||||
|
||||
|
@ -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/openstack-ops/content/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``
|
||||
|
@ -146,7 +146,7 @@ Launch the instance
|
||||
+--------------------------------------+-------------------+--------+---------------------------------+
|
||||
| ID | Name | Status | Networks |
|
||||
+--------------------------------------+-------------------+--------+---------------------------------+
|
||||
| 181c52ba-aebc-4c32-a97d-2e8e82e4eaaf | provider-instance | ACTIVE | provider=203.0.113.103 |
|
||||
| 181c52ba-aebc-4c32-a97d-2e8e82e4eaaf | provider-instance | ACTIVE | provider=203.0.113.103 |
|
||||
+--------------------------------------+-------------------+--------+---------------------------------+
|
||||
|
||||
The status changes from ``BUILD`` to ``ACTIVE`` when the build process
|
||||
@ -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/openstack-ops/content/instances.html#instance_boot_failures>`__
|
||||
<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/openstack-ops/content/instances.html#instance_boot_failures>`__
|
||||
<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!
|
||||
|
Loading…
x
Reference in New Issue
Block a user