Running a query against servers in e-s seems like something to try to avoid; it will rely on the search index being up to date (i.e. although a document may have been indexed it's not necessarily visible to search yet versus retrieval by id). I don't see a cleaner option though. Ideally nova would send out a notification as it does for volume attach.
On detach, not so much:
{ allowed_ address_ pairs": [], extra_dhcp_ opts": [], 06T17:40: 05", device_ owner": "", port_security_ enabled" : true, binding: profile" : {},
"subnet_ id": "e89b3879- db18-4c9d- a2b5-9a985f0bd5 12",
"ip_ address" : "172.40.0.4"
"subnet_ id": "44064101- 3f26-4eae- ab0e-2c9e6751f8 49",
"ip_ address" : "fd4f:2ae3: e98a:0: f816:3eff: fe2e:2028" 0919-4109- 9990-a2f21b25fe c7", security_ groups" : [
"9790d25c- aea7-4342- b4ef-5f0f7cb657 bd" binding: vif_details" : {}, binding: vif_type" : "unbound", mac_address" : "fa:16: 3e:2e:20: 28", binding: host_id" : "", description" : "", admin_state_ up": true, b4f2-4ee3- b131-27829ab599 84", 01T17:47: 16", binding: vnic_type" : "normal", 8c95d6e84483fc9 95a"
"event_type": "port.update.end",
"payload": {
"port": {
"
"
"updated_at": "2016-04-
"
"
"
"fixed_ips": [
{
},
{
}
],
"id": "ee486fc1-
"
],
"
"
"
"status": "DOWN",
"
"
"device_id": "",
"name": "attaching-port",
"
"network_id": "910cc348-
"dns_name": "octo-1",
"created_at": "2016-04-
"
"tenant_id": "3307049f95b740
}
}
# SNIP
}
Running a query against servers in e-s seems like something to try to avoid; it will rely on the search index being up to date (i.e. although a document may have been indexed it's not necessarily visible to search yet versus retrieval by id). I don't see a cleaner option though. Ideally nova would send out a notification as it does for volume attach.