9732b57e3d
Devstack should not die if the IP and prefix len for establishing a connection to the public network are not provided. In this case, the public gateway IP address used to configure Neutron's public network should be used, together with the prefix length of the public network's CIDR. This patch also ensures $PUBLIC_BRIDGE is created, even if Q_USE_DEBUG_COMMAND is disabled. Finally this patch also adds the teardown operation for restoring the original IP addresses on the interface used for connectivity to the public network implemented on the NVP gateway. Bug #1227750 Change-Id: Ib58738a578c46f2183d503cabfdc6039bfbeb702 |
||
|---|---|---|
| .. | ||
| bigswitch_floodlight | ||
| midonet | ||
| nicira | ||
| README.md | ||
| ryu | ||
| trema | ||
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)