Why not to use stevedore?
On Wed, Jun 18, 2014 at 1:42 PM, Igor Kalnitsky <[email protected]> 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 <[email protected]> > 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 >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Andrey Danin [email protected] skype: gcon.monolake
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
