openstack/fuel-library
Code Issues Proposed changes

Fixed heading levels in reference architecture

Browse Source
This commit is contained in:
nickchase 2013-06-01 04:49:25 -04:00
parent efd98ddf73
commit c4dd3c0a2f
3 changed files with 12 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/pages/reference-architecture/0020-logical-setup.rst
View File

@ -1,12 +1,14 @@
Logical Setup
-------------
^^^^^^^^^^^^^
An OpenStack HA cluster involves, at a minimum, three types of nodes:
controller nodes, compute nodes, and storage nodes.
Controller Nodes
^^^^^^^^^^^^^^^^
++++++++++++++++
The first order of business in achieving high availability (HA) is
redundancy, so the first step is to provide multiple controller nodes.
You must keep in mind, however, that the database uses Galera to
@ -45,7 +47,7 @@ mechanism for achieving HA:
Compute Nodes
^^^^^^^^^^^^^
+++++++++++++
OpenStack compute nodes are, in many ways, the foundation of your
cluster; they are the servers on which your users will create their
@ -60,7 +62,7 @@ controller nodes using the VIP and going through HAProxy.
Storage Nodes
^^^^^^^^^^^^^
+++++++++++++
In this OpenStack cluster reference architecture, shared storage acts

2
docs/pages/reference-architecture/0030-cluster-sizing.rst
View File

@ -1,6 +1,6 @@
Cluster Sizing
--------------
^^^^^^^^^^^^^^
This reference architecture is well suited for production-grade
OpenStack deployments on a medium and large scale when you can afford

9
docs/pages/reference-architecture/0040-network-setup.rst
View File

@ -1,6 +1,6 @@
Network Architecture
--------------------
^^^^^^^^^^^^^^^^^^^^
The current architecture assumes the presence of 3 NIC cards in
@ -26,7 +26,8 @@ cluster.
Public Network
^^^^^^^^^^^^^^
++++++++++++++
This network allows inbound connections to VMs from the outside world
(allowing users to connect to VMs from the Internet). It also allows
outbound connections from VMs to the outside world.
@ -61,7 +62,7 @@ The public network also provides VIPs for Endpoint nodes, which are
used to connect to OpenStack services APIs.
Internal (Management) Network
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+++++++++++++++++++++++++++++
The internal network connects all OpenStack nodes in the cluster. All
components of an OpenStack cluster communicate with each other using
@ -80,7 +81,7 @@ non-globally routed IP address range.
Private Network
^^^^^^^^^^^^^^^
+++++++++++++++
The private network facilitates communication between each tenant's
VMs. Private network address spaces are part of the enterprise network