openstack/devstack
Code Issues Proposed changes
26f7a5ae4e
devstack/lib/quantum_thirdparty/README.md
Isaku Yamahata 0dd34df455 lib/quantum: refactor quantum plugins and third party 
As quantum plugin support is coming like floodlight, nvp and nec,
it's worth while to refactor quantum plugin logic so that each plugin can
be modified/enhanced intervening with other quantum plugin.
And new plugin support can be added easily (hopefully) without modifying
core logic.

Change-Id: Ic5ab5b993272fdd3b4e779823323777a845ee681
2013-01-21 11:33:24 +09:00

1.0 KiB
Raw Blame History

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)