openstack/training-guides
Code Issues Proposed changes

Merge "changes to section_basics-prerequisites"

Browse Source
This commit is contained in:
Jenkins 2014-08-26 21:42:09 +00:00 committed by Gerrit Code Review
commit 5aa6dbaed9
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/training-guides/basic-install-guide/section_basics-prerequisites.xml
View File

@ -6,7 +6,7 @@
xml:id="basics-prerequisites">
<?dbhtml stop-chunking?>
<title>Before you begin</title>
<para>For a functional environment, OpenStack doesn't require a
<para>For a functional environment, OpenStack does not require a
significant amount of resources. We recommend that your environment meets
or exceeds the following minimum requirements which can support several
minimal <glossterm>CirrOS</glossterm> instances:</para>
@ -28,7 +28,7 @@
recommend a minimal installation of your Linux distribution. Also, we
strongly recommend that you install a 64-bit version of your distribution
on at least the compute node. If you install a 32-bit version of your
distribution on the compute node, attempting to start an instance using
distribution on the compute node, starting an instance using
a 64-bit image will fail.</para>
<note>
<para>A single disk partition on each node works for most basic
@ -38,20 +38,20 @@
</note>
<para>Many users build their test environments on
<glossterm baseform="virtual machine (VM)">virtual machines
(VMs)</glossterm>. The primary benefits of VMs include the
(VMs)</glossterm>. The primary benefits of this method include the
following:</para>
<itemizedlist>
<listitem>
<para>One physical server can support multiple nodes, each with almost
<para>One physical server can support multiple nodes with almost
any number of network interfaces.</para>
</listitem>
<listitem>
<para>Ability to take periodic "snap shots" throughout the installation
<para>The ability to take periodic "snapshots" throughout the installation
process and "roll back" to a working configuration in the event of
a problem.</para>
</listitem>
</itemizedlist>
<para>However, VMs will reduce performance of your instances, particularly
<para>VMs can result in slow instances, particularly
if your hypervisor and/or processor lacks support for hardware
acceleration of nested VMs.</para>
<note>