Dear Brian,

thanks for your response and consideration of the issue. I did some further
tests again to retrieve the details that are available for each action.

1) When disassociating an FIP from a VM, I get the following:

DEBUG Received event: type floatingip.update.start, payload {'id':
'************************************', 'floatingip': {'port_id': None}}

DEBUG Received event: type floatingip.update.end, payload {'floatingip':
{'router_id': None, 'status': 'ACTIVE', 'description': '', 'tags': [],
'tenant_id': '********************************', 'created_at':
'2018-11-29T12:15:18Z', 'updated_at': '2019-07-31T08:14:08Z',
'floating_network_id': '************************************',
'fixed_ip_address': None, 'floating_ip_address': '134.94.199.121',
'revision_number': 70, 'project_id': '********************************',
'port_id': None, 'id': '************************************'}}

2) When deleting a VM that has an FIP associated to it, I get the following event

DEBUG Received event: type port.delete.start, payload {'port_id':
'************************************'}

DEBUG Received event: type port.delete.end, payload {'port_id':
'************************************', 'port': {'status': 'ACTIVE',
'binding:host_id': 'hdfc006', 'description': '', 'allowed_address_pairs': [],
'tags': [], 'extra_dhcp_opts': [], 'updated_at': '2019-07-31T07:41:54Z',
'device_owner': 'compute:HDFCloud', 'revision_number': 10,
'port_security_enabled': True, 'binding:profile': {}, 'fixed_ips':
[{'subnet_id': '************************************', 'ip_address':
'10.0.19.6'}], 'id': '************************************', 'security_groups':
['************************************'], 'device_id':
'************************************', 'name': '', 'admin_state_up': True,
'network_id': '************************************', 'tenant_id':
'********************************', 'binding:vif_details': {'port_filter': True,
'datapath_type': 'system', 'ovs_hybrid_plug': True}, 'binding:vnic_type':
'normal', 'binding:vif_type': 'ovs', 'mac_address': 'fa:16:3e:28:7f:7c',
'project_id': '********************************', 'created_at':
'2019-07-31T07:41:48Z'}}

That is all I get, and there is unfortunately no FIP in the event. I do see the
fixed IP, though.


Regarding the behaviour of the router, I need to be more precise:

Apart from serving FIPs for VMs, the router itself has an IP in the external
network to serve as a NAT router. You'll see it under Project -> Network ->
Routers -> router -> Overview -> External Fixed IPs. OK, this is not a floating
IP, agreed. Still, this is also something we would like to keep track of.

Now, when there is no floating IP on the router for any VM, it still has this
IP. I do receive a deletion event of the IP when deleting the router. For
completeness, it looks like this:

DEBUG Received event: type router.delete.start, payload {'router_id':
'************************************'}

 DEBUG Received event: type router.delete.end, payload {'router_id':
'************************************', 'router': {'status': 'ACTIVE',
'external_gateway_info': {'network_id': '************************************',
'enable_snat': True, 'external_fixed_ips': [{'subnet_id':
'************************************', 'ip_address': '134.94.199.187'}]},
'availability_zone_hints': [], 'availability_zones': ['nova'], 'description':
'', 'tags': [], 'tenant_id': '********************************', 'created_at':
'2019-07-31T07:53:51Z', 'admin_state_up': True, 'updated_at':
'2019-07-31T07:53:53Z', 'flavor_id': None, 'revision_number': 2, 'routes': [],
'project_id': '********************************', 'id':
'************************************', 'name': 'tmp-router'}}

As you can see, the router.delete.end event contains the ip_address. When
clearing the gateway instead of deleting the router, I do not get the IP in the
event:

DEBUG Received event: type router.update.start, payload {'router':
{'external_gateway_info': {}}, 'id': '************************************'}

DEBUG Received event: type router.update.end, payload {'router': {'status':
'ACTIVE', 'external_gateway_info': None, 'availability_zone_hints': [],
'availability_zones': ['nova'], 'description': '', 'tags': [], 'tenant_id':
'********************************', 'created_at': '2019-07-31T08:02:58Z',
'admin_state_up': True, 'updated_at': '2019-07-31T08:03:08Z', 'flavor_id': None,
'revision_number': 6, 'routes': [], 'project_id':
'********************************', 'id':
'************************************', 'name': 'test-router'}}

"Set gateway" gives me the IP address in the event:

DEBUG Received event: type router.update.start, payload {'router':
{'external_gateway_info': {'network_id':
'************************************'}}, 'id':
'************************************'}

DEBUG Received event: type router.update.end, payload {'router': {'status':
'ACTIVE', 'external_gateway_info': {'network_id':
'************************************', 'enable_snat': True,
'external_fixed_ips': [{'subnet_id': '************************************',
'ip_address': '134.94.199.179'}]}, 'availability_zone_hints': [],
'availability_zones': ['nova'], 'description': '', 'tags': [], 'tenant_id':
'********************************', 'created_at': '2019-07-31T08:02:58Z',
'admin_state_up': True, 'updated_at': '2019-07-31T08:05:11Z', 'flavor_id': None,
'revision_number': 8, 'routes': [], 'project_id':
'********************************', 'id':
'************************************', 'name': 'test-router'}}

Again, I would expect to have the FIPs for these events. If there are good
reasons for not being able to provide them, I would understand that. On the
other hand, it would require me to keep track of certain links and associations
or access the Neutron DB directly, which I would like to avoid.


Best regards,
Björn