yahoo-eng-team team mailing list archive

[Salvatore Orlando <1528510@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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 CollectionController and ItemController.

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://git.openstack.org/cgit/openstack/neutron/tree/neutron/pecan_wsgi/startup.py#n86

** Affects: neutron
     Importance: Medium
     Assignee: Salvatore Orlando (salvatore-orlando)
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1528510

Title:
  Pecan: startup assumes controllers specify plugins

Status in neutron:
  New

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 CollectionController and
  ItemController.

  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://git.openstack.org/cgit/openstack/neutron/tree/neutron/pecan_wsgi/startup.py#n86

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1528510/+subscriptions