stackforge/libra
Code Issues Proposed changes

A better docs option cross-reference fix

Browse Source 
Change-Id: I41459cb0569181cabfe824cd7f81ae1fef81da9f
This commit is contained in:
Andrew Hutchings 2012-11-13 12:05:53 +00:00
parent 20d89cccd5
commit 8f1fa33a97
2 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/pool_mgm/code.rst
View File

@ -124,7 +124,7 @@ Known Drivers Dictionary
.. py:data:: known_drivers .. py:data:: known_drivers
This is the dictionary that maps values for the This is the dictionary that maps values for the
:option:`libra_pool_mgm.py --driver` option :option:`--driver <libra_pool_mgm.py --driver>` option
to a class implementing the driver :py:class:`~MgmDriver` API to a class implementing the driver :py:class:`~MgmDriver` API
for that API server. After implementing a new driver class, you simply add for that API server. After implementing a new driver class, you simply add
a new entry to this dictionary to plug in the new driver. a new entry to this dictionary to plug in the new driver.

5
doc/worker/code.rst
View File

@ -100,7 +100,7 @@ Known Load Balancer Drivers Dictionary
.. py:data:: known_drivers .. py:data:: known_drivers
This is the dictionary that maps values for the This is the dictionary that maps values for the
:option:`libra_worker.py --driver` option :option:`--driver <libra_worker.py --driver>` option
to a class implementing the driver :py:class:`~LoadBalancerDriver` API to a class implementing the driver :py:class:`~LoadBalancerDriver` API
for that appliance. After implementing a new driver class, you simply add for that appliance. After implementing a new driver class, you simply add
a new entry to this dictionary to plug in the new driver. a new entry to this dictionary to plug in the new driver.
@ -138,7 +138,8 @@ The steps shown above are:
the message that it received. the message that it received.
* Based on the contents of the message, the controller then makes the relevant * Based on the contents of the message, the controller then makes the relevant
driver API calls using the :py:class:`~drivers.LoadBalancerDriver` driver driver API calls using the :py:class:`~drivers.LoadBalancerDriver` driver
that was selected via the :option:`libra_worker.py --driver` option. that was selected via the :option:`--driver <libra_worker.py --driver>`
option.
* The driver executes the API call. If the driver encounters an error during * The driver executes the API call. If the driver encounters an error during
execution, an exception is thrown that should be handled by the execution, an exception is thrown that should be handled by the
:py:class:`~controller.LBaaSController` object. Otherwise, nothing is :py:class:`~controller.LBaaSController` object. Otherwise, nothing is