[openstack-dev] [nova] Changes toComputeVirtAPI.wait_for_instance_event

Chen CH Ji jichenjc at cn.ibm.com
Wed Apr 11 02:06:09 UTC 2018


Thanks for your info ,really helpful

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM at IBMCN   Internet: jichenjc at cn.ibm.com
Phone: +86-10-82451493
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:	Andreas Scheuring <scheuran at linux.vnet.ibm.com>
To:	"OpenStack Development Mailing List (not for usage questions)"
            <openstack-dev at lists.openstack.org>
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 (andreas_s)



On 10. Apr 2018, at 16:05, Matt Riedemann <mriedemos at gmail.com> 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] 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 consumed by compute node?
      [1]
      https://github.com/openstack/neutron/tree/master/neutron/notify_port_active_direct

      [2]
      https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/rpc.py#L264

I believe the neutron agent is the one that is getting (or polling) the
information from the underlying network backend when VIFs are plugged or
unplugged from a host, then route that information via RPC to the neutron
server which then sends an os-server-external-events request to the compute
REST API, which then routes the event information down to the nova-compute
host where the instance is currently running.

--

Thanks,

Matt

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at 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-request at lists.openstack.org?subject:unsubscribe
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0&m=tIntFpZ0ffp-_h5CsqN1I9tv64hW2xugxBXaxDn7Z_I&s=z2jOgMD7B3XFoNsUHTtIO6hWKYXH-Dm4L4P0-u-oSSw&e=



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180411/36f92930/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180411/36f92930/attachment.gif>


More information about the OpenStack-dev mailing list