You can do it like we did for juno Designate as covered in our Vancouver talk start about 21 minutes: https://www.youtube.com/watch?v=N8y51zqtAPA We've not ported the code to Kilo or Liberty yet but the approach may still work. On Fri, Nov 13, 2015 at 9:49 AM, Jaime Fernández <jjjaime at gmail.com> wrote: > When removing an instance (with one floating address assigned) in Horizon, > designate-sink only receives an event for instance removal. As a result, > only the instance is removed but the floating addresses records are not > removed. > I'm not sure if it's a bug in openstack (I guess that it should also > notify about the unassignment of floating addresses) or it should be > considered in the nova notification handler ( > https://github.com/openstack/designate/blob/master/designate/notification_handler/nova.py#L72 > ). > However, it is not possible to add metadata in the floating IP records to > save the instance_id and remove them easily when an instance is removed. > What's the best approach to remove the floating address records of an > instance that is being removed? > > __________________________________________________________________________ > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151113/e44bb032/attachment.html>