On Mon, Feb 02, 2015 at 01:21:31PM -0500, Andrew Laski wrote:
On 02/02/2015 11:26 AM, Daniel P. Berrange wrote:
On Mon, Feb 02, 2015 at 11:19:45AM -0500, Andrew Laski wrote:
On 02/02/2015 05:58 AM, Daniel P. Berrange wrote:
On Sun, Feb 01, 2015 at 11:20:08AM -0800, Noel Burton-Krahn wrote:
On Mon, Feb 02, 2015 at 08:24:20AM +1300, Robert Collins wrote:
On 31 January 2015 at 05:47, Daniel P. Berrange berra...@redhat.com wrote:
In working on a recent Nova migration bug
https://bugs.launchpad.net/nova/+bug/1414065
I had cause to refactor the way the nova libvirt driver
-dev] [nova][libvirt] RFC: ensuring live migration ends
In working on a recent Nova migration bug
https://bugs.launchpad.net/nova/+bug/1414065
I had cause to refactor the way the nova libvirt driver monitors live
migration completion/failure/progress. This refactor has opened
On Sun, Feb 01, 2015 at 11:20:08AM -0800, Noel Burton-Krahn wrote:
Thanks for bringing this up, Daniel. I don't think it makes sense to have
a timeout on live migration, but operators should be able to cancel it,
just like any other unbounded long-running process. For example, there's
no
5:56:56 AM
Subject: Re: [openstack-dev] [nova][libvirt] RFC: ensuring live migration
ends
On Mon, Feb 02, 2015 at 08:24:20AM +1300, Robert Collins wrote:
On 31 January 2015 at 05:47, Daniel P. Berrange berra...@redhat.com
wrote:
In working on a recent Nova migration bug
On 02/02/2015 05:58 AM, Daniel P. Berrange wrote:
On Sun, Feb 01, 2015 at 11:20:08AM -0800, Noel Burton-Krahn wrote:
Thanks for bringing this up, Daniel. I don't think it makes sense to have
a timeout on live migration, but operators should be able to cancel it,
just like any other unbounded
On 02/02/2015 11:26 AM, Daniel P. Berrange wrote:
On Mon, Feb 02, 2015 at 11:19:45AM -0500, Andrew Laski wrote:
On 02/02/2015 05:58 AM, Daniel P. Berrange wrote:
On Sun, Feb 01, 2015 at 11:20:08AM -0800, Noel Burton-Krahn wrote:
Thanks for bringing this up, Daniel. I don't think it makes
On 31 January 2015 at 05:47, Daniel P. Berrange berra...@redhat.com wrote:
In working on a recent Nova migration bug
https://bugs.launchpad.net/nova/+bug/1414065
I had cause to refactor the way the nova libvirt driver monitors live
migration completion/failure/progress. This refactor has
Thanks for bringing this up, Daniel. I don't think it makes sense to have
a timeout on live migration, but operators should be able to cancel it,
just like any other unbounded long-running process. For example, there's
no timeout on file transfers, but they need an interface report progress
and
In working on a recent Nova migration bug
https://bugs.launchpad.net/nova/+bug/1414065
I had cause to refactor the way the nova libvirt driver monitors live
migration completion/failure/progress. This refactor has opened the
door for doing more intelligent active management of the live
- Original Message -
From: Daniel P. Berrange berra...@redhat.com
To: openstack-dev@lists.openstack.org, openstack-operat...@lists.openstack.org
Sent: Friday, 30 January, 2015 11:47:16 AM
Subject: [openstack-dev] [nova][libvirt] RFC: ensuring live migration ends
In working
11 matches
Mail list logo
