<html><body><p>When you write "<font size="4">Neutron has the ability already of sending an event</font> <font size="4">as a REST call to notify a third party</font>", that third party can be Nova only as of now and notifying any other party requires changes to Neutron. It seems that one needs to add a notifier for Kuryr similar to the one that exists for Nova that you have pointed to here: [1]. Furthermore, Nuetron needs to be changed to call this new notifier. I suppose one can make the current Nova notifier more generic and have the third party (the client to use for notifying the third party) configurable.<br>Have I understood this correctly or there is such a generic framework already in place?<br><br>Best,<br><br>Mohammad<br><br><img width="16" height="16" src="cid:1__=8FBBF55EDFCD9E8E8f9e8a93df938690918c8FB@" border="0" alt="Inactive hide details for Salvatore Orlando ---06/08/2016 01:06:37 PM---Neutron has the ability already of sending an event as "><font color="#424282">Salvatore Orlando ---06/08/2016 01:06:37 PM---Neutron has the ability already of sending an event as a REST call to notify a third party that a po</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Salvatore Orlando <salv.orlando@gmail.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">06/08/2016 01:06 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [openstack-dev] [Kuryr] [Neutron] Waiting until Neutron Port is Active</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font size="4">Neutron has the ability already of sending an event as a REST call to notify a third party that a port became active [1]</font><br><font size="4">This is used by Nova to hold on booting instances until network has been wired.</font><br><font size="4">Perhaps kuryr could leverage this without having to tap into the AMQP bus, as that would be implementation-specific - since there would be an assumption about having a plugin that communicates with the reference impl l2 agent.</font><br><br><font size="4">Salvatore</font><br><br><font size="4">[1] </font><a href="http://git.openstack.org/cgit/openstack/neutron/tree/neutron/notifiers/nova.py"><u><font size="4" color="#0000FF">http://git.openstack.org/cgit/openstack/neutron/tree/neutron/notifiers/nova.py</font></u></a><br><br><br><br><font size="4">On 8 June 2016 at 17:23, Mohammad Banikazemi <</font><a href="mailto:mb@us.ibm.com" target="_blank"><u><font size="4" color="#0000FF">mb@us.ibm.com</font></u></a><font size="4">> wrote:</font><ul><font size="4">For the Kuryr project, in order to support blocking until vifs are plugged in (that is adding config options similar to the following options define in Nova: vif_plugging_is_fatal and vif_plugging_timeout), we need to detect that the Neutron plugin being used is done with plugging a given vif.<br><br>Here are a few options:<br><br>1- The simplest approach seems to be polling for the status of the Neutron port to become Active. (This may lead to scalability issues but short of having a specific goal for scalability, it is not clear that will be the case.)<br>2- Alternatively, We could subscribe to the message queue and wait for such a port update event. <br>3- It was also suggested that we could use l2 agent extension to detect such an event but that seems to limit us to certain Neutron plugins and therefore not acceptable.<br><br>I was wondering if there are other and better options. <br><br>Best,<br><br>Mohammad</font><br><font size="4"><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: </font><a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank"><u><font size="4" color="#0000FF">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</font></u></a><u><font size="4" color="#0000FF"><br></font></u><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><u><font size="4" color="#0000FF">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></u></a><font size="4"><br></font></ul><tt>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br></tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt><tt><br></tt><br><BR>
</body></html>