openstack
/
neutron
Code Issues Proposed changes

Fix minor nits with the devref's contribute section 

Be more explicit on the adoption of Externally Hosted Plugins, which
are based on Extra.d Hooks.

Partially-implement: blueprint core-vendor-decomposition

Change-Id: I4510aaa74c8853278b1c17757d4f4fa67554093a
This commit is contained in:
armando-migliaccio 2015-02-06 23:44:07 -08:00
parent b1b15d26f5
commit eca0d1ff24
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/devref/contribute.rst
View File

@ -221,12 +221,12 @@ make sense depending on whether you are contributing a new or existing plugin or
driver.
If you are contributing a new plugin, the approach to choose should be based on
`Extras.d Hooks <http://docs.openstack.org/developer/devstack/plugins.html#extras-d-hooks>`_.
`Extras.d Hooks' externally hosted plugins <http://docs.openstack.org/developer/devstack/plugins.html#extras-d-hooks>`_.
With the extra.d hooks, the DevStack integration is colocated with the vendor integration
library, and it leads to the greatest level of flexibility when dealing with DevStack based
dev/test deployments.
Having said that, most Neutron Plugins developed in the past likely already have
Having said that, most Neutron plugins developed in the past likely already have
integration with DevStack in the form of `neutron_plugins <https://github.com/openstack-dev/devstack/tree/master/lib/neutron_plugins>`_.
If the plugin is being decomposed in vendor integration plus vendor library, it would
be necessary to adjust the instructions provided in the neutron_plugin file to pull the