yahoo-eng-team team mailing list archive

[Björn Hagemeier <b.hagemeier@xxxxxxxxxxxxx>]

Public bug reported:

Dear all,

we are using `oslo_messaging_notifications` configured in Neutron server [1] to
receive updates about floating ip (FIP) associations and disassociations to process
them with an in-house tool. This works well in almost all cases, except one.

The cases that are working:

1) associate FIP to router (event router.create.end, router.update.end)
2) delete router that still has a FIP (router.delete.end)
3) associate FIP to VM
4) disassociate FIP from VM

Now, the interesting case that *does not work* is the deletion of a VM that
still has a FIP associated to it. We would like to have this case covered and
be notified about the disassociation. Is there a way to capture this event
via a notification?

There is one more case that also does not seem to work: when clearing the
gateway of a router ("Clear Gateway" in the Horizon dashboard), I am also
not notified of the FIP being released. However, this happens much less
frequently, so we're not overly worried about it.

We do need the information to update an internal, site-wide database of
registered addresses and responsible contacts. There are solutions that
periodically poll the information from the API and report changes as
compared to the previously recorded state. The notification solution allows
us to update our central DB in a more timely manner.


Thanks for any help and best regards,
Björn


[1]
https://docs.openstack.org/oslo.messaging/latest/configuration/opts.html#oslo_messaging_notifications

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1838403

Title:
  Asymmetric floating IP notifications

Status in neutron:
  New

Bug description:
  Dear all,

  we are using `oslo_messaging_notifications` configured in Neutron server [1] to
  receive updates about floating ip (FIP) associations and disassociations to process
  them with an in-house tool. This works well in almost all cases, except one.

  The cases that are working:

  1) associate FIP to router (event router.create.end, router.update.end)
  2) delete router that still has a FIP (router.delete.end)
  3) associate FIP to VM
  4) disassociate FIP from VM

  Now, the interesting case that *does not work* is the deletion of a VM that
  still has a FIP associated to it. We would like to have this case covered and
  be notified about the disassociation. Is there a way to capture this event
  via a notification?

  There is one more case that also does not seem to work: when clearing the
  gateway of a router ("Clear Gateway" in the Horizon dashboard), I am also
  not notified of the FIP being released. However, this happens much less
  frequently, so we're not overly worried about it.

  We do need the information to update an internal, site-wide database of
  registered addresses and responsible contacts. There are solutions that
  periodically poll the information from the API and report changes as
  compared to the previously recorded state. The notification solution allows
  us to update our central DB in a more timely manner.

  
  Thanks for any help and best regards,
  Björn

  
  [1]
  https://docs.openstack.org/oslo.messaging/latest/configuration/opts.html#oslo_messaging_notifications

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1838403/+subscriptions