diff --git a/doc/admin-guide/source/blockstorage.rst b/doc/admin-guide/source/blockstorage.rst index d30de97af5..c7c7b649fe 100644 --- a/doc/admin-guide/source/blockstorage.rst +++ b/doc/admin-guide/source/blockstorage.rst @@ -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/ diff --git a/doc/admin-guide/source/cli_manage_flavors.rst b/doc/admin-guide/source/cli_manage_flavors.rst index d2667c5820..1f6f08adf3 100644 --- a/doc/admin-guide/source/cli_manage_flavors.rst +++ b/doc/admin-guide/source/cli_manage_flavors.rst @@ -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 `_. + See + `Private Flavors in the OpenStack Operations Guide `_. For a list of optional parameters, run this command: diff --git a/doc/admin-guide/source/compute-networking-nova.rst b/doc/admin-guide/source/compute-networking-nova.rst index a72637b456..ad93fa98bf 100644 --- a/doc/admin-guide/source/compute-networking-nova.rst +++ b/doc/admin-guide/source/compute-networking-nova.rst @@ -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 -`__. +`__. All networking options require network connectivity to be already set up between OpenStack physical nodes. OpenStack does not configure any diff --git a/doc/arch-design-draft/source/arch-guide-draft-mitaka/high-availability.rst b/doc/arch-design-draft/source/arch-guide-draft-mitaka/high-availability.rst index 56d28e32f4..53005accd3 100644 --- a/doc/arch-design-draft/source/arch-guide-draft-mitaka/high-availability.rst +++ b/doc/arch-design-draft/source/arch-guide-draft-mitaka/high-availability.rst @@ -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 -`_. +`_. When using the Networking service, the OpenStack controller servers or separate Networking hosts handle routing unless the dynamic virtual routers pattern for diff --git a/doc/arch-design-draft/source/arch-guide-draft-mitaka/introduction.rst b/doc/arch-design-draft/source/arch-guide-draft-mitaka/introduction.rst index 9cff71f50d..eb19ad05ea 100644 --- a/doc/arch-design-draft/source/arch-guide-draft-mitaka/introduction.rst +++ b/doc/arch-design-draft/source/arch-guide-draft-mitaka/introduction.rst @@ -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 `_. +`OpenStack Operations Guide `_. Before reading this book, we recommend: diff --git a/doc/arch-design-draft/source/arch-guide-draft-mitaka/operator-requirements-quota-management.rst b/doc/arch-design-draft/source/arch-guide-draft-mitaka/operator-requirements-quota-management.rst index 859a600c30..dcba50f5dd 100644 --- a/doc/arch-design-draft/source/arch-guide-draft-mitaka/operator-requirements-quota-management.rst +++ b/doc/arch-design-draft/source/arch-guide-draft-mitaka/operator-requirements-quota-management.rst @@ -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 `__ +chapter `__ of the OpenStack Operators Guide. diff --git a/doc/arch-design-draft/source/arch-guide-draft-mitaka/operator-requirements-upgrades.rst b/doc/arch-design-draft/source/arch-guide-draft-mitaka/operator-requirements-upgrades.rst index 14f9a29d50..4c4663cf2c 100644 --- a/doc/arch-design-draft/source/arch-guide-draft-mitaka/operator-requirements-upgrades.rst +++ b/doc/arch-design-draft/source/arch-guide-draft-mitaka/operator-requirements-upgrades.rst @@ -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 `_ +chapter `_ of the OpenStack Operations Guide for details): #. Upgrade the OpenStack Identity service (keystone). diff --git a/doc/arch-design-draft/source/arch-guide-draft-mitaka/technical-requirements-logging-monitoring.rst b/doc/arch-design-draft/source/arch-guide-draft-mitaka/technical-requirements-logging-monitoring.rst index 74a5f2ba71..06e070ecea 100644 --- a/doc/arch-design-draft/source/arch-guide-draft-mitaka/technical-requirements-logging-monitoring.rst +++ b/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 -`__ of +`__ of the Operations Guide remain applicable. Logging and monitoring can be provided on a per-site basis, and in a common centralized location. diff --git a/doc/arch-design/source/compute-focus-technical-considerations.rst b/doc/arch-design/source/compute-focus-technical-considerations.rst index 341d18354f..2c179d4637 100644 --- a/doc/arch-design/source/compute-focus-technical-considerations.rst +++ b/doc/arch-design/source/compute-focus-technical-considerations.rst @@ -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 `_. +Flavors `_. OpenStack components ~~~~~~~~~~~~~~~~~~~~ diff --git a/doc/arch-design/source/generalpurpose-technical-considerations.rst b/doc/arch-design/source/generalpurpose-technical-considerations.rst index c0cc60cf2c..0ad8f9f7c6 100644 --- a/doc/arch-design/source/generalpurpose-technical-considerations.rst +++ b/doc/arch-design/source/generalpurpose-technical-considerations.rst @@ -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 `_. +different network deployment models described in the +`Networking deployment options table ` +of OpenStack Operations Guide. Ensure your deployment has adequate back-up capabilities. diff --git a/doc/arch-design/source/introduction-intended-audience.rst b/doc/arch-design/source/introduction-intended-audience.rst index e9c217144e..3c0dc42dac 100644 --- a/doc/arch-design/source/introduction-intended-audience.rst +++ b/doc/arch-design/source/introduction-intended-audience.rst @@ -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 `_. +to the `OpenStack Operations Guide `_. Before reading this book, we recommend prior knowledge of cloud architecture and principles, experience in enterprise system design, diff --git a/doc/arch-design/source/multi-site-operational-considerations.rst b/doc/arch-design/source/multi-site-operational-considerations.rst index 76953b3fa9..2c30dcaef3 100644 --- a/doc/arch-design/source/multi-site-operational-considerations.rst +++ b/doc/arch-design/source/multi-site-operational-considerations.rst @@ -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 `__ +chapter `__ 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 `__ +chapter `__ 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 `__ +chapter `__ of the OpenStack Operators Guide. Policy management diff --git a/doc/arch-design/source/references.rst b/doc/arch-design/source/references.rst index fbcd5b7c02..85513a67f7 100644 --- a/doc/arch-design/source/references.rst +++ b/doc/arch-design/source/references.rst @@ -28,7 +28,7 @@ characteristics to images. : Official LibGuestFS documentation. `Logging and Monitoring -`_ +`_ : Official OpenStack Operations documentation. `ManageIQ Cloud Management Platform `_ @@ -47,7 +47,7 @@ and enable the delivery of the most efficient server, storage and data center hardware designs for scalable computing. `OpenStack Flavors -`_ +`_ : Official OpenStack documentation. `OpenStack High Availability Guide `_ @@ -61,7 +61,7 @@ storage and data center hardware designs for scalable computing. `_ : Developer documentation of Swift replication. -`OpenStack Operations Guide `_ +`OpenStack Operations Guide `_ : The OpenStack Operations Guide provides information on setting up and installing OpenStack. diff --git a/doc/install-guide/source/keystone-users.rst b/doc/install-guide/source/keystone-users.rst index a2ca5e023c..98478186a1 100644 --- a/doc/install-guide/source/keystone-users.rst +++ b/doc/install-guide/source/keystone-users.rst @@ -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 `__. + Users `__. #. This guide uses a service project that contains a unique user for each service that you add to your environment. Create the ``service`` diff --git a/doc/install-guide/source/launch-instance-provider.rst b/doc/install-guide/source/launch-instance-provider.rst index e020f12f28..dd5102854e 100644 --- a/doc/install-guide/source/launch-instance-provider.rst +++ b/doc/install-guide/source/launch-instance-provider.rst @@ -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 -`__ +`__ section in OpenStack Operations Guide for more information or use one of the :doc:`many other options ` to seek assistance. We want your first installation to work! diff --git a/doc/install-guide/source/launch-instance-selfservice.rst b/doc/install-guide/source/launch-instance-selfservice.rst index 6a82574b47..d7eae821f2 100644 --- a/doc/install-guide/source/launch-instance-selfservice.rst +++ b/doc/install-guide/source/launch-instance-selfservice.rst @@ -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 -`__ +`__ section in OpenStack Operations Guide for more information or use one of the :doc:`many other options ` to seek assistance. We want your first installation to work!