-Original Message-
From: Ahmed RAHAL [mailto:ara...@iweb.com]
Sent: 25 June 2014 20:25
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] should we have a stale data indication in
nova list/show?
Le 2014-06-25 14:26, Day, Phil a écrit :
-Original
I like the current behavior of not changing the VM state if nova-compute
goes down.
The cloud operators can identify the issue in the compute node and try to
fix it without users noticing. Depending in the problem I can inform users
if instances are affected and change the state if necessary.
I
On 06/25/2014 04:28 AM, Belmiro Moreira wrote:
I like the current behavior of not changing the VM state if nova-compute
goes down.
The cloud operators can identify the issue in the compute node and try
to fix it without users noticing. Depending in the problem I can inform
users if
-Original Message-
From: Sean Dague [mailto:s...@dague.net]
Sent: 25 June 2014 11:49
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] should we have a stale data indication in
nova list/show?
On 06/25/2014 04:28 AM, Belmiro
On Wed, Jun 25, 2014 at 11:26 AM, Day, Phil philip@hp.com wrote:
-Original Message-
From: Sean Dague [mailto:s...@dague.net]
Sent: 25 June 2014 11:49
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] should we have a stale
Le 2014-06-25 14:26, Day, Phil a écrit :
-Original Message-
From: Sean Dague [mailto:s...@dague.net]
Sent: 25 June 2014 11:49
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] should we have a stale data indication in
nova list/show
On Jun 18, 2014 3:03 PM, Chris Friesen chris.frie...@windriver.com
wrote:
The output of nova list and nova show reflects the current status in
the database, not the actual state on the compute node.
If the instances in question are on a compute node that is currently
down, then the information
On 06/24/2014 04:42 PM, Joe Gordon wrote:
On Jun 18, 2014 3:03 PM, Chris Friesen chris.frie...@windriver.com
mailto:chris.frie...@windriver.com wrote:
The output of nova list and nova show reflects the current status
in the database, not the actual state on the compute node.
If the
On Jun 24, 2014 2:31 PM, Russell Bryant rbry...@redhat.com wrote:
On 06/24/2014 04:42 PM, Joe Gordon wrote:
On Jun 18, 2014 3:03 PM, Chris Friesen chris.frie...@windriver.com
mailto:chris.frie...@windriver.com wrote:
The output of nova list and nova show reflects the current status
On 06/24/2014 02:38 PM, Joe Gordon wrote:
I agree nova shouldn't take any actions. But I don't think leaving an
instance as 'active' is right either. I was thinking move instance to
error state (maybe an unknown state would be more accurate) and let the
user deal with it, versus just letting
On Jun 24, 2014 2:47 PM, Rick Jones rick.jon...@hp.com wrote:
On 06/24/2014 02:38 PM, Joe Gordon wrote:
I agree nova shouldn't take any actions. But I don't think leaving an
instance as 'active' is right either. I was thinking move instance to
error state (maybe an unknown state would be
- Original Message -
From: Rick Jones rick.jon...@hp.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
On 06/24/2014 02:38 PM, Joe Gordon wrote:
I agree nova shouldn't take any actions. But I don't think leaving an
instance as
On 06/24/2014 02:53 PM, Steve Gordon wrote:
- Original Message -
From: Rick Jones rick.jon...@hp.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
On 06/24/2014 02:38 PM, Joe Gordon wrote:
I agree nova shouldn't take any actions.
Le 2014-06-24 17:38, Joe Gordon a écrit :
On Jun 24, 2014 2:31 PM, Russell Bryant rbry...@redhat.com
mailto:rbry...@redhat.com wrote:
There be dragons here. Just because Nova doesn't see the node reporting
in, doesn't mean the VMs aren't actually still running. I think this
needs to
On Tue, Jun 24, 2014 at 4:16 PM, Ahmed RAHAL ara...@iweb.com wrote:
Le 2014-06-24 17:38, Joe Gordon a écrit :
On Jun 24, 2014 2:31 PM, Russell Bryant rbry...@redhat.com
mailto:rbry...@redhat.com wrote:
There be dragons here. Just because Nova doesn't see the node
reporting
in,
On Tue, Jun 24, 2014 at 5:12 PM, Joe Gordon joe.gord...@gmail.com wrote:
On Tue, Jun 24, 2014 at 4:16 PM, Ahmed RAHAL ara...@iweb.com wrote:
Le 2014-06-24 17:38, Joe Gordon a écrit :
On Jun 24, 2014 2:31 PM, Russell Bryant rbry...@redhat.com
mailto:rbry...@redhat.com wrote:
There
I don't think we should be flipping states for instances on a potentially
downed compute. We definitely should not set an instance to ERROR. I think a
time associated with the last power state check might be nice and be good
enough.
- Chris
On Jun 24, 2014, at 5:17 PM, Joe Gordon
Hi,
Le 2014-06-24 20:12, Joe Gordon a écrit :
Finally, assuming the customer had access to this 'unknown' state
information, what would he be able to do with it ? Usually he has no
lever to 'evacuate' or 'recover' the VM. All he could do is spawn
another instance to replace the
The output of nova list and nova show reflects the current status in
the database, not the actual state on the compute node.
If the instances in question are on a compute node that is currently
down, then the information is stale and possibly incorrect. Would
there be any benefit in adding
19 matches
Mail list logo
