From 86d3d9eaccedfb7ca38bae1044bd5a61aa089051 Mon Sep 17 00:00:00 2001
From: Baptiste Assmann <bedis9@gmail.com>
Date: Wed, 12 Nov 2014 19:31:00 +0100
Subject: [PATCH] rst typos

In RST, bullet lists must be preceded by a blank line, otherwise it is
not processed properly.
---
 HACKING.rst |  2 ++
 ROADMAP.rst | 39 ++++++++++++++++++++++++++-------------
 2 files changed, 28 insertions(+), 13 deletions(-)

diff --git a/HACKING.rst b/HACKING.rst
index 7d93201..c6b8e6e 100644
--- a/HACKING.rst
+++ b/HACKING.rst
@@ -39,6 +39,7 @@ either additional knowledge about the state of other components in the Octavia
 system, advanced logic behind decisions, or otherwise a high degree of
 intelligence should be done by centralized components (ex. controllers) within
 the Octavia system. Examples of this might include:
+
 * Generating haproxy configuration files
 * Managing the lifecycle of Octavia VMs
 * Moving a loadbalancer instance from one Octavia VM to another.
@@ -46,6 +47,7 @@ the Octavia system. Examples of this might include:
 On the other hand, tasks done extremely often, or which entail a significant
 load on the system should be pushed as far out to the most horizontally
 scalable components as possible. Examples of this might include:
+
 * Serving actual client requests to end-users (ie. running haproxy)
 * Monitoring pool members for failure and sending notifications about this
 * Processing log files
diff --git a/ROADMAP.rst b/ROADMAP.rst
index 6b197fb..2c248fa 100644
--- a/ROADMAP.rst
+++ b/ROADMAP.rst
@@ -27,15 +27,19 @@ be implementing. Work commenced on Octavia coding.
 OpenStack release target: Juno
 
 Neutron LBaaS progress:
+
 * New object model support
 * TLS support
 
 Octavia progress:
+
 * Consensus on:
-** Constitution
-** Road map
-** Component design
-** APIs
+
+ * Constitution
+ * Road map
+ * Component design
+ * APIs
+
 * Initial code underway (perhaps alpha release?)
 
 
@@ -47,24 +51,28 @@ on multiple Nova VMs. Single, centralized command and control (not scalable).
 OpenStack release target: Kilo
 
 Neutron LBaaS progress:
+
 * Flavor support
 * L7 switching support
 * Updated horizon UI
 * Hooks for Heat integration
 
 Octavia progress:
+
 * Octavia delivers all functionality of Neutron LBaaS user API
 * Octavia VMs image building scripts
 * Octavia operator API
 * Horizon UI for operators
 * Neutron LBaaS driver interface for Octavia
 * Non-voting Neutron third-party CI for Octavia to ensure Neutron code changes
-don't break Octavia
+  don't break Octavia
 * Command-and-control layer handles:
-** Octavia VM lifecycle maangement
-** Octavia VM monitoring
-** Octavia VM command and control
-** Neutron LBaaS service deployment
+
+ * Octavia VM lifecycle maangement
+ * Octavia VM monitoring
+ * Octavia VM command and control
+ * Neutron LBaaS service deployment
+
 * Resilient topologies for Octavia VMs (ie. HA for the VMs)
 * "Experimental" project status
 
@@ -77,6 +85,7 @@ services on multiple Nova VMs, and has scalable command and control layer.
 OpenStack release target: "L" release
 
 Octavia progress:
+
 * Possibly becomes reference implementation for Neutron LBaaS
 * Project becomes incubated
 * Fully scalable and HA command-and-control layer
@@ -92,8 +101,9 @@ Description: "Web scale" release of Octavia. Delivers all the features of
 OpenStack release target: ???
 
 Octavia progress:
+
 * "Two layer" load balancing topology implemented where layers 1-4 handled by
-routing infrastructure, and 4-7 handled by Octavia VMs acting in parallel.
+  routing infrastructure, and 4-7 handled by Octavia VMs acting in parallel.
 * Improvements to Horizon UI for operators
 
 
@@ -102,15 +112,17 @@ Short-term timeline
 ===================
 
 Highest priority:
+
 * See Neutron LBaaS work scheduled for Juno through to completion.
 * Import google docs describing v0.5, v1.0 and v2.0 Octavia into specs folder
-of this repository
+  of this repository
 * Get reviews and consensus on the same
 
 Medium priority:
+
 * Define and document Octavia VM <=> Controller RESTful APIs
 * Define best practices for credential management between Octavia VM and
-controllers (suggested: bi-direction server / client certificat verification)
+  controllers (suggested: bi-direction server / client certificat verification)
 * Collect requirements for Operator API
 * Start work on Octavia VM image
 * Start work on Octavia VM agent
@@ -118,9 +130,10 @@ controllers (suggested: bi-direction server / client certificat verification)
 * Create Neutron LBaaS driver for Octavia
 * Get Octavia to work in devstack
 * Flesh out the above items with more detailed checklists as work commences on
-them
+  them
 
 Lower priority:
+
 * Create mock-ups of and start coding Horizon UI for Octavia operators
 * Create non-voting CI interface for testing changes relating to Octavia in
 gerrit
-- 
2.0.1