42503fc929
(Finally) move away from the old quantum naming for services, and move to the ultra-modern, but bland, neutron-vpnaas naming. On a practical note, coupled with I2bb7ac01e619c8a9b22bd517a4ff60d67035dfed this commit prevents two VPN agent processes from being started. Note: This cannot be tested/upstreamed, until the devstack repo commit is upstreamed. With this commit, the Devstack plugin for VPN is completed. Closes-Bug: 1473475 Closes-Bug: 1484141 Change-Id: I267c300ef5a577823dddec08e0a93e098413198a Depends-On: I2bb7ac01e619c8a9b22bd517a4ff60d67035dfed |
||
---|---|---|
.. | ||
plugin.sh | ||
README.md | ||
settings |
This directory contains the neutron-vpnaas devstack plugin. To configure VPNaaS, in the local section, you will need to enable the neutron-vpnaas devstack plugin.
Add a line of the form:
enable_plugin neutron-vpnaas <GITURL> [GITREF]
where
<GITURL> is the URL of a neutron-vpnaas repository
[GITREF] is an optional git ref (branch/ref/tag). The default is
master.
For example
enable_plugin neutron-vpnaas https://git.openstack.org/openstack/neutron-vpnaas stable/kilo
Note: Since the VPN agent process, is a subclass of the L3 agent, which is a subclass of the FW agent, the DevStack plugin will check for the FW service being enabled, and if so, will include the config file specified in Q_FWAAS_CONF_FILE (default is fwaas_driver.ini).
For more information, see the "Externally Hosted Plugins" section of http://docs.openstack.org/developer/devstack/plugins.html.