openstack
/
devstack
Code Issues Proposed changes
devstack/lib/neutron_thirdparty
History
Ian Wienand 523f488036 Namespace XTRACE commands 
I noticed this when debugging some grenade issues failures.

An include of grenade/functions stores the current value of XTRACE
(on) and disables xtrace for the rest of the import.

We then include devstack's "functions" library, which now overwrites
the stored value of XTRACE the current state; i.e. disabled.

When it finishes it restores the prior state (disabled), and then
grenade restores the same value of XTRACE (disabled).

The result is that xtrace is incorrectly disabled until the next time
it just happens to be turned on.

The solution is to name-space the store of the current-value of xtrace
so when we finish sourcing a file, we always restore the tracing value
to what it was when we entered.

Some files had already discovered this.  In general there is
inconsistency around the setting of the variable, and a lot of obvious
copy-paste.  This brings consistency across all files by using
_XTRACE_* prefixes for the sotre/restore of tracing values.

Change-Id: Iba7739eada5711d9c269cb4127fa712e9f961695
 		2015-11-27 15:36:04 +11:00
..
README.md Rename lib/neutron to lib/neutron-legacy 2015-03-25 22:22:11 -04:00
bigswitch_floodlight Namespace XTRACE commands 2015-11-27 15:36:04 +11:00
vmware_nsx Update to bashate 0.3.2 2015-10-29 11:30:20 +11:00

README.md

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-legacy 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