openstack/openstack-manuals
Code Issues Proposed changes

Arch Design: Edits on massively_scalable

Browse Source 
Various minor edits to improve text and follow conventions.

Change-Id: If8b0753b24bd89d0b686f67768a5b596b5811313
This commit is contained in:
Andreas Jaeger 2014-07-31 22:35:13 +02:00
parent 2cb84e92af
commit 133885f97b
3 changed files with 27 additions and 19 deletions

5
doc/arch-design/massively_scalable/section_operational_considerations_massively_scalable.xml

@ -96,7 +96,8 @@
encouraging active participation in the mailing lists and
committees is a very important way to maintain skills and
forge relationships in the community. A list of OpenStack
training providers in the marketplace can be found here:
http://www.openstack.org/marketplace/training/.</para>
training providers in the marketplace can be found here: <link
xlink:href="http://www.openstack.org/marketplace/training/">http://www.openstack.org/marketplace/training/</link>.
</para>
</section>
</section>

14
doc/arch-design/massively_scalable/section_tech_considerations_massively_scalable.xml

@ -1,4 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE section [
<!ENTITY % openstack SYSTEM "../../common/entities/openstack.ent">
%openstack;
]>
<section xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink"
@ -74,7 +78,7 @@
normal filter scheduler then handles placement within the
cell.</para>
<para>The downside of using cells is that they are not well
supported by any of the OpenStack services other than compute.
supported by any of the OpenStack services other than Compute.
Also, they do not adequately support some relatively standard
OpenStack functionality such as security groups and host
aggregates. Due to their relative newness and specialized use,
@ -84,7 +88,7 @@
including those at CERN and Rackspace.</para></section>
<section xml:id="host-aggregates">
<title>Host aggregates</title>
<para>Host Aggregates enable partitioning of OpenStack Compute
<para>Host aggregates enable partitioning of OpenStack Compute
deployments into logical groups for load balancing and
instance distribution. Host aggregates may also be used to
further partition an availability zone. Consider a cloud which
@ -98,7 +102,7 @@
<section xml:id="availability-zones">
<title>Availability zones</title>
<para>Availability zones provide another mechanism for subdividing
an installation or region. They are, in effect, Host
an installation or region. They are, in effect, host
aggregates that are exposed for (optional) explicit targeting
by users.</para>
<para>Unlike cells, they do not have their own database server or
@ -106,7 +110,7 @@
compute nodes. Typically, grouping of nodes into availability
zones is based on a shared failure domain based on a physical
characteristic such as a shared power source, physical network
connection, and so on. Availability Zones are exposed to the
connection, and so on. Availability zones are exposed to the
user because they can be targeted; however, users are not
required to target them. An alternate approach is for the
operator to set a default availability zone to schedule
@ -119,7 +123,7 @@
the power layout of the data centers. A number of host
aggregates have also been defined to allow targeting of
virtual machine instances using flavors, that require special
capabilities shared by the target hosts such as SSDs, 10 G
capabilities shared by the target hosts such as SSDs, 10&nbsp;GbE
networks, or GPU cards.</para>
<mediaobject>
<imageobject>

27
doc/arch-design/massively_scalable/section_user_requirements_massively_scalable.xml

@ -39,13 +39,15 @@
in other locations for the same reason.</para>
</listitem>
</itemizedlist>
<para>Examples of such legal frameworks include the data
protection framework of the European Union
(http://ec.europa.eu/justice/data-protection/ ) and the
requirements of the Financial Industry Regulatory Authority
(http://www.finra.org/Industry/Regulation/FINRARules/ ) in the
United States. Consult a local regulatory body for more
information.</para>
<para>
Examples of such legal frameworks include the <link
xlink:href="http://ec.europa.eu/justice/data-protection/">data
protection framework</link> of the European Union and the
requirements of the <link
xlink:href="http://www.finra.org/Industry/Regulation/FINRARules/">Financial
Industry Regulatory Authority</link> in the United
States. Consult a local regulatory body for more information.
</para>
<section xml:id="user-requirements-massive-scale">
<title>User requirements</title>
<para>Massively scalable OpenStack clouds have the following user
@ -115,10 +117,11 @@
freely available open source software components to
reduce deployment costs and operational expenses.
Initiatives like OpenCompute (more information
available at http://www.opencompute.org) provide
additional information and pointers. To cut costs,
many operators sacrifice redundancy. For example,
redundant power supplies, redundant network
available at <link
xlink:href="http://www.opencompute.org">http://www.opencompute.org</link>)
provide additional information and pointers. To cut
costs, many operators sacrifice redundancy. For
example, redundant power supplies, redundant network
connections, and redundant rack switches.</para>
</listitem>
<listitem>
@ -159,7 +162,7 @@
consistency-availability; storage replication and
availability (both block and file/object storage); and
authentication, authorization, and auditing (AAA),
just to name a few. Refer to the "Multi-Site" section
just to name a few. Refer to the <xref linkend="multi_site"/>
for more details on requirements and considerations
for multi-site OpenStack clouds.</para>
</listitem>