e3a9160c0d
The various Neutron plugin files need to have unique variables for the xtrace state as they are sometimes nested more than two levels deep and MY_XTRACE is getting stomped. This gives each of the neutron_plugin and neutron_thirdparty include files a unique XTRACE state variable. I don't think this is a problem with any of the other plugin include files (yet) so this just handles Neutron for now. Change-Id: I7c272a48e7974edecaff5f431ff7443dd6622588 |
||
---|---|---|
.. | ||
bigswitch_floodlight | ||
midonet | ||
README.md | ||
ryu | ||
trema | ||
vmware_nsx |
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>
.
- The corresponding file name should be same to service name,
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