From 6073a8b3e587f86aed88a225b2cb71f3b59f40dc Mon Sep 17 00:00:00 2001 From: KATO Tomoyuki Date: Fri, 27 Jan 2017 22:59:24 +0900 Subject: [PATCH] [arch-design] use https instead of http for docs.o.o Change-Id: I130acc6e045e76d479b2d2bccdd50f2a377a6afb --- doc/arch-design-draft/setup.cfg | 2 +- .../source/capacity-planning-scaling.rst | 8 ++++---- .../source/design-compute/design-compute-cpu.rst | 2 +- .../design-compute/design-compute-hardware.rst | 2 +- .../design-compute/design-compute-hypervisor.rst | 4 ++-- .../design-compute/design-compute-networking.rst | 2 +- .../design-compute/design-compute-overcommit.rst | 2 +- .../source/design-control-plane.rst | 2 +- doc/arch-design-draft/source/design-networking.rst | 2 +- .../design-networking/design-networking-design.rst | 2 +- .../design-storage/design-storage-concepts.rst | 4 ++-- .../design-storage/design-storage-object.rst | 2 +- .../design-storage-planning-scaling.rst | 2 +- doc/arch-design-draft/source/high-availability.rst | 4 ++-- .../source/overview-customer-requirements.rst | 2 +- .../source/overview-operator-requirements.rst | 8 ++++---- .../source/overview-security-requirements.rst | 2 +- doc/arch-design-draft/source/overview.rst | 2 +- doc/arch-design/setup.cfg | 2 +- .../source/compute-focus-architecture.rst | 2 +- .../compute-focus-technical-considerations.rst | 2 +- .../source/generalpurpose-architecture.rst | 4 ++-- .../generalpurpose-operational-considerations.rst | 2 +- .../generalpurpose-technical-considerations.rst | 6 +++--- .../source/introduction-intended-audience.rst | 2 +- .../source/legal-security-requirements.rst | 2 +- .../multi-site-operational-considerations.rst | 6 +++--- .../source/multi-site-technical-considerations.rst | 2 +- .../source/multi-site-user-requirements.rst | 2 +- doc/arch-design/source/references.rst | 14 +++++++------- doc/arch-design/source/specialized-hardware.rst | 2 +- .../source/storage-focus-architecture.rst | 2 +- 32 files changed, 52 insertions(+), 52 deletions(-) diff --git a/doc/arch-design-draft/setup.cfg b/doc/arch-design-draft/setup.cfg index 3cc38ba319..cdcc8fec9c 100644 --- a/doc/arch-design-draft/setup.cfg +++ b/doc/arch-design-draft/setup.cfg @@ -3,7 +3,7 @@ name = architecturedesignguide summary = OpenStack Architecture Design Guide author = OpenStack author-email = openstack-docs@lists.openstack.org -home-page = http://docs.openstack.org/ +home-page = https://docs.openstack.org/ classifier = Environment :: OpenStack Intended Audience :: Information Technology diff --git a/doc/arch-design-draft/source/capacity-planning-scaling.rst b/doc/arch-design-draft/source/capacity-planning-scaling.rst index bdd2884a11..ba449fa8ca 100644 --- a/doc/arch-design-draft/source/capacity-planning-scaling.rst +++ b/doc/arch-design-draft/source/capacity-planning-scaling.rst @@ -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 - `_. + `_. Adding Cloud Controller Nodes ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -152,7 +152,7 @@ load-balancing method (DNS round robin, hardware load balancer, or software such as Pound or HAProxy). One caveat with dashboard is the VNC proxy, which uses the WebSocket protocol— something that an L7 load balancer might struggle with. See also `Horizon session storage -`_. +`_. You can configure some services, such as ``nova-api`` and ``glance-api``, to use multiple processes by changing a flag in their @@ -165,7 +165,7 @@ the one machine. supported AMQP brokers have built-in clustering support. Information on how to configure these and many of the other services can be found in the `operations chapter - `_ in the Operations + `_ in the Operations Guide. Segregating Your Cloud @@ -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 -`_ +`_ chapte in the Operations Guide details some useful metrics. Burn-in Testing diff --git a/doc/arch-design-draft/source/design-compute/design-compute-cpu.rst b/doc/arch-design-draft/source/design-compute/design-compute-cpu.rst index 629af85a53..5180b2dc28 100644 --- a/doc/arch-design-draft/source/design-compute/design-compute-cpu.rst +++ b/doc/arch-design-draft/source/design-compute/design-compute-cpu.rst @@ -56,7 +56,7 @@ Additionally, CPU selection may not be one-size-fits-all across enterprises, but more of a list of SKUs that are tuned for the enterprise workloads. A deeper discussion about NUMA can be found in `CPU topologies in the Admin -Guide `_. +Guide `_. In order to take advantage of these new enhancements in OpenStack nova, Compute hosts must be using NUMA capable CPUs. diff --git a/doc/arch-design-draft/source/design-compute/design-compute-hardware.rst b/doc/arch-design-draft/source/design-compute/design-compute-hardware.rst index 38aeeb1d01..1d2a18c1ec 100644 --- a/doc/arch-design-draft/source/design-compute/design-compute-hardware.rst +++ b/doc/arch-design-draft/source/design-compute/design-compute-hardware.rst @@ -59,7 +59,7 @@ under the CPU selection secution. However, there are also network and storage considerations for any compute server. Network considerations are discussed in the `network section -`_ +`_ of this chapter. diff --git a/doc/arch-design-draft/source/design-compute/design-compute-hypervisor.rst b/doc/arch-design-draft/source/design-compute/design-compute-hypervisor.rst index ef14b5bdd9..6e6ff37b86 100644 --- a/doc/arch-design-draft/source/design-compute/design-compute-hypervisor.rst +++ b/doc/arch-design-draft/source/design-compute/design-compute-hypervisor.rst @@ -31,9 +31,9 @@ hypervisors as well as ironic and Virtuozzo (formerly Parallels). The best information available to support your choice is found on the `Hypervisor Support Matrix -`_ +`_ and in the `configuration reference -`_. +`_. .. note:: diff --git a/doc/arch-design-draft/source/design-compute/design-compute-networking.rst b/doc/arch-design-draft/source/design-compute/design-compute-networking.rst index c8c028f0a3..2ced5a3201 100644 --- a/doc/arch-design-draft/source/design-compute/design-compute-networking.rst +++ b/doc/arch-design-draft/source/design-compute/design-compute-networking.rst @@ -47,4 +47,4 @@ be handled by a SDN other than neutron. However, when using neutron DVR with OVS, this network must be present on the compute node since north and south traffic will not be handled by the controller nodes, but by the compute node itself. For more information on DVR with OVS and compute nodes, see `Scenario: -High Availability using Distributed Virtual Routing (DVR) `_ +High Availability using Distributed Virtual Routing (DVR) `_ diff --git a/doc/arch-design-draft/source/design-compute/design-compute-overcommit.rst b/doc/arch-design-draft/source/design-compute/design-compute-overcommit.rst index 3074733de3..2a0b25b91d 100644 --- a/doc/arch-design-draft/source/design-compute/design-compute-overcommit.rst +++ b/doc/arch-design-draft/source/design-compute/design-compute-overcommit.rst @@ -50,7 +50,7 @@ Logging ~~~~~~~ Logging is described in more detail in `Logging and Monitoring -`_. However, +`_. However, it is an important design consideration to take into account before commencing operations of your cloud. diff --git a/doc/arch-design-draft/source/design-control-plane.rst b/doc/arch-design-draft/source/design-control-plane.rst index f2ef2eff30..ec96190f45 100644 --- a/doc/arch-design-draft/source/design-control-plane.rst +++ b/doc/arch-design-draft/source/design-control-plane.rst @@ -373,7 +373,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 -`_ in the +`_ in the OpenStack Operations Guide. OpenStack Identity supports different plug-ins for authentication diff --git a/doc/arch-design-draft/source/design-networking.rst b/doc/arch-design-draft/source/design-networking.rst index 5e811df268..85ffd87190 100644 --- a/doc/arch-design-draft/source/design-networking.rst +++ b/doc/arch-design-draft/source/design-networking.rst @@ -21,7 +21,7 @@ services that are essential for stable operation. Additionally, you must research and discuss cloud network connectivity through proxy servers and firewalls. -See the `OpenStack Security Guide `_ for tips +See the `OpenStack Security Guide `_ for tips on securing your network. Networking (neutron) diff --git a/doc/arch-design-draft/source/design-networking/design-networking-design.rst b/doc/arch-design-draft/source/design-networking/design-networking-design.rst index 2f0f67c0c8..c6b4719146 100644 --- a/doc/arch-design-draft/source/design-networking/design-networking-design.rst +++ b/doc/arch-design-draft/source/design-networking/design-networking-design.rst @@ -286,7 +286,7 @@ examples include: * Routing daemons Some of these software packages are described in more detail in the -`OpenStack network nodes chapter `_ +`OpenStack network nodes chapter `_ in the OpenStack High Availability Guide. For a general purpose OpenStack cloud, the OpenStack infrastructure diff --git a/doc/arch-design-draft/source/design-storage/design-storage-concepts.rst b/doc/arch-design-draft/source/design-storage/design-storage-concepts.rst index 10087a48dc..b6914ba778 100644 --- a/doc/arch-design-draft/source/design-storage/design-storage-concepts.rst +++ b/doc/arch-design-draft/source/design-storage/design-storage-concepts.rst @@ -93,7 +93,7 @@ provided by OpenStack. * - Encryption set by… - Parameter in nova.conf - Admin establishing `encrypted volume type - `_, + `_, then user selecting encrypted volume - Not yet available - Shared File Systems service does not apply any additional encryption @@ -106,7 +106,7 @@ provided by OpenStack. a share was being created. In case of thin provisioning it can be partial space reservation (for more details see `Capabilities and Extra-Specs - `_ + `_ specification) .. note:: diff --git a/doc/arch-design-draft/source/design-storage/design-storage-object.rst b/doc/arch-design-draft/source/design-storage/design-storage-object.rst index 97aa7c9e46..6e5cfbeaa3 100644 --- a/doc/arch-design-draft/source/design-storage/design-storage-object.rst +++ b/doc/arch-design-draft/source/design-storage/design-storage-object.rst @@ -19,7 +19,7 @@ every level, at some point. Infrequently encountered failures that would hamstring other storage systems, such as issues taking down RAID cards or entire servers, are handled gracefully with OpenStack Object Storage. For more information, see the `Swift developer -documentation `_ +documentation `_ When designing your cluster, you must consider durability and availability which is dependent on the spread and placement of your data, diff --git a/doc/arch-design-draft/source/design-storage/design-storage-planning-scaling.rst b/doc/arch-design-draft/source/design-storage/design-storage-planning-scaling.rst index 0a3f39b8d1..5c2bf9ba4d 100644 --- a/doc/arch-design-draft/source/design-storage/design-storage-planning-scaling.rst +++ b/doc/arch-design-draft/source/design-storage/design-storage-planning-scaling.rst @@ -43,7 +43,7 @@ storage replication network between the two sites to support a single swift endpoint and a shared Object Storage capability between them. An example of this technique, as well as a configuration walk-through, is available at `Dedicated replication network -`_. +`_. Another option in this scenario is to build a dedicated set of tenant private networks across the secondary link, using overlay networks with a third party mapping the site overlays to each other. diff --git a/doc/arch-design-draft/source/high-availability.rst b/doc/arch-design-draft/source/high-availability.rst index 7f110dcc0d..e7d9b7ae2e 100644 --- a/doc/arch-design-draft/source/high-availability.rst +++ b/doc/arch-design-draft/source/high-availability.rst @@ -73,7 +73,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 @@ -140,7 +140,7 @@ connectivity. Some options include full mesh topology, hub spoke, spine leaf, and 3D Torus. For more information on high availability in OpenStack, see the `OpenStack High -Availability Guide `_. +Availability Guide `_. Site loss and recovery ~~~~~~~~~~~~~~~~~~~~~~ diff --git a/doc/arch-design-draft/source/overview-customer-requirements.rst b/doc/arch-design-draft/source/overview-customer-requirements.rst index 00cee2319f..db3e917569 100644 --- a/doc/arch-design-draft/source/overview-customer-requirements.rst +++ b/doc/arch-design-draft/source/overview-customer-requirements.rst @@ -299,7 +299,7 @@ useful in rolling back the changes if they affect production. For example, if all security group rules for a tenant disappeared, the ability to quickly track down the issue would be important for operational and legal reasons. For more details on auditing, see the `Compliance chapter -`_ in the OpenStack +`_ in the OpenStack Security Guide. Security diff --git a/doc/arch-design-draft/source/overview-operator-requirements.rst b/doc/arch-design-draft/source/overview-operator-requirements.rst index a259f81412..3a36176641 100644 --- a/doc/arch-design-draft/source/overview-operator-requirements.rst +++ b/doc/arch-design-draft/source/overview-operator-requirements.rst @@ -156,7 +156,7 @@ Reliability and availability For more information on managing and maintaining your OpenStack environment, see the -`Operations chapter `_ +`Operations chapter `_ in the OpenStack Operations Guide. Logging and monitoring @@ -178,7 +178,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. @@ -198,7 +198,7 @@ bandwidth. The inclusion of clustering software, such as Corosync or Pacemaker, is primarily determined by the availability of the cloud infrastructure and the complexity of supporting the configuration after it is deployed. The -`OpenStack High Availability Guide `_ +`OpenStack High Availability Guide `_ provides more details on the installation and configuration of Corosync and Pacemaker, should these packages need to be included in the design. @@ -265,7 +265,7 @@ Quota management Quotas are used to set operational limits to prevent system capacities from being exhausted without notification. For more information on managing quotas refer to the `Managing projects and users -chapter `__ +chapter `__ of the OpenStack Operations Guide. Policy management diff --git a/doc/arch-design-draft/source/overview-security-requirements.rst b/doc/arch-design-draft/source/overview-security-requirements.rst index d243f07b0a..448926158e 100644 --- a/doc/arch-design-draft/source/overview-security-requirements.rst +++ b/doc/arch-design-draft/source/overview-security-requirements.rst @@ -37,7 +37,7 @@ Consider the following security implications and requirements: clouds to explore authentication options. For more information OpenStack Security, see the `OpenStack Security -Guide `_. +Guide `_. Security domains ~~~~~~~~~~~~~~~~ diff --git a/doc/arch-design-draft/source/overview.rst b/doc/arch-design-draft/source/overview.rst index a32286f172..edf5df4978 100644 --- a/doc/arch-design-draft/source/overview.rst +++ b/doc/arch-design-draft/source/overview.rst @@ -11,7 +11,7 @@ Intended audience This book has been written for architects and designers of OpenStack clouds. For information about deploying and operating OpenStack, see the -`OpenStack Operations Guide `_. +`OpenStack Operations Guide `_. Before reading this book, we recommend: diff --git a/doc/arch-design/setup.cfg b/doc/arch-design/setup.cfg index 3cc38ba319..cdcc8fec9c 100644 --- a/doc/arch-design/setup.cfg +++ b/doc/arch-design/setup.cfg @@ -3,7 +3,7 @@ name = architecturedesignguide summary = OpenStack Architecture Design Guide author = OpenStack author-email = openstack-docs@lists.openstack.org -home-page = http://docs.openstack.org/ +home-page = https://docs.openstack.org/ classifier = Environment :: OpenStack Intended Audience :: Information Technology diff --git a/doc/arch-design/source/compute-focus-architecture.rst b/doc/arch-design/source/compute-focus-architecture.rst index 706684e177..1c11bc485c 100644 --- a/doc/arch-design/source/compute-focus-architecture.rst +++ b/doc/arch-design/source/compute-focus-architecture.rst @@ -165,7 +165,7 @@ Networking software OpenStack Networking provides a wide variety of networking services for instances. There are many additional networking software packages that might be useful to manage the OpenStack components themselves. The -`OpenStack High Availability Guide `_ +`OpenStack High Availability Guide `_ describes some of these software packages in more detail. For a compute-focused OpenStack cloud, the OpenStack infrastructure diff --git a/doc/arch-design/source/compute-focus-technical-considerations.rst b/doc/arch-design/source/compute-focus-technical-considerations.rst index a5d96daf42..53e3dcdd7e 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-architecture.rst b/doc/arch-design/source/generalpurpose-architecture.rst index 17132c6661..d7f3f9a1d5 100644 --- a/doc/arch-design/source/generalpurpose-architecture.rst +++ b/doc/arch-design/source/generalpurpose-architecture.rst @@ -428,7 +428,7 @@ examples include: Some of these software packages are described in more detail in the OpenStack High Availability Guide (refer to the `OpenStack network nodes -chapter `__ of +chapter `__ of the OpenStack High Availability Guide). For a general purpose OpenStack cloud, the OpenStack infrastructure @@ -449,7 +449,7 @@ including (or not including) these software packages is primarily determined by the availability of the cloud infrastructure and the complexity of supporting the configuration after it is deployed. The `OpenStack High Availability -Guide `__ provides more details on +Guide `__ provides more details on the installation and configuration of Corosync and Pacemaker, should these packages need to be included in the design. diff --git a/doc/arch-design/source/generalpurpose-operational-considerations.rst b/doc/arch-design/source/generalpurpose-operational-considerations.rst index ffbb380fd2..14bc64c432 100644 --- a/doc/arch-design/source/generalpurpose-operational-considerations.rst +++ b/doc/arch-design/source/generalpurpose-operational-considerations.rst @@ -121,4 +121,4 @@ installed in compute hosts, and adding capacity to the shared storage for additional ephemeral storage to instances, may be necessary. For a deeper discussion on many of these topics, refer to the `OpenStack -Operations Guide `_. +Operations Guide `_. diff --git a/doc/arch-design/source/generalpurpose-technical-considerations.rst b/doc/arch-design/source/generalpurpose-technical-considerations.rst index c09c37713c..11209dd68b 100644 --- a/doc/arch-design/source/generalpurpose-technical-considerations.rst +++ b/doc/arch-design/source/generalpurpose-technical-considerations.rst @@ -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 ` +`Networking deployment options table ` of OpenStack Operations Guide. Ensure your deployment has adequate back-up capabilities. @@ -540,7 +540,7 @@ level of guarantee to match service features. For more information on high availability in OpenStack, see the `OpenStack High Availability -Guide `_. +Guide `_. Security ~~~~~~~~ @@ -615,4 +615,4 @@ authentication tokens. For this reason, placing the API services behind hardware that performs SSL termination is strongly recommended. For more information OpenStack Security, see the `OpenStack Security -Guide `_. +Guide `_. diff --git a/doc/arch-design/source/introduction-intended-audience.rst b/doc/arch-design/source/introduction-intended-audience.rst index 3c0dc42dac..6779234c3a 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/legal-security-requirements.rst b/doc/arch-design/source/legal-security-requirements.rst index 602b82362e..f84a1409ff 100644 --- a/doc/arch-design/source/legal-security-requirements.rst +++ b/doc/arch-design/source/legal-security-requirements.rst @@ -164,7 +164,7 @@ offers private Cloud-as-a-Service. handles the organization's data or workloads. More information on OpenStack Security can be found in the -`OpenStack Security Guide `_. +`OpenStack Security Guide `_. Networking security ~~~~~~~~~~~~~~~~~~~ diff --git a/doc/arch-design/source/multi-site-operational-considerations.rst b/doc/arch-design/source/multi-site-operational-considerations.rst index a5d052dd21..df5385a36e 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/multi-site-technical-considerations.rst b/doc/arch-design/source/multi-site-technical-considerations.rst index 280b342e63..5554921319 100644 --- a/doc/arch-design/source/multi-site-technical-considerations.rst +++ b/doc/arch-design/source/multi-site-technical-considerations.rst @@ -23,7 +23,7 @@ storage replication network between the two sites to support a single Swift endpoint and a shared Object Storage capability between them. An example of this technique, as well as a configuration walk-through, is available at `Dedicated replication network -`_. +`_. Another option in this scenario is to build a dedicated set of project private networks across the secondary link, using overlay networks with a third party mapping the site overlays to each other. diff --git a/doc/arch-design/source/multi-site-user-requirements.rst b/doc/arch-design/source/multi-site-user-requirements.rst index df028ca1b1..9b5449e28d 100644 --- a/doc/arch-design/source/multi-site-user-requirements.rst +++ b/doc/arch-design/source/multi-site-user-requirements.rst @@ -55,7 +55,7 @@ should have minimal impact on the availability of the OpenStack services. The `OpenStack High Availability -Guide `_ contains more information +Guide `_ contains more information on how to provide redundancy for the OpenStack components. Multiple network links should be deployed between sites to provide diff --git a/doc/arch-design/source/references.rst b/doc/arch-design/source/references.rst index 5b668a80e1..f36642c010 100644 --- a/doc/arch-design/source/references.rst +++ b/doc/arch-design/source/references.rst @@ -19,7 +19,7 @@ techsupport/papers/ethernet_switch_reliability.pdf>`_ `_ : Requirements of the Financial Industry Regulatory Authority in the USA. -`Image Service property keys `_ : Glance API property keys allows the administrator to attach custom characteristics to images. @@ -28,7 +28,7 @@ characteristics to images. : Official LibGuestFS documentation. `Logging and Monitoring -`_ +`_ : Official OpenStack Operations documentation. `ManageIQ Cloud Management Platform `_ @@ -47,10 +47,10 @@ 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 `_ +`OpenStack High Availability Guide `_ : Information on how to provide redundancy for the OpenStack components. `OpenStack Hypervisor Support Matrix @@ -58,14 +58,14 @@ storage and data center hardware designs for scalable computing. : Matrix of supported hypervisors and capabilities when used with OpenStack. `OpenStack Object Store (Swift) Replication Reference -`_ +`_ : Developer documentation of Swift replication. -`OpenStack Operations Guide `_ +`OpenStack Operations Guide `_ : The OpenStack Operations Guide provides information on setting up and installing OpenStack. -`OpenStack Security Guide `_ +`OpenStack Security Guide `_ : The OpenStack Security Guide provides information on securing OpenStack deployments. diff --git a/doc/arch-design/source/specialized-hardware.rst b/doc/arch-design/source/specialized-hardware.rst index fde88ee552..68404a68d5 100644 --- a/doc/arch-design/source/specialized-hardware.rst +++ b/doc/arch-design/source/specialized-hardware.rst @@ -26,7 +26,7 @@ you can use Image service configuration options. For example, assign the cryptography chip to a device node in the guest. The OpenStack Command Line Reference contains further information on configuring this solution in the section `Image service property keys -`_. +`_. A challenge, however, is this option allows all guests using the configured images to access the hypervisor cryptography device. diff --git a/doc/arch-design/source/storage-focus-architecture.rst b/doc/arch-design/source/storage-focus-architecture.rst index 0bea91c8d6..1c2213dddf 100644 --- a/doc/arch-design/source/storage-focus-architecture.rst +++ b/doc/arch-design/source/storage-focus-architecture.rst @@ -360,7 +360,7 @@ themselves. Some examples include HAProxy, Keepalived, and various routing daemons (like Quagga). The OpenStack High Availability Guide describes some of these software packages, HAProxy in particular. See the `Network controller cluster stack -chapter `_ of +chapter `_ of the OpenStack High Availability Guide. Management software