When you write "Neutron has the ability already of sending an event as a
REST call to notify a third party", 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.
Have I understood this correctly or there is such a generic framework
already in place?
Best,
Mohammad
From: Salvatore Orlando <salv.orla...@gmail.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date: 06/08/2016 01:06 PM
Subject: Re: [openstack-dev] [Kuryr] [Neutron] Waiting until Neutron
Port is Active
Neutron has the ability already of sending an event as a REST call to
notify a third party that a port became active [1]
This is used by Nova to hold on booting instances until network has been
wired.
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.
Salvatore
[1]
http://git.openstack.org/cgit/openstack/neutron/tree/neutron/notifiers/nova.py
On 8 June 2016 at 17:23, Mohammad Banikazemi <m...@us.ibm.com> wrote:
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.
Here are a few options:
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.)
2- Alternatively, We could subscribe to the message queue and wait for
such a port update event.
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.
I was wondering if there are other and better options.
Best,
Mohammad
__________________________________________________________________________
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
__________________________________________________________________________
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
