Open Stack

Cool. I have no objections.
On Jun 25, 2014 9:27 AM, "Dmitriy Shulyak" <dshulyak at mirantis.com> wrote:

> As i mentioned cliff uses similar approach, extending app by means of
> entry points, and written by same author.
> So i think stevedore will be used in cliff, or maybe already used in newer
> versions.
> But apart of stevedore-like dynamic extensions - cliff provides modular
> layers for cli app, it is kindof framework for wrtiting
> cli applications.
>
>
> On Tue, Jun 24, 2014 at 11:15 PM, Andrey Danin <adanin at mirantis.com>
> wrote:
>
>> Why not to use stevedore?
>>
>>
>> On Wed, Jun 18, 2014 at 1:42 PM, Igor Kalnitsky <ikalnitsky at mirantis.com>
>> wrote:
>>
>>> Hi guys,
>>>
>>> Actually, I'm not a fun of cliff, but I think it's a good solution to
>>> use it in our fuel client.
>>>
>>> Here some pros:
>>>
>>> * pluggable design: we can encapsulate entire command logic in separate
>>> plugin file
>>> * builtin output formatters: we no need to implement various formatters
>>> to represent received data
>>> * interactive mode: cliff makes possible to provide a shell mode, just
>>> like psql do
>>>
>>> Well, I vote to use cliff inside fuel client. Yeah, I know, we need to
>>> rewrite a lot of code, but we
>>> can do it step-by-step.
>>>
>>> - Igor
>>>
>>>
>>>
>>>
>>> On Wed, Jun 18, 2014 at 9:14 AM, Dmitriy Shulyak <dshulyak at mirantis.com>
>>> wrote:
>>>
>>>> Hi folks,
>>>>
>>>> I am wondering what our story/vision for plugins in fuel client [1]?
>>>>
>>>> We can benefit from using cliff [2] as framework for fuel cli, apart
>>>> from common code
>>>> for building cli applications on top of argparse, it provides nice
>>>> feature that allows to
>>>> dynamicly add actions by means of entry points (stevedore-like).
>>>>
>>>> So we will be able to add new actions for fuel client simply by
>>>> installing separate packages with correct entry points.
>>>>
>>>> Afaik stevedore is not used there, but i think it will be - cause of
>>>> same author and maintainer.
>>>>
>>>> Do we need this? Maybe there is other options?
>>>>
>>>> Thanks
>>>>
>>>> [1] https://github.com/stackforge/fuel-web/tree/master/fuelclient
>>>> [2]  https://github.com/openstack/cliff
>>>>
>>>> _______________________________________________
>>>> OpenStack-dev mailing list
>>>> OpenStack-dev at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>> Andrey Danin
>> adanin at mirantis.com
>> skype: gcon.monolake
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> _______________________________________________
> 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/20140626/b33116bc/attachment.html>