On Aug 3, 2012, at 6:59 AM, Alan Pevec wrote:
So before glance is removed from openstack/glance (in folsom-3 if I
understood correctly?)
Given the response from the community, I think it would be a bad idea to remove
bin/glance in Folsom. My current plan is to leave it in until Grizzly
Brian Waldon wrote:
Ok, so I spent some time on this and got all of the existing/legacy CLI
working within python-glanceclient. It should let anybody using the
existing client keep on keepin' on without having to worry about CLI
compatibility (until we actually remove the deprecated
The review has now landed in python-glanceclient master, so I'm going to
release it tomorrow as v0.3.0 if nothing comes up between now and then.
On Aug 2, 2012, at 3:10 AM, Thierry Carrez wrote:
Brian Waldon wrote:
Ok, so I spent some time on this and got all of the existing/legacy CLI
On Jul 31, 2012, at 10:09 PM, Brian Waldon bcwal...@gmail.com wrote:
I do agree that this current upgrade story could be better, but how much
better do you expect it to be and in what specific ways? If the command-line
interface were backwards-compatibile, would that solve all your
] [glance] legacy client removal and python-
glanceclient
On Jul 31, 2012, at 10:09 PM, Brian Waldon bcwal...@gmail.com wrote:
I do agree that this current upgrade story could be better, but how much
better do you expect it to be and in what specific ways? If the command-line
interface
On Wed, 01 Aug 2012 01:06:10 -0400
Jay Pipes jaypi...@gmail.com wrote:
I don't disagree with you. At the same time, I think Brian has a good
point when he compares having two versions of SQLAlchemy installed on a
system: it just doesn't make much sense.
But having glance(1) and
Gabriel Hurley wrote:As a rule of thumb, we need to start doing proper deprecation on allpublic interfaces, whether that's a CLI, client method signatures,APIs, etc. It's a little late for this on the old vs. new glanceclient/CLI (unless Brian feels the work can be reasonably done tomake them
On Wed, 2012-08-01 at 18:37 +, Gabriel Hurley wrote:
As a rule of thumb, we need to start doing proper deprecation on all
public interfaces, whether that's a CLI, client method signatures,
APIs, etc. It's a little late for this on the old vs. new glance
client/CLI (unless Brian feels the
. Mitchell
Sent: Wednesday, August 01, 2012 12:19 PM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] [glance] legacy client removal and python-
glanceclient
On Wed, 2012-08-01 at 18:37 +, Gabriel Hurley wrote:
As a rule of thumb, we need to start doing proper deprecation on all
On 08/01/2012 03:18 PM, Kevin L. Mitchell wrote:
On Wed, 2012-08-01 at 18:37 +, Gabriel Hurley wrote:
As a rule of thumb, we need to start doing proper deprecation on all
public interfaces, whether that's a CLI, client method signatures,
APIs, etc. It's a little late for this on the old
On 08/01/2012 02:11 PM, Pete Zaitcev wrote:
On Wed, 01 Aug 2012 01:06:10 -0400
Jay Pipes jaypi...@gmail.com wrote:
I don't disagree with you. At the same time, I think Brian has a good
point when he compares having two versions of SQLAlchemy installed on a
system: it just doesn't make much
On Wed, 2012-08-01 at 19:50 +, Gabriel Hurley wrote:
Personally I'd recommend using Python's built-in warnings module and
the standard DeprecationWarning and PendingDeprecation warning
classes:
http://docs.python.org/library/warnings.html#warning-categories
For an example of this in
On 01/08/12 15:09, Brian Waldon wrote:
I do agree that this current upgrade story could be better, but how
much better do you expect it to be and in what specific ways? If the
command-line interface were backwards-compatibile, would that solve
all your problems? I'm fine doing that for the
Ok, so I spent some time on this and got all of the existing/legacy CLI working
within python-glanceclient. It should let anybody using the existing client
keep on keepin' on without having to worry about CLI compatibility (until we
actually remove the deprecated functionality in the v2
On Tue, 2012-07-31 at 11:41 -0700, Brian Waldon wrote:
released python-glanceclient v0.2.0 and would love to gather some
feedback. Please file bugs on the python-glanceclient project in
launchpad if you find anything to be missing.
What is the plan to deal with the fact that the user interface
On Jul 31, 2012, at 2:37 PM, Christoph Hellwig wrote:
On Tue, 2012-07-31 at 11:41 -0700, Brian Waldon wrote:
released python-glanceclient v0.2.0 and would love to gather some
feedback. Please file bugs on the python-glanceclient project in
launchpad if you find anything to be missing.
On Tue, 2012-07-31 at 15:17 -0700, Brian Waldon wrote:
On Jul 31, 2012, at 2:37 PM, Christoph Hellwig wrote:
On Tue, 2012-07-31 at 11:41 -0700, Brian Waldon wrote:
released python-glanceclient v0.2.0 and would love to gather some
feedback. Please file bugs on the python-glanceclient
On Jul 31, 2012, at 2:41 PM, Brian Waldon bcwal...@gmail.com wrote:
This is a reminder that the client in glance is deprecated and will not ship
with Folsom. Horizon and Devstack both use python-glanceclient, and I'm
presently working on updating Nova.
I also wanted to point out that I
I think we're running out of opportunities to do stuff like this.
This is exactly the sort of thing that will drive George Reese into a
homocidal rage. More to the point its exactly the sort of thing our users
are going to despise us for. And that hatred will outlive any benefit.
Users only
On 08/01/2012 12:49 AM, Matt Joyce wrote:
I think we're running out of opportunities to do stuff like this.
This is exactly the sort of thing that will drive George Reese into a
homocidal rage. More to the point its exactly the sort of thing our
users are going to despise us for. And that
On Jul 31, 2012, at 9:49 PM, Matt Joyce wrote:
I think we're running out of opportunities to do stuff like this.
This is exactly the sort of thing that will drive George Reese into a
homocidal rage. More to the point its exactly the sort of thing our users
are going to despise us for.
21 matches
Mail list logo
