16dd8b3ed9
we mostly have a consistent style on if/then & for/do in devstack, except when we don't. This attempts to build a set of rules to enforce this. Because there are times when lines are legitimately long, and there is a continuation, this starts off ignoring if and for loops with continuations. But for short versions, we should enforce this. Changes to make devstack pass are included. The fact that the cleanup patch was so small is pretty solid reason that this is actually the style we've all agreed to. Part of a git stash from hong kong that I finally cleaned up. Change-Id: I6376d7afd59cc5ebba9ed69e5ee784a3d5934a10 |
||
|---|---|---|
| .. | ||
| 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