! ---Andreas Scheuring ---04/10/2018
> 10:19:21 PM---Yes, that’s how it works! ---
>
> From: Andreas Scheuring
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 04/10/2018 10:19 PM
> Subject:
t; From: Andreas Scheuring
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 04/10/2018 10:19 PM
> Subject: Re: [openstack-dev] [nova] Changes
> toComputeVirtAPI.wait_for_instance_event
>
> ---
: Andreas Scheuring
To: "OpenStack Development Mailing List (not for usage questions)"
Date: 04/10/2018 10:19 PM
Subject: Re: [openstack-dev] [nova] Changes
toComputeVirtAPI.wait_for_instance_event
Yes, that’s how it works!
---
Andreas Scheuring
Yes, that’s how it works!
---
Andreas Scheuring (andreas_s)
On 10. Apr 2018, at 16:05, Matt Riedemann wrote:
On 4/9/2018 9:57 PM, Chen CH Ji wrote:
> Could you please help to share whether this kind of event is sent by
> neutron-server or neutron agent ? I searched neutron code
> from [1][2]
On 4/9/2018 9:57 PM, Chen CH Ji wrote:
Could you please help to share whether this kind of event is sent by
neutron-server or neutron agent ? I searched neutron code
from [1][2] this means the agent itself need tell neutron server the
device(VIF) is up then neutron server will send notification
Could you please help to share whether this kind of event is sent by
neutron-server or neutron agent ? I searched neutron code
from [1][2] this means the agent itself need tell neutron server the
device(VIF) is up then neutron server will send notification
to nova through REST API and in turn cons
