Files

Dean Troyer 8d55be31a9 Handle nested xtrace states (Quantum edition)

The lib/quantum_* directories include plugin files that also
contains the $XTRACE bits at entry and exit.  The nested XTRACE handling overwrote
the value from lib/quantum.  So...make the nested files use their own
XTRACE variables.

Change-Id: Ib5e643371666b21402eef2ec58bfb1dfb7e1ccc4

2013-02-07 17:16:40 -06:00

bigswitch_floodlight

Handle nested xtrace states (Quantum edition)

2013-02-07 17:16:40 -06:00

README.md

lib/quantum: refactor quantum plugins and third party

2013-01-21 11:33:24 +09:00

ryu

Handle nested xtrace states (Quantum edition)

2013-02-07 17:16:40 -06:00

README.md

Quantum third party specific files

Some Quantum plugins require third party programs to function. The files under the directory, lib/quantum_thirdparty/, will be used when their service are enabled. Third party program specific configuration variables should be in this file.

filename: <third_party>
- The corresponding file name should be same to service name, <third_party>.

functions

lib/quantum calls the following functions when the <third_party> is enabled

functions to be implemented

configure_<third_party>: set config files, create data dirs, etc e.g. sudo python setup.py deploy iniset $XXXX_CONF...
init_<third_party>: initialize databases, etc
install_<third_party>: collect source and prepare e.g. git clone xxx
start_<third_party>: start running processes, including screen e.g. screen_it XXXX "cd $XXXXY_DIR && $XXXX_DIR/bin/XXXX-bin"
stop_<third_party>: stop running processes (non-screen)