openstack/openstack-manuals
Code Issues Proposed changes

Merge "Removal of passive voice from chap 1, arch guide"

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