Fixed heading levels in reference architecture

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

View File

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

View File

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

View File

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