openstack-manuals/doc/install-guide/section_compute-sys-requirements.xml
Diane Fleming 64b6c9261e Folder rename, file rename, flattening of directories
Current folder name	New folder name	        Book title
----------------------------------------------------------
basic-install 	        DELETE
cli-guide	        DELETE
common	                common
NEW	                admin-guide-cloud	Cloud Administrators Guide
docbkx-example	        DELETE
openstack-block-storage-admin 	DELETE
openstack-compute-admin 	DELETE
openstack-config 	config-reference	OpenStack Configuration Reference
openstack-ha 	        high-availability-guide	OpenStack High Availabilty Guide
openstack-image	        image-guide	OpenStack Virtual Machine Image Guide
openstack-install 	install-guide	OpenStack Installation Guide
openstack-network-connectivity-admin 	admin-guide-network 	OpenStack Networking Administration Guide
openstack-object-storage-admin 	DELETE
openstack-security 	security-guide	OpenStack Security Guide
openstack-training 	training-guide	OpenStack Training Guide
openstack-user 	        user-guide	OpenStack End User Guide
openstack-user-admin 	user-guide-admin	OpenStack Admin User Guide
glossary	        NEW        	OpenStack Glossary

bug: #1220407

Change-Id: Id5ffc774b966ba7b9a591743a877aa10ab3094c7
author: diane fleming
2013-09-08 15:15:50 -07:00

113 lines
5.8 KiB
XML
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?xml version="1.0" encoding="UTF-8"?>
<section xml:id="compute-system-requirements"
xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
<title>Compute and Image System Requirements</title>
<para><emphasis role="bold">Hardware</emphasis>: OpenStack
components are intended to run on standard hardware.
Recommended hardware configurations for a minimum
production deployment are as follows for the cloud
controller nodes and compute nodes for Compute and the
Image Service, and object, account, container, and proxy
servers for Object Storage.</para>
<table rules="all">
<caption>Hardware Recommendations</caption>
<col width="20%"/>
<col width="23%"/>
<col width="57%"/>
<thead>
<tr>
<td>Server</td>
<td>Recommended Hardware</td>
<td>Notes</td>
</tr>
</thead>
<tbody>
<tr>
<td>Cloud Controller node (runs network, volume, API, scheduler and image
services)</td>
<td>
<para>Processor: 64-bit x86</para>
<para>Memory: 12 GB RAM</para>
<para>Disk space: 30 GB (SATA, SAS or SSD)</para>
<para>Volume storage: two disks with 2 TB (SATA) for volumes attached to the
compute nodes</para>
<para>Network: one 1 Gbps Network Interface Card (NIC)</para>
</td>
<td>
<para>Two NICS are recommended but not required. A quad core server with 12
GB RAM would be more than sufficient for a cloud controller node.</para>
</td>
</tr>
<tr>
<td>Compute nodes (runs virtual instances)</td>
<td>
<para>Processor: 64-bit x86</para>
<para>Memory: 32 GB RAM</para>
<para>Disk space: 30 GB (SATA)</para>
<para>Network: two 1 Gbps NICs</para>
</td>
<td>
<para>With 2 GB RAM you can run one m1.small instance on a node or three
m1.tiny instances without memory swapping, so 2 GB RAM would be a
minimum for a test-environment compute node. As an example, Rackspace
Cloud Builders use 96 GB RAM for compute nodes in OpenStack
deployments.</para>
<para>Specifically for virtualization on certain hypervisors on the node or
nodes running <systemitem class="service">nova-compute</systemitem>, you need a x86 machine with an AMD processor
with SVM extensions (also called AMD-V) or an Intel processor with VT
(virtualization technology) extensions.</para>
<para>For XenServer and XCP refer to the <link
xlink:href="http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/installation.html#sys_requirements">
XenServer installation guide</link> and the <link
xlink:href="http://hcl.vmd.citrix.com/">
XenServer hardware compatibility list</link>.</para>
<para>For LXC, the VT extensions are not required.</para>
</td>
</tr>
</tbody>
</table>
<note>
<para>While certain parts of OpenStack are known to work on
various operating systems, currently the only
feature-complete, production-supported host environment is
64-bit Linux.</para></note>
<para><emphasis role="bold">Operating System</emphasis>: OpenStack
currently has packages for the following distributions:
CentOS, Debian, Fedora, RHEL, openSUSE, SLES, and Ubuntu. These packages are
maintained by community members, refer to <link
xlink:href="http://wiki.openstack.org/Packaging"
>http://wiki.openstack.org/Packaging</link> for additional
links. <note>
<para os="ubuntu">The Grizzly version is available on the
most recent LTS (Long Term Support) version which is
12.04 (Precise Pangolin), via the Ubuntu Cloud
Archive. At this time, there are not
packages available for 12.10. It is also available on
the current Ubuntu development series, which is 13.04
(Raring Ringtail).</para>
<para os="fedora">The Grizzly release of OpenStack Compute
requires Fedora 16 or later.</para>
<para os="opensuse">Packages for openSUSE are available in
the Open Build Service.</para>
</note></para>
<para><emphasis role="bold">Database</emphasis>: For
OpenStack Compute, you need access to either a PostgreSQL
or MySQL database, or you can install it as part of the
OpenStack Compute installation process.</para>
<para><emphasis role="bold">Permissions</emphasis>: You can
install OpenStack services either as root or as a user
with sudo permissions if you configure the sudoers file
to enable all the permissions.</para>
<para><emphasis role="bold">Network Time Protocol</emphasis>:
You must install a time synchronization program such as
NTP. For Compute, time synchronization avoids problems
when scheduling VM launches on compute
nodes. For Object Storage, time synchronization ensures the
object replications are accurately updating objects when
needed so that the freshest content is served.</para>
</section>