yahoo-eng-team team mailing list archive

[Christian Berendt <1508942@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

At the moment the update events for a floating IP address do not contain
an instance ID. I think it makes sense to include the instance ID in the
payload of the generated event to simplify the processing of those
events in 3rd party applications. At the moment the payload only
contains the port ID when associating a floating IP address with an
instance. When disassociating a floating IP address there is no port ID
included in the payload.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: wishlist

** Description changed:

- At the moment the generated events for when updating a floating IP
- address do not contain an instance ID. I think it makes sense to include
- the instance ID in the payload of the generated event to simplify the
- processing of those events in 3rd party applications listening for this
- kind of event. At the moment in the payload only the port ID is included
- when associating a floating IP address with an instance. When
- disassociating a floating IP address from an instance there is also no
- port ID included in the payload.
+ At the moment the update events for a floating IP address do not contain
+ an instance ID. I think it makes sense to include the instance ID in the
+ payload of the generated event to simplify the processing of those
+ events in 3rd party applications. At the moment the payload only
+ contains the port ID when associating a floating IP address with an
+ instance. When disassociating a floating IP address there is no port ID
+ included in the payload.

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

Title:
  Events for create/update/delete floating IP address do not contain an
  instance ID

Status in neutron:
  New

Bug description:
  At the moment the update events for a floating IP address do not
  contain an instance ID. I think it makes sense to include the instance
  ID in the payload of the generated event to simplify the processing of
  those events in 3rd party applications. At the moment the payload only
  contains the port ID when associating a floating IP address with an
  instance. When disassociating a floating IP address there is no port
  ID included in the payload.

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