openstack/openstack-manuals
Code Issues Proposed changes

Merge "[install] unify list syntax"

Browse Source
This commit is contained in:
Jenkins 2015-10-15 09:33:35 +00:00 committed by Gerrit Code Review
commit ba7d6cf0d2
3 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/install-guide/source/environment-networking.rst
View File

@ -59,7 +59,7 @@ using :term:`NAT`.
The example architectures assume use of the following networks:
- Management on 10.0.0.0/24 with gateway 10.0.0.1
* Management on 10.0.0.0/24 with gateway 10.0.0.1
.. note::
@ -67,7 +67,7 @@ The example architectures assume use of the following networks:
nodes for administrative purposes such as package installation,
security updates, :term:`DNS`, and :term:`NTP`.
- Public on 203.0.113.0/24 with gateway 203.0.113.1
* Public on 203.0.113.0/24 with gateway 203.0.113.1
.. note::

8
doc/install-guide/source/environment.rst
View File

@ -29,9 +29,9 @@ not require a significant amount of resources and the following minimum
requirements should support a proof-of-concept environment with core services
and several :term:`CirrOS` instances:
- Controller Node: 1 processor, 2 GB memory, and 5 GB storage
* Controller Node: 1 processor, 2 GB memory, and 5 GB storage
- Compute Node: 1 processor, 2 GB memory, and 10 GB storage
* Compute Node: 1 processor, 2 GB memory, and 10 GB storage
To minimize clutter and provide more resources for OpenStack, we recommend
a minimal installation of your Linux distribution. Also, you must install a
@ -45,10 +45,10 @@ For first-time installation and testing purposes, many users elect to build
each host as a :term:`virtual machine (VM)`. The primary benefits of VMs
include the following:
- One physical server can support multiple nodes, each with almost any
* One physical server can support multiple nodes, each with almost any
number of network interfaces.
- Ability to take periodic "snap shots" throughout the installation
* Ability to take periodic "snap shots" throughout the installation
process and "roll back" to a working configuration in the event of a
problem.

10
doc/install-guide/source/overview.rst
View File

@ -94,13 +94,13 @@ After becoming familiar with basic installation, configuration, operation,
and troubleshooting of these OpenStack services, you should consider the
following steps toward deployment using a production architecture:
- Determine and implement the necessary core and optional services to
* Determine and implement the necessary core and optional services to
meet performance and redundancy requirements.
- Increase security using methods such as firewalls, encryption, and
* Increase security using methods such as firewalls, encryption, and
service policies.
- Implement a deployment tool such as Ansible, Chef, Puppet, or Salt
* Implement a deployment tool such as Ansible, Chef, Puppet, or Salt
to automate deployment and management of the production environment.
.. _overview-example-architectures:
@ -115,10 +115,10 @@ services such as Block Storage and Object Storage require additional nodes.
This example architecture differs from a minimal production architecture as
follows:
- Networking agents reside on the controller node instead of one or more
* Networking agents reside on the controller node instead of one or more
dedicated network nodes.
- Overlay (tunnel) traffic for private networks traverses the management
* Overlay (tunnel) traffic for private networks traverses the management
network instead of a dedicated network.
For more information on production architectures, see the