Restructured all general topics
This commit is contained in:
parent
0d36a2aab4
commit
cd2bbfe1c9
@ -1,5 +1,3 @@
|
|||||||
.. index:: Introduction
|
|
||||||
|
|
||||||
==================================
|
==================================
|
||||||
Introduction to Fuel for OpenStack
|
Introduction to Fuel for OpenStack
|
||||||
==================================
|
==================================
|
2
conf.py
2
conf.py
@ -74,7 +74,7 @@ release = '3.1'
|
|||||||
|
|
||||||
# List of patterns, relative to source directory, that match files and
|
# List of patterns, relative to source directory, that match files and
|
||||||
# directories to ignore when looking for source files.
|
# directories to ignore when looking for source files.
|
||||||
exclude_patterns = ['_build']
|
exclude_patterns = ['_*', "pages"]
|
||||||
|
|
||||||
# The reST default role (used for this markup: `text`) to use for all documents.
|
# The reST default role (used for this markup: `text`) to use for all documents.
|
||||||
#default_role = None
|
#default_role = None
|
||||||
|
16
contents.rst
16
contents.rst
@ -10,12 +10,12 @@ Table of Contents
|
|||||||
:maxdepth: 2
|
:maxdepth: 2
|
||||||
|
|
||||||
index
|
index
|
||||||
pages/0010-package-contents
|
0010-package-contents
|
||||||
pages/0020-about-fuel
|
0020-about-fuel
|
||||||
pages/0030-release-notes
|
0030-release-notes
|
||||||
pages/0040-reference-architecture
|
0040-reference-architecture
|
||||||
pages/0045-installation-fuel-ui
|
0045-installation-fuel-ui
|
||||||
pages/0050-installation-fuel-cli
|
0050-installation-fuel-cli
|
||||||
pages/0055-production-considerations
|
0055-production-considerations
|
||||||
pages/0060-frequently-asked-questions
|
0060-frequently-asked-questions
|
||||||
copyright
|
copyright
|
||||||
|
@ -12,14 +12,14 @@ its constituent components are tailored to one or more common cloud use cases.
|
|||||||
Fuel provides the ability to create the following cluster types without requiring
|
Fuel provides the ability to create the following cluster types without requiring
|
||||||
extensive customization:
|
extensive customization:
|
||||||
|
|
||||||
.. index:: Deployment Configurations, Single node
|
.. index:: Deployment Configurations; Single node
|
||||||
|
|
||||||
**Single node**: Perfect for getting a feel for how OpenStack works, the
|
**Single node**: Perfect for getting a feel for how OpenStack works, the
|
||||||
Single-node installation is the simplest way to get OpenStack up and running.
|
Single-node installation is the simplest way to get OpenStack up and running.
|
||||||
The Single-node installation provides an easy way to install an entire OpenStack
|
The Single-node installation provides an easy way to install an entire OpenStack
|
||||||
cluster on a single physical server system or in a virtual machine environment.
|
cluster on a single physical server system or in a virtual machine environment.
|
||||||
|
|
||||||
.. index:: Deployment Configurations, Multi-node (non-HA)
|
.. index:: Deployment Configurations; Multi-node (non-HA)
|
||||||
|
|
||||||
**Multi-node (non-HA)**: The Multi-node (non-HA) installation enables you to try
|
**Multi-node (non-HA)**: The Multi-node (non-HA) installation enables you to try
|
||||||
out additional OpenStack services like Cinder, Neutron (formerly Quantum), and
|
out additional OpenStack services like Cinder, Neutron (formerly Quantum), and
|
||||||
@ -27,18 +27,18 @@ Swift without requiring the degree of increased hardware involved in ensuring
|
|||||||
high availability. In addition to the ability to independently specify which
|
high availability. In addition to the ability to independently specify which
|
||||||
services to activate, you also have the following options:
|
services to activate, you also have the following options:
|
||||||
|
|
||||||
.. index:: Deployment Configurations, Compact Swift non-HA
|
.. index:: Deployment Configurations; Compact Swift non-HA
|
||||||
|
|
||||||
**Compact Swift**: When you choose this option, Swift will be installed on
|
**Compact Swift**: When you choose this option, Swift will be installed on
|
||||||
your controllers, reducing your hardware requirements by eliminating the need
|
your controllers, reducing your hardware requirements by eliminating the need
|
||||||
for additional Swift servers.
|
for additional Swift servers.
|
||||||
|
|
||||||
.. index:: Deployment Configurations, Standalone Swift non-HA
|
.. index:: Deployment Configurations; Standalone Swift non-HA
|
||||||
|
|
||||||
**Standalone Swift**: This option enables you to install independant Swift
|
**Standalone Swift**: This option enables you to install independant Swift
|
||||||
nodes, so that you can separate their operation from your controller nodes.
|
nodes, so that you can separate their operation from your controller nodes.
|
||||||
|
|
||||||
.. index:: Deployment Configurations, Multi-node (HA)
|
.. index:: Deployment Configurations; Multi-node (HA)
|
||||||
|
|
||||||
**Multi-node (HA)**: When you're ready to begin your move to production, the
|
**Multi-node (HA)**: When you're ready to begin your move to production, the
|
||||||
Multi-node (HA) configuration is a straightforward way to create an OpenStack
|
Multi-node (HA) configuration is a straightforward way to create an OpenStack
|
||||||
@ -46,19 +46,19 @@ cluster that provides high availability. With three controller nodes and the
|
|||||||
ability to individually specify services such as Cinder, Neutron, and Swift,
|
ability to individually specify services such as Cinder, Neutron, and Swift,
|
||||||
Fuel provides the following variations of the Multi-node (HA) configuration:
|
Fuel provides the following variations of the Multi-node (HA) configuration:
|
||||||
|
|
||||||
.. index:: Deployment Configurations, Compact Swift HA
|
.. index:: Deployment Configurations; Compact Swift HA
|
||||||
|
|
||||||
**Compact Swift**: When you choose this option, Swift will be installed on
|
**Compact Swift**: When you choose this option, Swift will be installed on
|
||||||
your controllers, reducing your hardware requirements by eliminating the need
|
your controllers, reducing your hardware requirements by eliminating the need
|
||||||
for additional Swift servers while still addressing high availability
|
for additional Swift servers while still addressing high availability
|
||||||
requirements.
|
requirements.
|
||||||
|
|
||||||
.. index:: Deployment Configurations, Standalone Swift HA
|
.. index:: Deployment Configurations; Standalone Swift HA
|
||||||
|
|
||||||
**Standalone Swift**: This option enables you to install independant Swift
|
**Standalone Swift**: This option enables you to install independant Swift
|
||||||
nodes, so that you can separate their operation from your controller nodes.
|
nodes, so that you can separate their operation from your controller nodes.
|
||||||
|
|
||||||
.. index:: Deployment Configurations, Compact Neutron HA
|
.. index:: Deployment Configurations; Compact Neutron HA
|
||||||
|
|
||||||
**Compact Neutron**: If you don't need the flexibility of a separate Neutron
|
**Compact Neutron**: If you don't need the flexibility of a separate Neutron
|
||||||
node, Fuel provides the option to combine your Neutron node with one of your
|
node, Fuel provides the option to combine your Neutron node with one of your
|
||||||
|
Loading…
Reference in New Issue
Block a user