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

-
https://github.com/openstack/nova/blob/stable/kilo/nova/availability_zones.py#L130

-
https://github.com/openstack/nova/blob/stable/kilo/nova/api/openstack/compute/contrib/availability_zone.py#L68

-
https://github.com/openstack/nova/blob/stable/kilo/nova/api/openstack/compute/contrib/hosts.py#L88-L89

-
https://github.com/openstack/nova/blob/stable/kilo/nova/compute/api.py#L3399-L3421
.


Blueprint which plans to fix this :
https://blueprints.launchpad.net/nova/+spec/servicegroup-api-control-plane

Related Spec : 1) https://review.openstack.org/#/c/190322/

                           2) https://review.openstack.org/#/c/138607/

-Vilobh


On Mon, May 11, 2015 at 8:08 AM, Chris Friesen <chris.frie...@windriver.com>
wrote:

> 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:
>> https://bugs.launchpad.net/oslo.messaging/+bug/1437955
>>
>> We do not need a dedicated is_up just for this.
>>
>
> Is that really going to help?  As I understand it if nova-compute dies (or
> is isolated) then the queue remains present on the server but nothing will
> process messages from it.
>
> Chris
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to