[openstack-dev] [python-openstackclient][python-openstacksdk][neutron][nova] supporting resource extensions with our CLI
amotoki at gmail.com
Tue Aug 8 16:29:10 UTC 2017
2017-08-08 23:12 GMT+09:00 Akihiro Motoki <amotoki at gmail.com>:
> 2017-08-08 22:41 GMT+09:00 Boden Russell <bodenvmw at gmail.com>:
>> On 8/7/17 10:39 PM, Clint Byrum wrote:
>>> If the thing you're doing doesn't fit in the mainline API, then what
>>> you're doing is making a new API. Extensions just bypass the important
>>> part where that API gets designed and thought through.
>> Irrespective of opinions as to if API extensions are good or not, the
>> fact of the matter is we support them in neutron today and as a result
>> we have users that rely on them as well as the ability to interface
>> (CLI) with such extensions via python-neutronclient. That said, I think
>> this concern has been heard  and we will work to address it
>> short-to-mid term.
> I totally agree with other comments that all API features should be upstreamed.
> Replying to Boden's question on the short-term solution.
> If you need CLI support, you can implement OSC plugin to support your
> API extensions
> rather than extending OSC or OSC plugin provided by python-neutronclient.
> If you need SDK support, you can provide your own python bindings
> (perhaps it will be most stable)
> or continue to use the python-neutronclient CLI extension mechanism
> (which extends methods
> based on "neutronclient.extension" entry points.
> Does it answer to you, Boden?
My above reply does not answer the original question.
The subject of the thread says "resource extension" but this is
actually on attribute extension.
My reply applies to 'resource' extension but does not apply to
>> As to neutron's longer-term goals W/R/T API extensions; I can't speak to
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev