devstack/lib/neutron_thirdparty
armando-migliaccio db20cd5436 Add Neutron/NSX plugin sanity check
Supports-blueprint: nvp-third-party-support (aka bp vmware-nsx-third-party)
Related-bug: #1265671

Change-Id: Ifa4e1d36b8735e81f24b8852103a9c433d736e84
2014-01-25 09:05:01 -08:00
..
bigswitch_floodlight Add sanity check framework to verify neutron server/backend integration 2014-01-14 08:14:25 -08:00
midonet Add sanity check framework to verify neutron server/backend integration 2014-01-14 08:14:25 -08:00
README.md Add sanity check framework to verify neutron server/backend integration 2014-01-14 08:14:25 -08:00
ryu Add sanity check framework to verify neutron server/backend integration 2014-01-14 08:14:25 -08:00
trema Add sanity check framework to verify neutron server/backend integration 2014-01-14 08:14:25 -08:00
vmware_nsx Add Neutron/NSX plugin sanity check 2014-01-25 09:05:01 -08: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 e.g. screen_it XXXX "cd $XXXXY_DIR && $XXXX_DIR/bin/XXXX-bin"

  • stop_<third_party>: stop running processes (non-screen)

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