Hi All, It's great to see the vendor plugin decomposition spec 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.
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. Thanks in advance! Best, Ryu  https://review.openstack.org/#/c/134680/
_______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev