...@redhat.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Tuesday, November 5, 2013 10:40:48 AM
Subject: Re: [openstack-dev] Improvement of Cinder API wrt
https://bugs.launchpad.net/nova/+bug/1213953
Also, that's still an overly
Message -
From: Solly Ross sr...@redhat.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Tuesday, November 5, 2013 10:40:48 AM
Subject: Re: [openstack-dev] Improvement of Cinder API wrt
https://bugs.launchpad.net/nova/+bug/1213953
: [openstack-dev] Improvement of Cinder API wrt
https://bugs.launchpad.net/nova/+bug/1213953
Also, that's still an overly complicated process for one or two VMs. The
idea behind the Nova command was to minimize the steps in the
image-volume-VM process for a single VM.
Complexity
On 11/05/2013 01:27 AM, Avishay Traeger wrote:
I think the proper fix is to make sure that Cinder is moving the volume
into 'error' state in all cases where there is an error. Nova can then
poll as long as its in the 'downloading' state, until it's 'available' or
'error'. Is there a reason
/2013 07:41 AM
Subject:Re: [openstack-dev] Improvement of Cinder API wrt
https://bugs.launchpad.net/nova/+bug/1213953
On Tue, Nov 5, 2013 at 7:27 AM, John Griffith
john.griff...@solidfire.com wrote:
On Tue, Nov 5, 2013 at 6:29 AM, Chris Friesen
chris.frie...@windriver.com
Wouldn't you still need variable timeouts? I'm assuming that copying
multi-gig cinder volumes might take a while, even if it's local. (Or
are you assuming copy-on-write?)
Chris
On 11/05/2013 01:43 AM, Caitlin Bestler wrote:
Replication of snapshots is one solution to this.
You create a
Sent: Tuesday, November 5, 2013 9:23:39 AM
Subject: Re: [openstack-dev] Improvement of Cinder API wrt
https://bugs.launchpad.net/nova/+bug/1213953
Wouldn't you still need variable timeouts? I'm assuming that copying
multi-gig cinder volumes might take a while, even if it's local. (Or
are you
Chris Friesen chris.frie...@windriver.com wrote on 11/05/2013 10:21:07
PM:
I think the proper fix is to make sure that Cinder is moving the volume
into 'error' state in all cases where there is an error. Nova can then
poll as long as its in the 'downloading' state, until it's 'available'
or
So,
There's currently an outstanding issue with regards to a Nova shortcut command
that creates a volume from an image and then boots from it in one fell swoop.
The gist of the issue is that there is currently a set timeout which can time
out before the volume creation has finished (it's
On 11/04/2013 03:49 PM, Solly Ross wrote:
So, There's currently an outstanding issue with regards to a Nova
shortcut command that creates a volume from an image and then boots
from it in one fell swoop. The gist of the issue is that there is
currently a set timeout which can time out before the
On Tue, Nov 5, 2013 at 7:27 AM, John Griffith
john.griff...@solidfire.com wrote:
On Tue, Nov 5, 2013 at 6:29 AM, Chris Friesen
chris.frie...@windriver.com wrote:
On 11/04/2013 03:49 PM, Solly Ross wrote:
So, There's currently an outstanding issue with regards to a Nova
shortcut command that
in
'downloading'?
Thanks,
Avishay
From: John Griffith john.griff...@solidfire.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date: 11/05/2013 07:41 AM
Subject:Re: [openstack-dev] Improvement of Cinder API wrt
Replication of snapshots is one solution to this.
You create a Cinder Volume once. snapshot it. Then replicate to the hosts
that need it (this is the piece currently missing). Then you clone there.
I will be giving an in an hour in conference session on this and other uses
of snapshots in the
13 matches
Mail list logo
