
Start running the doc8 RST linter in the pep8 job. This will catch obvious errors like line too long, etc. Tried to fix most of the errors (there were a lot!), but added some ignore directives so we can address some files later. Did have to move a couple of files around as a double include was causing some issues, but content is unchanged. Change-Id: I336a9ee7729045da095be22ea0f58ee596967174
38 lines
1.4 KiB
ReStructuredText
38 lines
1.4 KiB
ReStructuredText
.. _config-experimental-framework:
|
|
|
|
===============================
|
|
Experimental Features Framework
|
|
===============================
|
|
|
|
Some Neutron features are not supported because the community doesn't have
|
|
the resources and/or technical expertise to maintain them anymore. As they
|
|
arise, the Neutron team designates these features as experimental. Deployers
|
|
can continue using these features at their own risk, by explicitly enabling
|
|
them in the ``experimental`` section of ``neutron.conf``.
|
|
|
|
.. note::
|
|
Of course, the Neutron core team would love to return experimetal features
|
|
to the supported status, if interested parties step up to maintain them. If
|
|
you are interested in maintaining any of the experimental features listed
|
|
below, please contact the PTL shown in the
|
|
`Neutron project page
|
|
<https://governance.openstack.org/tc/reference/projects/neutron.html>`_.
|
|
|
|
The following table shows the Neutron features currently designated as
|
|
experimetal:
|
|
|
|
.. table:: **Neutron Experimental features**
|
|
|
|
========================= ===================================
|
|
Feature Option in neutron.conf to enable
|
|
========================= ===================================
|
|
ML2 Linuxbridge driver linuxbridge
|
|
========================= ===================================
|
|
|
|
This is an example of how to enable the use of an experimental feature:
|
|
|
|
.. code-block:: ini
|
|
|
|
[experimental]
|
|
linuxbridge = true
|