On 03/02/2015 06:24 PM, Jay Pipes wrote:
On 02/25/2015 06:41 AM, Daniel P. Berrange wrote:
On Wed, Feb 25, 2015 at 02:08:32PM +, Gary Kotton wrote:
I understand that this is a high or critical bug but I think that
we need to discuss more on it and try have a more robust model.
What I'm
-Original Message-
From: Jay Pipes Sent Monday, March 02, 2015 16:24
On 02/25/2015 06:41 AM, Daniel P. Berrange wrote:
On Wed, Feb 25, 2015 at 02:08:32PM +, Gary Kotton wrote:
I understand that this is a high or critical bug but I think that
we need to discuss more on it and try
On 02/25/2015 06:41 AM, Daniel P. Berrange wrote:
On Wed, Feb 25, 2015 at 02:08:32PM +, Gary Kotton wrote:
I understand that this is a high or critical bug but I think that
we need to discuss more on it and try have a more robust model.
What I'm not seeing from the bug description is just
Hi,
There is an issue with the statistics reported when a nova compute driver has
shared storage attached. That is, there may be more than one compute node
reporting on the shared storage. A patch has been posted -
https://review.openstack.org/#/c/155184. The direction here was to add a extra
Actually I have similar idea, an plan to work on it at L by a nova-spec (is
it worth a spec?).
But this idea not come from this bug, it's come from other cases:
1. Currently we need specified 'on_shared_storage' and 'block_migration'
when evacuate and live_migration. After we tracking the shared
