Pecan: startup assumes controllers specify plugins
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Salvatore Orlando |
Bug Description
At startup, the Pecan API server associates a plugin (core or service) to every Neutron resource.
With this association, every Pecan controller gets a plugin where calls should be dispatched.
However, this association is not performed for 'pecanized extensions' [1]. A 'pecanized' extension is a Neutron API extension which is able to return Pecan controllers. The plugin association is instead currently performed only for those extensions for which a controller is generated on-the-fly using the generic CollectionContr
This approach has the drawback that the API extension descriptor should have the logic to identify a plugin for the API itself.
While this is not a bad idea, it requires extensions descriptors to identify a plugin, thus duplicating, in a way, what's already done by the extension manager.
For this reason it is advisable to do plugin association for all extensions during pecan startup unless until the Pecan framework won't rely anymore on the home grown extension manager.
[1] http://
Changed in neutron: | |
milestone: | mitaka-2 → mitaka-3 |
Fix proposed to branch: master /review. openstack. org/260439
Review: https:/