From 4ba904a12b7895ef4aa554b204586c12b01cad5f Mon Sep 17 00:00:00 2001 From: Christian Berendt Date: Sat, 10 Oct 2015 18:45:35 +0200 Subject: [PATCH] [install] unify list syntax * use * instead of - everywhere Change-Id: I4c28e2856e944bd355a6edccdb6481c4b42aaf29 --- doc/install-guide/source/environment-networking.rst | 4 ++-- doc/install-guide/source/environment.rst | 8 ++++---- doc/install-guide/source/overview.rst | 10 +++++----- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/doc/install-guide/source/environment-networking.rst b/doc/install-guide/source/environment-networking.rst index 4474c12e33..83cf651dbd 100644 --- a/doc/install-guide/source/environment-networking.rst +++ b/doc/install-guide/source/environment-networking.rst @@ -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:: diff --git a/doc/install-guide/source/environment.rst b/doc/install-guide/source/environment.rst index 5b5e5f2220..f39be20c0e 100644 --- a/doc/install-guide/source/environment.rst +++ b/doc/install-guide/source/environment.rst @@ -36,9 +36,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 @@ -52,10 +52,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. diff --git a/doc/install-guide/source/overview.rst b/doc/install-guide/source/overview.rst index 93435ed2e9..73d5f94baa 100644 --- a/doc/install-guide/source/overview.rst +++ b/doc/install-guide/source/overview.rst @@ -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