openstack/openstack-manuals
Code Issues Proposed changes

[arch-design] use https instead of http for docs.o.o

Browse Source 
Change-Id: I130acc6e045e76d479b2d2bccdd50f2a377a6afb
This commit is contained in:
KATO Tomoyuki 2017-01-27 22:59:24 +09:00
parent 84a6622b46
commit 6073a8b3e5
32 changed files with 52 additions and 52 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/arch-design-draft/setup.cfg
View File

@ -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

8
doc/arch-design-draft/source/capacity-planning-scaling.rst
View File

@ -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>`_.
<https://docs.openstack.org/ops-guide/ops-logging-monitoring.html>`_.
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
<http://docs.openstack.org/developer/horizon/topics/deployment.html#session-storage>`_.
<https://docs.openstack.org/developer/horizon/topics/deployment.html#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
<http://docs.openstack.org/ops-guide/operations.html>`_ in the Operations
<https://docs.openstack.org/ops-guide/operations.html>`_ 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
<http://docs.openstack.org/ops-guide/ops-logging-monitoring.html>`_
<https://docs.openstack.org/ops-guide/ops-logging-monitoring.html>`_
chapte in the Operations Guide details some useful metrics.
Burn-in Testing

2
doc/arch-design-draft/source/design-compute/design-compute-cpu.rst
View File

@ -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 <http://docs.openstack.org/admin-guide/compute-cpu-topologies.html>`_.
Guide <https://docs.openstack.org/admin-guide/compute-cpu-topologies.html>`_.
In order to take advantage of these new enhancements in OpenStack nova, Compute
hosts must be using NUMA capable CPUs.

2
doc/arch-design-draft/source/design-compute/design-compute-hardware.rst
View File

@ -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
<http://docs.openstack.org/draft/arch-design-draft/design-networking.html>`_
<https://docs.openstack.org/draft/arch-design-draft/design-networking.html>`_
of this chapter.

4
doc/arch-design-draft/source/design-compute/design-compute-hypervisor.rst
View File

@ -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
<http://docs.openstack.org/developer/nova/support-matrix.html>`_
<https://docs.openstack.org/developer/nova/support-matrix.html>`_
and in the `configuration reference
<http://docs.openstack.org/mitaka/config-reference/compute/hypervisors.html>`_.
<https://docs.openstack.org/mitaka/config-reference/compute/hypervisors.html>`_.
.. note::

2
doc/arch-design-draft/source/design-compute/design-compute-networking.rst
View File

@ -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) <http://docs.openstack.org/mitaka/networking-guide/scenario-dvr-ovs.html>`_
High Availability using Distributed Virtual Routing (DVR) <https://docs.openstack.org/mitaka/networking-guide/scenario-dvr-ovs.html>`_

2
doc/arch-design-draft/source/design-compute/design-compute-overcommit.rst
View File

@ -50,7 +50,7 @@ Logging
~~~~~~~
Logging is described in more detail in `Logging and Monitoring
<http://docs.openstack.org/ops-guide/ops-logging-monitoring.html>`_. However,
<https://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.

2
doc/arch-design-draft/source/design-control-plane.rst
View File

@ -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
<http://docs.openstack.org/ops-guide/ops-projects-users.html>`_ in the
<https://docs.openstack.org/ops-guide/ops-projects-users.html>`_ in the
OpenStack Operations Guide.
OpenStack Identity supports different plug-ins for authentication

2
doc/arch-design-draft/source/design-networking.rst
View File

@ -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 <http://docs.openstack.org/sec/>`_ for tips
See the `OpenStack Security Guide <https://docs.openstack.org/sec/>`_ for tips
on securing your network.
Networking (neutron)

2
doc/arch-design-draft/source/design-networking/design-networking-design.rst
View File

@ -286,7 +286,7 @@ examples include:
* Routing daemons
Some of these software packages are described in more detail in the
`OpenStack network nodes chapter <http://docs.openstack.org/ha-guide/networking-ha.html>`_
`OpenStack network nodes chapter <https://docs.openstack.org/ha-guide/networking-ha.html>`_
in the OpenStack High Availability Guide.
For a general purpose OpenStack cloud, the OpenStack infrastructure

4
doc/arch-design-draft/source/design-storage/design-storage-concepts.rst
View File

@ -93,7 +93,7 @@ provided by OpenStack.
* - Encryption set by…
- Parameter in nova.conf
- Admin establishing `encrypted volume type
<http://docs.openstack.org/admin-guide/dashboard_manage_volumes.html>`_,
<https://docs.openstack.org/admin-guide/dashboard_manage_volumes.html>`_,
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
<http://docs.openstack.org/developer/manila/devref/capabilities_and_extra_specs.html?highlight=extra%20specs#common-capabilities>`_
<https://docs.openstack.org/developer/manila/devref/capabilities_and_extra_specs.html?highlight=extra%20specs#common-capabilities>`_
specification)
.. note::

2
doc/arch-design-draft/source/design-storage/design-storage-object.rst
View File

@ -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 <http://docs.openstack.org/developer/swift/overview_architecture.html>`_
documentation <https://docs.openstack.org/developer/swift/overview_architecture.html>`_
When designing your cluster, you must consider durability and
availability which is dependent on the spread and placement of your data,

2
doc/arch-design-draft/source/design-storage/design-storage-planning-scaling.rst
View File

@ -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
<http://docs.openstack.org/developer/swift/replication_network.html#dedicated-replication-network>`_.
<https://docs.openstack.org/developer/swift/replication_network.html#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.

4
doc/arch-design-draft/source/high-availability.rst
View File

@ -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
<http://docs.openstack.org/ops-guide/arch_network_design.html#network-topology>`_.
<https://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
@ -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 <http://docs.openstack.org/ha-guide/>`_.
Availability Guide <https://docs.openstack.org/ha-guide/>`_.
Site loss and recovery
~~~~~~~~~~~~~~~~~~~~~~

2
doc/arch-design-draft/source/overview-customer-requirements.rst
View File

@ -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
<http://docs.openstack.org/security-guide/compliance.html>`_ in the OpenStack
<https://docs.openstack.org/security-guide/compliance.html>`_ in the OpenStack
Security Guide.
Security

8
doc/arch-design-draft/source/overview-operator-requirements.rst
View File

@ -156,7 +156,7 @@ Reliability and availability
For more information on
managing and maintaining your OpenStack environment, see the
`Operations chapter <http://docs.openstack.org/ops-guide/operations.html>`_
`Operations chapter <https://docs.openstack.org/ops-guide/operations.html>`_
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
<http://docs.openstack.org/ops-guide/ops-logging-monitoring.html>`__ of
<https://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.
@ -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 <http://docs.openstack.org/ha-guide/>`_
`OpenStack High Availability Guide <https://docs.openstack.org/ha-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 <http://docs.openstack.org/ops-guide/ops-projects-users.html>`__
chapter <https://docs.openstack.org/ops-guide/ops-projects-users.html>`__
of the OpenStack Operations Guide.
Policy management

2
doc/arch-design-draft/source/overview-security-requirements.rst
View File

@ -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 <http://docs.openstack.org/security-guide/>`_.
Guide <https://docs.openstack.org/security-guide/>`_.
Security domains
~~~~~~~~~~~~~~~~

2
doc/arch-design-draft/source/overview.rst
View File

@ -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 <http://docs.openstack.org/ops-guide/>`_.
`OpenStack Operations Guide <https://docs.openstack.org/ops-guide/>`_.
Before reading this book, we recommend:

2
doc/arch-design/setup.cfg
View File

@ -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

2
doc/arch-design/source/compute-focus-architecture.rst
View File

@ -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 <http://docs.openstack.org/ha-guide/>`_
`OpenStack High Availability Guide <https://docs.openstack.org/ha-guide/>`_
describes some of these software packages in more detail.
For a compute-focused OpenStack cloud, the OpenStack infrastructure

2
doc/arch-design/source/compute-focus-technical-considerations.rst
View File

@ -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 <https://docs.openstack.org/ops-guide/ops-user-facing-operations.html#flavors>`_.
OpenStack components
~~~~~~~~~~~~~~~~~~~~

4
doc/arch-design/source/generalpurpose-architecture.rst
View File

@ -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 <http://docs.openstack.org/ha-guide/networking-ha.html>`__ of
chapter <https://docs.openstack.org/ha-guide/networking-ha.html>`__ 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 <http://docs.openstack.org/ha-guide/>`__ provides more details on
Guide <https://docs.openstack.org/ha-guide/>`__ provides more details on
the installation and configuration of Corosync and Pacemaker, should
these packages need to be included in the design.

2
doc/arch-design/source/generalpurpose-operational-considerations.rst
View File

@ -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 <http://docs.openstack.org/ops>`_.
Operations Guide <https://docs.openstack.org/ops>`_.

6
doc/arch-design/source/generalpurpose-technical-considerations.rst
View File

@ -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 <https://docs.openstack.org/ops-guide/arch-network-design.html#network-topology>`
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 <http://docs.openstack.org/ha-guide/>`_.
Guide <https://docs.openstack.org/ha-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 <http://docs.openstack.org/security-guide/>`_.
Guide <https://docs.openstack.org/security-guide/>`_.

2
doc/arch-design/source/introduction-intended-audience.rst
View File

@ -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/ops-guide/>`_.
to the `OpenStack Operations Guide <https://docs.openstack.org/ops-guide/>`_.
Before reading this book, we recommend prior knowledge of cloud
architecture and principles, experience in enterprise system design,

2
doc/arch-design/source/legal-security-requirements.rst
View File

@ -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 <http://docs.openstack.org/security-guide>`_.
`OpenStack Security Guide <https://docs.openstack.org/security-guide>`_.
Networking security
~~~~~~~~~~~~~~~~~~~

6
doc/arch-design/source/multi-site-operational-considerations.rst
View File

@ -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 <https://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 <https://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 <https://docs.openstack.org/ops-guide/ops-projects-users.html>`__
of the OpenStack Operators Guide.
Policy management

2
doc/arch-design/source/multi-site-technical-considerations.rst
View File

@ -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
<http://docs.openstack.org/developer/swift/replication_network.html#dedicated-replication-network>`_.
<https://docs.openstack.org/developer/swift/replication_network.html#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.

2
doc/arch-design/source/multi-site-user-requirements.rst
View File

@ -55,7 +55,7 @@ should have minimal impact on the availability of the OpenStack
services.
The `OpenStack High Availability
Guide <http://docs.openstack.org/ha-guide/>`_ contains more information
Guide <https://docs.openstack.org/ha-guide/>`_ contains more information
on how to provide redundancy for the OpenStack components.
Multiple network links should be deployed between sites to provide

14
doc/arch-design/source/references.rst
View File

@ -19,7 +19,7 @@ techsupport/papers/ethernet_switch_reliability.pdf>`_
<http://www.finra.org/Industry/Regulation/FINRARules/>`_
: Requirements of the Financial Industry Regulatory Authority in the USA.
`Image Service property keys <http://docs.openstack.org/
`Image Service property keys <https://docs.openstack.org/
cli-reference/glance.html#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
<http://docs.openstack.org/ops-guide/ops-logging-monitoring.html>`_
<https://docs.openstack.org/ops-guide/ops-logging-monitoring.html>`_
: Official OpenStack Operations documentation.
`ManageIQ Cloud Management Platform <http://manageiq.org/>`_
@ -47,10 +47,10 @@ 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>`_
<https://docs.openstack.org/ops-guide/ops-user-facing-operations.html#flavors>`_
: Official OpenStack documentation.
`OpenStack High Availability Guide <http://docs.openstack.org/ha-guide/>`_
`OpenStack High Availability Guide <https://docs.openstack.org/ha-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
<http://docs.openstack.org/developer/swift/replication_network.html>`_
<https://docs.openstack.org/developer/swift/replication_network.html>`_
: Developer documentation of Swift replication.
`OpenStack Operations Guide <http://docs.openstack.org/ops-guide/>`_
`OpenStack Operations Guide <https://docs.openstack.org/ops-guide/>`_
: The OpenStack Operations Guide provides information on setting up
and installing OpenStack.
`OpenStack Security Guide <http://docs.openstack.org/security-guide/>`_
`OpenStack Security Guide <https://docs.openstack.org/security-guide/>`_
: The OpenStack Security Guide provides information on securing
OpenStack deployments.

2
doc/arch-design/source/specialized-hardware.rst
View File

@ -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
<http://docs.openstack.org/cli-reference/glance.html#image-service-property-keys>`_.
<https://docs.openstack.org/cli-reference/glance.html#image-service-property-keys>`_.
A challenge, however, is this option allows all guests using the
configured images to access the hypervisor cryptography device.

2
doc/arch-design/source/storage-focus-architecture.rst
View File

@ -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 <http://docs.openstack.org/ha-guide/networking-ha.html>`_ of
chapter <https://docs.openstack.org/ha-guide/networking-ha.html>`_ of
the OpenStack High Availability Guide.
Management software