On 09/14/2015 02:41 PM, Monty Taylor wrote:
On 09/14/2015 04:58 PM, Brian Rosmaita wrote:
I'm not saying that there's no other way to do this -- e.g., you could do
all sorts of alternative workflows and configurations in the "regular"
upload process -- but the feedback I got can be summarized li
On 14/09/15 16:09 -0400, Doug Hellmann wrote:
Excerpts from Monty Taylor's message of 2015-09-14 20:41:38 +0200:
On 09/14/2015 04:58 PM, Brian Rosmaita wrote:
[snip]
If "glance import-from http://example.com/my-image.qcow2' always worked,
and in the back end generated a task with the task work
Excerpts from Monty Taylor's message of 2015-09-14 20:41:38 +0200:
> On 09/14/2015 04:58 PM, Brian Rosmaita wrote:
> > Apologies for forking the thread, but there was way too much in Doug's
> > email (and Flavio's response) and I only want to make a few points about
> > tasks. Please read Doug's o
On 09/14/2015 04:58 PM, Brian Rosmaita wrote:
Apologies for forking the thread, but there was way too much in Doug's
email (and Flavio's response) and I only want to make a few points about
tasks. Please read Doug's original email and Flavio's reply at some
point, preferably before you read this
Apologies for forking the thread, but there was way too much in Doug's
email (and Flavio's response) and I only want to make a few points about
tasks. Please read Doug's original email and Flavio's reply at some
point, preferably before you read this.
I'm going to limit myself to 4 points. We'll
On 11/14/2013 08:32 AM, George Reese wrote:
One critical reasons why tasks rather than resource status may be
required is because:
a) The system state may not be sufficient at time of POST/PUT to
generate a “minimum viable resource” and we don’t want to risk timeouts
waiting for the “minimum via
One critical reasons why tasks rather than resource status may be required is
because:
a) The system state may not be sufficient at time of POST/PUT to generate a
“minimum viable resource” and we don’t want to risk timeouts waiting for the
“minimum viable resource"
b) There may be more stuff ab
Responses to both Jay and George inline.
On Wed, Nov 13, 2013 at 5:08 PM, Jay Pipes wrote:
> Sorry for top-posting, but in summary, I entirely agree with George here.
> His logic is virtually identical to the concerns I raised with the initial
> proposal for Glance Tasks here:
>
> http://lists.
Sorry for top-posting, but in summary, I entirely agree with George
here. His logic is virtually identical to the concerns I raised with the
initial proposal for Glance Tasks here:
http://lists.openstack.org/pipermail/openstack-dev/2013-May/009400.html
and
http://lists.openstack.org/pipermail/o
Let’s preface this with Glance being the part of OpenStack I am least familiar
with. Keep in mind my commentary is related to the idea that the asynchronous
tasks as designed are being considered beyond Glance. The problems of image
upload/import/cloning/export are unlike other OpenStack operati
George,
Thanks for the comments, they make a lot of sense. There is a Glance
team meeting on Thursday where we would like to push a bit further on
this. Would you mind sending in a few more details? Perhaps a sample of
what your ideal layout would be? As an example, how would you prefer
ac
I was asked at the OpenStack Summit to look at the Glance Tasks, particularly
as a general pattern for other asynchronous operations.
If I understand Glance Tasks appropriately, different asynchronous operations
get replaced by a single general purpose API call?
In general, a unified API for ta
me kind of scrubber which
deletes tasks after current_time > expires_at
Please let me know if you've any questions.
Thanks,
-Nikhil
-Original Message-
From: "Nikhil Komawar"
Sent: Thursday, October 3, 2013 2:22pm
To: "OpenStack Development Mailing List"
S
Hi folks,
I was hoping to see if you all were free sometime tomorrow (Friday) Oct 4th at
14:00 UTC to do a sync up on the patch we've had going on for async workers
(full PS here:- [https://review.openstack.org/#/c/46117/]
https://review.openstack.org/#/c/46117/ ).
Venkatesh and I are worki
14 matches
Mail list logo
