Go to file
David Shrewsbury 0ad3586a31 Logging fix and --syslog option.
Logging did not work when running as a daemon
because all open file handles were closed for
the fork. Since we cannot get to the file handle
using the 'logging' module, we'll just have to
re-init the logging after the daemon starts.

Added a --syslog option so that we can choose to
use syslog for capturing our logs. If present, it
takes precedence over any log file specified. The
timestamps are removed from the log message when
using syslog (it is assumed syslog will add the time).
2012-10-01 16:12:19 -04:00
2012-09-14 12:19:33 +01:00
2012-10-01 16:12:19 -04:00
2012-10-01 16:12:19 -04:00
2012-09-27 17:24:06 -07:00
2012-09-26 12:02:58 -07:00
2012-09-21 15:52:52 -04:00
2012-09-13 16:25:53 -04:00
2012-09-27 17:03:30 -07:00

Description
-----------

A Python-based Gearman worker that handles work for the job queue named
'lbaas-<IP>'. It receives JSON data describing a load balancer, and
returns this same JSON object, but with status fields added to describe
the state of the LB.


Running Tests
-------------

Tox is the best way to run the tests. Tox, if unavailable, can be installed
via the Python pip command:

   $ pip install tox

Once it is installed, run the tests:

   $ tox


Installing the Worker
---------------------

    $ python setup.py install


Running the Worker
------------------

The worker can run in either daemon or non-daemon mode. Daemon mode requires
escalated privileges so that it can behave like a proper daemon. Non-daemon
mode (--nodaemon option) is useful for testing.

Basic commands:

    # Getting help
    $ libra_worker -h

    # Start up as a daemon
    $ sudo libra_worker

    # Start up with debugging output in non-daemon mode
    $ libra_worker --debug --nodaemon

You can verify that the worker is running by using the sample Gearman
client in the bin/ directory:

    $ bin/client.py
Description
RETIRED, Create and manage loadbalancers
Readme 5.1 MiB