openstack team mailing list archive

[Joseph Heck <heckj@xxxxxx>]

I think Dean Troyer was going to take an even farther stance at the Summit. A unified client for all the core projects (and "OpenStack client") instead of the proliferation of separate clients that we have. As we got into really testing the Essex release these past weeks, it because pretty clear to me that the user experience of working with nova, glance, and keystone (sorry Dan, I wasn't trying to through Quantum in the mix too at the time) - was definitely working with totally separate projects. On top of which is required some pretty deep knowledge of how and where things tied in to use those clients effectively (i..e don't use "nova project list", use "keystone tenant-list". 

These all made sense while focused on the individual projects, but make for a confusing proliferation of tools needed to deploy, run and use OpenStack.

OpenStack would be well served to consolidate the clients, or at the very least drive further against the ideas started in http://wiki.openstack.org/UnifiedCLI to make the command structure, responses, and options available in clients consistent. For horizon, just having python libraries that don't require the entire back-end of a system to be installed was necessary, so the proliferation didn't matter that much. We are evolving beyond that now.

-joe

On Apr 5, 2012, at 9:04 AM, Brian Waldon wrote:
> We should definitely push to consolidate common code for clients! We can use either glanceclient or quantumclient as a prototype. As for the auth code specifically, it can be replaced with something as simple as this:  https://github.com/openstack/python-glanceclient/blob/master/glanceclient/shell.py#L119
> 
> 
> On Apr 4, 2012, at 9:11 AM, Dan Wendlandt wrote:
> 
>> Very cool guys!
>> 
>> We'll be reworking the Quantum client in a similar alignment effort during Folsom. 
>> 
>> One question to that end: is there any effort to get much of the code that will be common across all OpenStack python-*client projects into something like openstack-common (or an openstack-client-common)?  It seems like much of what is in https://github.com/openstack/python-glanceclient/tree/master/glanceclient/common would be useful across all projects.  The same could likely be said for the basic keystone code required by a client (e.g., https://github.com/openstack/python-novaclient/blob/master/novaclient/service_catalog.py).  
>> Thanks, 
>> 
>> Dan
>> 
>> On Tue, Apr 3, 2012 at 8:39 PM, Brian Waldon <brian.waldon@xxxxxxxxxxxxx> wrote:
>> In an effort to further align OpenStack API clients, Jay Pipes, Monty Taylor and myself have set up the python-glanceclient project. It is not intended to be a drop-in replacement for the existing client that lives in Glance, but a complete rewrite with a shiny new interface that maintains feature-parity.
>> 
>> As for integrating this new client with the necessary OpenStack projects, here's a little roadmap I came up with:
>> 
>> X 1) Basic functionality
>> X 2) Integrate with Gerrit
>> 3) Verify feature parity
>> 4) Integrate with DevStack
>> 5) Integrate with Nova
>> 6) Drop old client from Glance
>> 
>> If anybody is interested in playing with the new client, here it is: https://github.com/openstack/python-glanceclient. You can either yell at me or use Gerrit to fix anything I may have overlooked. Thanks!
>> 
>> Brian Waldon
>> 
>> 
>> 
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>> 
>> 
>> 
>> 
>> -- 
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Dan Wendlandt 
>> Nicira Networks: www.nicira.com
>> twitter: danwendlandt
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp