stackforge/libra
Code Issues Proposed changes

[docs] Minor documentation clean up.

Browse Source 
Change-Id: I2baf131546d0ef0bf8e5fc4d3e1c4854572f9b03
This commit is contained in:
David Shrewsbury
2013-06-27 13:12:33 -04:00
parent 48b55a66f3
commit fe170f378c
2 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/api/api.rst
View File

@@ -2283,6 +2283,6 @@ The following features are not supported.
and the HTTPS connections will be passed through the load balancer with no
termination at the load balancer.
3. The ability to list deleted load balancers is yet not supported.
3. The ability to list deleted load balancers is not yet supported.

7
doc/introduction.rst
View File

@@ -6,12 +6,13 @@ Hewlett-Packard Cloud Services. It consists of five core components
required to get LBaaS working:
* A node pool manager to keep a warm spare pool of load balancers ready
* A node worker to asyncronusly communicate to the API server
* A node worker to asynchronously communicate to the API server
* A monitoring system for the load balancers
* A customer API server
* An administrative API server
The API server is based on a modified version of the Atlas API specification.
The API server is based on a modified version of the `Atlas API specification
<https://wiki.openstack.org/wiki/Atlas-LB>`_.
Layout
------
@@ -30,4 +31,4 @@ designed to use HAProxy.
The statsd monitoring system routinely probes the workers and can alert on as
well as disable faulty nodes.
The parts of this diagram in orange are provided by the libra codebase.
The parts of this diagram in orange are provided by the Libra codebase.