5c8941eeed
This adds a new tox environment, genconfig, which generates sample neutron VPNaaS configuration file using oslo-config-generator. Updates to some configuration option help messages to reflect useful details that were missing in the code but were present in config files. DocImpact: Update the docs that VPNaaS no longer includes static example configuration files. Instead, use tools/generate_config_file_samples.sh to generate them and the files generated now end with .sample extension. Partially-Implements: blueprint autogen-neutron-conf-file Change-Id: I4a6094b8218dfd320d05bfb1e3bc121e8930c551 Partial-bug: #1199963 |
||
---|---|---|
.. | ||
README.md | ||
plugin.sh | ||
settings |
README.md
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.