openstack/fuel-docs
Code Issues Proposed changes

Reviewed install guide and corrected errors

Browse Source
This commit is contained in:
manashkin 2013-10-21 19:51:10 +04:00
parent 6f0a11f1a5
commit 524e86a4e1
6 changed files with 16 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
pages/frequently-asked-questions/0080-other-questions.rst
View File

@ -15,6 +15,9 @@ Other Questions
provide a plain vanilla distribution. Put simply, there is no vendor lock-in
with Fuel. For your convenience, we maintain repositories containing a
history of OpenStack packages certified to work with our Puppet manifests.
Additionally, we keep updated or customized versions of some Linux
components, of those we know their particular versions has blocker issues,
preventing some OpenStack components from normal operation.
The advantage of this approach is that you can install any OpenStack version
you want (with possible custom big fixes). Even if you are running Essex,

2
pages/install-guide/0010-prerequisites.rst
View File

@ -85,7 +85,7 @@ Round the number of sockets to an even number to get 12 sockets. Use the followi
12 / 2 = 6
Therefore, you need 6 dual core servers.
Therefore, you need 6 dual socket servers.
You can calculate the number of virtual machines per server using the following formula::
number of virtual machines / number of servers

2
pages/install-guide/0015-sizing-hardware.rst
View File

@ -51,7 +51,7 @@ least 5 CPU cores (16 GHz/(2.4 GHz per core * 1.3 to adjust for hyper-threading)
per machine, and at least 84 CPU cores ((100 VMs * 2 GHz per VM)/2.4 GHz per
core) in total. If you were to select the Intel E5 2650-70 8 core CPU, that
means you need 11 sockets (84 cores / 8 cores per socket). This breaks down to
six dual core servers (12 sockets / 2 sockets per server), for a "packing
six dual socket servers (12 sockets / 2 sockets per server), for a "packing
density" of 17 VMs per server (102 VMs / 6 servers).
This process also accommodates growth since you now know what a single server

8
pages/install-guide/0050-supported-software.rst
View File

@ -16,6 +16,8 @@ components:
* RHEL 6.4 (x86_64 architecture only)
* Ubuntu Server 12.04 LTS (x86_64 architecture only)
* Puppet (IT automation tool)
* 2.7.19
@ -30,7 +32,9 @@ components:
* OpenStack
* Grizzly release 2013.1.2
* Grizzly release 2013.1.3 (for Centos and Ubuntu)
* RedHat OpenStack 3.0 Grizzly 2013.1.2 for RHEL
* Hypervisor
@ -56,7 +60,7 @@ components:
* RabbitMQ
* 2.8.7
* 2.8.7 with mirrored queue patch
* Pacemaker

7
pages/install-guide/0060-understand-the-manifest.rst
View File

@ -34,10 +34,9 @@ Deploy
Deployment is done using Astute orchestrator, which parses ``nodes`` and
``attributes`` sections and recalculates parameters needed for deployment.
Calculated parameters are passed to the nodes being deployed by use of
``nailyfact`` MCollective agent that uploads these attributes to
``/etc/naily.facts`` file of the node. Then puppet parses this file using
Facter plugin and uploads these facts into puppet. These facts are used
during catalog compilation phase by puppet master. Finally catalog is executed
astute.yaml file. Then puppet parses this file using
Facter plugin and uploads the node settings into puppet. These settings are used
during catalog compilation phase by puppet. Finally catalog is executed
and Astute orchestrator passes to the next node in deployment sequence.
.. raw:: pdf

4
pages/install-guide/install.rst
View File

@ -149,7 +149,7 @@ First, create the Master node VM.
* OS Type: Linux
* Version: Red Hat (64bit)
* RAM: 1024+ MB
* RAM: 2048+ MB
* HDD: 50 GB with dynamic disk expansion
3. Modify your VM settings:
@ -170,7 +170,7 @@ Next, create Slave nodes where OpenStack needs to be installed.
1. Create 3 or 4 additional VMs depending on your wish with the following parameters:
* OS Type: Linux, Version: Red Hat (64bit)
* RAM: 1024+ MB
* RAM: 2048+ MB
* HDD: 30 GB, with dynamic disk expansion
* Network 1: host-only interface vboxnet0, PCnet-FAST III device