Re: [openstack-dev] [FUEL]Re-thinking Fuel Client

On Thu, Nov 20, 2014 at 9:30 AM, Roman Prykhodchenko < rprikhodche...@mirantis.com> wrote: > I think this is not very reasonable because Fuel does not provide any > service in OpenStack but instead allows to set up and manage OpenStack > clusters. > Ah, well that is different. FWIW, I have done

Re: [openstack-dev] [FUEL]Re-thinking Fuel Client

Dean, thank you for your input. > On 20 Nov 2014, at 15:43, Dean Troyer wrote: > > [pardon my jumping in like kibo, someone mentioned 'client' ;) ] Now I know for sure how to summon you :) > > On Thu, Nov 20, 2014 at 3:01 AM, Vladimir Kozhukalov > mailto:vkozhuka...@mirantis.com>> wrote: > 0

Re: [openstack-dev] [FUEL]Re-thinking Fuel Client

So as I mentioned in the etherpad I published a spec here https://review.openstack.org/#/c/135915/ Everyone is welcome to review it. @Juan: For sure we should use keystone for auth. I might have stated it wrong. What I mean is that we should use simila

Re: [openstack-dev] [FUEL]Re-thinking Fuel Client

[pardon my jumping in like kibo, someone mentioned 'client' ;) ] On Thu, Nov 20, 2014 at 3:01 AM, Vladimir Kozhukalov < vkozhuka...@mirantis.com> wrote: > 0) Rename fuelclient into python-fuelclient like any other OpenStack > clients when moving it to a separate repo. > 1) Use cliff as a cli libr

Re: [openstack-dev] [FUEL]Re-thinking Fuel Client

Hi, As a Fuel user I would like to give some input. 0) This would make fuel adhere to the standards for clients, I agree with this change. 1) cliff is not really necessary, but is actually being adopted by some other projects (other than OpenStack unified client) I initially proposed it for barbi

Re: [openstack-dev] [FUEL]Re-thinking Fuel Client

Roman, I am absolutely +1 for re-designing fuel client and bringing it out of fuel-web repo. If you ask me, it is also important to make new design following kind of standard just to avoid re-re-designing it in the foreseeable future. Some points here are: 0) Rename fuelclient into python-fuelcli

[openstack-dev] [FUEL]Re-thinking Fuel Client

Hi folks! I’ve made several internal discussions with Łukasz Oleś and Igor Kalnitsky and decided that the existing Fuel Client has to be redesigned. The implementation of the client we have at the moment does not seem to be compliant with most of the use cases people have in production and canno