openstack/openstack-manuals
Code Issues Proposed changes

Removal of passive voice from chap 1, arch guide

Browse Source 
Removal of passive voice from ch_generalpurpose

Change-Id: I09379f5cdf90ef8ccfa88468b961b10a966c9412
Partial-bug: #1400550
This commit is contained in:
Alexandra Settle 2014-12-09 13:05:35 +10:00
parent 7d65f1efc0
commit 2b3659ab77
1 changed files with 49 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

75
doc/arch-design/ch_generalpurpose.xml
View File

@ -5,33 +5,56 @@
version="5.0" version="5.0"
xml:id="generalpurpose"> xml:id="generalpurpose">
<title>General purpose</title> <title>General purpose</title>
<para>An OpenStack general purpose cloud is often considered a <para>An OpenStack general purpose cloud is often considered a
starting point for building a cloud deployment. General starting point for building a cloud deployment. They are designed
purpose clouds, by their nature, balance the components and do to balance the components and do not emphasize any particular aspect
not emphasize (or heavily emphasize) any particular aspect of of the overall computing environment.
the overall computing environment. The expectation is that the Cloud design must give equal weight to the compute, network, and
compute, network, and storage components will be given equal storage components. General purpose clouds are
weight in the design. General purpose clouds can be found in found in private, public, and hybrid environments, lending
private, public, and hybrid environments. They lend themselves themselves to many different use cases.
to many different use cases but, since they are homogeneous </para>
deployments, they are not suited to specialized environments <note>
or edge case situations. Common uses to consider for a general <para>
purpose cloud could be, but are not limited to, providing a General purpose clouds are homogeneous deployments and are
simple database, a web application runtime environment, a not suited to specialized environments or edge case situations.
shared application development platform, or lab test bed. In </para>
other words, any use case that would benefit from a scale-out </note>
rather than a scale-up approach is a good candidate for a <para>
general purpose cloud architecture.</para> Common uses of a general purpose cloud include:
<para>A general purpose cloud, by definition, is something that is </para>
designed to have a range of potential uses or functions; not <itemizedlist>
specialized for a specific use. General purpose architecture <listitem>
is largely considered a scenario that would address 80% of the <para>
potential use cases. The infrastructure, in itself, is a Providing a simple database
specific use case. It is also a good place to start the design </para>
process. As the most basic cloud service model, general </listitem>
purpose clouds are designed to be platforms suited for general <listitem>
purpose applications.</para> <para>
A web application runtime environment
</para>
</listitem>
<listitem>
<para>
A shared application development platform
</para>
</listitem>
<listitem>
<para>
Lab test bed
</para>
</listitem>
</itemizedlist>
<para>Use cases that benefit from scale-out rather than scale-up approaches
are good candidates for general purpose cloud architecture.
</para>
<para>A general purpose cloud is designed to have a range of potential
uses or functions; not specialized for specific use cases. General
purpose architecture is designed to address 80% of potential use
cases available. The infrastructure, in itself, is a specific use case,
enabling it to be used as a base model for the design process.
General purpose clouds are designed to be platforms that are suited
for general purpose applications.</para>
<para>General purpose clouds are limited to the most basic <para>General purpose clouds are limited to the most basic
components, but they can include additional resources such components, but they can include additional resources such
as:</para> as:</para>