On Thu, 5 Apr 2012, Dan Wendlandt wrote:
Hi Joe,
I've often had a similar thought myself of whether a single 'osclient'
would be better. I see consistency across all clients as the bare minimum,
and a single client as an interesting option to explore. Thanks for
driving this Dean, I look
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:
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
Hi Joe,
I've often had a similar thought myself of whether a single 'osclient'
would be better. I see consistency across all clients as the bare minimum,
and a single client as an interesting option to explore. Thanks for
driving this Dean, I look forward to talking about it at the summit.
Dan
On Tue, Apr 3, 2012 at 10:39 PM, Brian Waldon
brian.wal...@rackspace.com wrote:
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.
Coolness! I've added it to the command mapping in
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
6 matches
Mail list logo
