[openstack-dev] [neutron] Vendor Plugin Decomposition and NeutronClient vendor extension

Armando M. armamig at gmail.com
Sat Dec 13 06:32:16 UTC 2014


On 12 December 2014 at 22:18, Ryu Ishimoto <ryu at midokura.com> wrote:
>
>
> Hi All,
>
> It's great to see the vendor plugin decomposition spec[1] finally getting
> merged!  Now that the spec is completed, I have a question on how this may
> impact neutronclient, and in particular, its handling of vendor extensions.
>

Thanks for the excitement :)


>
> One of the great things about splitting out the plugins is that it will
> allow vendors to implement vendor extensions more rapidly.  Looking at the
> neutronclient code, however, it seems that these vendor extension commands
> are embedded inside the project, and doesn't seem easily extensible.  It
> feels natural that, now that neutron vendor code is split out,
> neutronclient should also do the same.
>
> Of course, you could always fork neutronclient yourself, but I'm wondering
> if there is any plan on improving this.  Admittedly, I don't have a great
> solution myself but I'm thinking something along the line of allowing
> neutronclient to load commands from an external directory.  I am not
> familiar enough with neutronclient to know if there are technical
> limitation to what I'm suggesting, but I would love to hear thoughts of
> others on this.
>

There is quite a bit of road ahead of us. We haven't thought or yet
considered how to handle extensions client side. Server side, the extension
mechanism is already quite flexible, but we gotta learn to walk before we
can run!

Having said that your points are well taken, but most likely we won't be
making much progress on these until we have provided and guaranteed a
smooth transition for all plugins and drivers as suggested by the spec
referenced below. Stay tuned!

Cheers,
Armando


>
> Thanks in advance!
>
> Best,
> Ryu
>
> [1] https://review.openstack.org/#/c/134680/
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141212/d076c72c/attachment.html>


More information about the OpenStack-dev mailing list