openstack/devstack
Code Issues Proposed changes
9a3ba4b3e1
devstack/lib/quantum_thirdparty
History
Isaku Yamahata 2cef6fbd44 ryu: minor updates for Ryu upstream change 
Since Ryu upstream changed configuration format, which is user visible.
Plus minor updates.

Fixes bug #1132992
Change-Id: I531360f3e0470916144d2c409066f1a8c75ec26f
Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
2013-02-28 14:50:03 +09: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 ryu: minor updates for Ryu upstream change 2013-02-28 14:50:03 +09: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)