devstack/lib/neutron_thirdparty
Jaume Devesa 9826093202 Improve MidoNet integration
Since midonet has become open source, we can build it from
external plugin scripts. The way to enable it is using the devstack
plugin approach:

    disable_service n-net
    enable_service q-svc
    enable_service q-dhcp
    enable_service q-meta
    enable_plugin networking-midonet \
        http://github.com/stackforge/networking-midonet
    Q_PLUGIN=midonet

and should download and build the last master branch of midonet.

Change-Id: I795f92f9d3c97b2c35bac712c6edfc032eff345a
2015-02-25 08:40:44 +00:00
..
bigswitch_floodlight add shebang lines to all lib files 2014-12-10 11:28:05 -05:00
README.md Replace screen_it() with run_process() throughout 2014-09-11 18:59:39 +01:00
trema add shebang lines to all lib files 2014-12-10 11:28:05 -05:00
vmware_nsx add shebang lines to all lib files 2014-12-10 11:28:05 -05:00

Neutron third party specific files

Some Neutron plugins require third party programs to function. The files under the directory, lib/neutron_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/neutron 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 if USE_SCREEN=True e.g. run_process XXXX "$XXXX_DIR/bin/XXXX-bin"

  • stop_<third_party>: stop running processes (non-screen) e.g. stop_process XXXX

  • check_<third_party>: verify that the integration between neutron server and third-party components is sane