Few more places which can trigger inconsistent behaviour.
-
https://github.com/openstack/nova/blob/stable/kilo/nova/api/openstack/compute/contrib/services.py#L44
-
https://github.com/openstack/nova/blob/stable/kilo/nova/api/openstack/compute/contrib/hypervisors.py#L98
-
Le 11/06/2015 18:52, Vilobh Meshram a écrit :
Few more places which can trigger inconsistent behaviour.
-
https://github.com/openstack/nova/blob/stable/kilo/nova/api/openstack/compute/contrib/services.py#L44
-
- Original Message -
From: John Garbutt j...@johngarbutt.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Saturday, May 9, 2015 1:18:48 PM
Subject: Re: [openstack-dev] [nova] Service group foundations and features
On 05/11/2015 07:13 AM, Attila Fazekas wrote:
From: John Garbutt j...@johngarbutt.com
* From the RPC api point of view, do we want to send a cast to
something that we know is dead, maybe we want to? Should we wait for
calls to timeout, or give up quicker?
How to fail sooner:
From: ext Chris Friesen [mailto:chris.frie...@windriver.com]
Sent: Monday, May 11, 2015 6:09 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] Service group foundations and features
On 05/11/2015 07:13 AM, Attila Fazekas wrote:
From: John Garbutt j...@johngarbutt.com
On 7 May 2015 at 22:52, Joshua Harlow harlo...@outlook.com wrote:
Hi all,
In seeing the following:
- https://review.openstack.org/#/c/169836/
- https://review.openstack.org/#/c/163274/
- https://review.openstack.org/#/c/138607/
Vilobh and I are starting to come to the conclusion that the
Hi all,
In seeing the following:
- https://review.openstack.org/#/c/169836/
- https://review.openstack.org/#/c/163274/
- https://review.openstack.org/#/c/138607/
Vilobh and I are starting to come to the conclusion that the service
group layers in nova really need to be cleaned up (without